Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Large-Scale Scrum (LeSS) Road, Where does it Leads?

Large-Scale Scrum (LeSS) Road, Where does it Leads?

LINE DevDay 2020

November 27, 2020
Tweet

More Decks by LINE DevDay 2020

Other Decks in Technology

Transcript

  1. Agenda
    › Background
    › LeSS Overview
    › TODAY’s LeSS Experiment
    › Current State

    View full-size slide

  2. Not a Large Scale Scrum (LeSS) Lecture
    › Debate what is the best approach ✘
    › Provide basic LeSS Overview for the purpose of understanding terms used
    and content of this session ✓
    › Underlying reasoning behind LeSS principles ✘

    View full-size slide

  3. Team’s Belief
    Embrace Agile values and mindset, Don’t stick to a particular Agile methodology
    Trust
    No Trust = Not Agile
    Believe in transparency,
    overcommunicate, and
    open-minded
    Collaboration
    Open-minded to
    suggestions from others
    and learn from
    experience
    Responding to change
    Flexible to change
    Being able to respond
    fast to changes in
    market

    View full-size slide

  4. LINE TODAY
    News content delivery platform

    View full-size slide

  5. Stakeholders from multiple locations
    Requirements increases as user base grew
    Taiwan
    Thailand Indonesia Hong Kong

    View full-size slide

  6. Team Composition
    Multi-functional
    40+
    Members
    Backend
    Frontend
    Service
    Planner
    Designer
    QA

    View full-size slide

  7. Problem as Team and Delivery Item Grow
    Trust
    Business owner’s
    request takes longer to
    deliver
    Collaboration
    More burden:
    Service Planners for
    detail specs,
    Developers code base
    dependency grew,
    QA needed more time to
    test
    Responding to change
    4-6 weeks per release
    Requirement at most
    may miss current sprint
    and wait 2 months

    View full-size slide

  8. LeSS Overview

    View full-size slide

  9. Some LeSS Principles
    Principles most relevant to the session

    View full-size slide

  10. LeSS is Scrum
    › Transparency
    › Empirical process control
    › Self-managing teams

    View full-size slide

  11. More with LeSS
    Descale to Scale
    Less
    › Roles
    › Artifacts
    › Processes
    More
    › Responsible teams

    View full-size slide

  12. Ceremonies in LeSS

    View full-size slide

  13. Ceremonies in LeSS
    Overall Retrospective
    Sprint Planning 2
    Sprint Review
    Product Backlog
    Refinement
    Team Daily /
    Retrospective
    Sprint Planning 1

    View full-size slide

  14. Ceremonies in LeSS
    Overall Retrospective
    Sprint Planning 2
    Sprint Review
    Product Backlog
    Refinement
    Team Daily /
    Retrospective
    Sprint Planning 1

    View full-size slide

  15. Ceremonies in LeSS
    Overall Retrospective
    Sprint Planning 2
    Sprint Review
    Product Backlog
    Refinement
    Team Daily /
    Retrospective
    Sprint Planning 1

    View full-size slide

  16. Ceremonies in LeSS
    Overall Retrospective
    Sprint Planning 2
    Sprint Review
    Product Backlog
    Refinement
    Team Daily /
    Retrospective
    Sprint Planning 1

    View full-size slide

  17. Team Anxiety with LeSS
    › How to measure success or failure of the experiment?

    View full-size slide

  18. TODAY’s LeSS Experiment

    View full-size slide

  19. First Target Goal
    Backlog
    1
    Sprint
    2 week
    Scrum Teams
    4

    View full-size slide

  20. Forming New Teams

    View full-size slide

  21. Forming New Teams
    4 Teams, 8 people max

    View full-size slide

  22. New Product Team Structure
    Product Owner
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Scrum Master Scrum Master
    Dev Lead
    Service Planner
    Designer
    Service Planner
    Designer

    View full-size slide

  23. New Product Team Structure
    Product Owner
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Scrum Master Scrum Master
    Dev Lead
    Service Planner
    Designer
    Service Planner
    Designer

    View full-size slide

  24. New Product Team Structure
    Product Owner
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Scrum Master Scrum Master
    Dev Lead
    Service Planner
    Designer
    Service Planner
    Designer

    View full-size slide

  25. New Product Team Structure
    Product Owner
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Scrum Master Scrum Master
    Dev Lead
    Service Planner
    Designer
    Service Planner
    Designer

    View full-size slide

  26. New Product Team Structure
    Product Owner
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Backend
    Frontend
    QA
    Scrum Master Scrum Master
    Dev Lead
    Service Planner
    Designer
    Service Planner
    Designer

    View full-size slide

  27. Sprint Cycle
    Goal: 2 Week Sprint
    1 Potential Shippable
    per Sprint
    Release at end of
    Month
    1 Potential Shippable
    per Sprint + Use 2nd
    Sprint as buffer
    Release every 2
    Sprint
    1 Potential
    Shippable per Sprint
    Release every 2
    Sprint
    1 Potential
    Shippable per Sprint
    Release every
    Sprint
    Transition
    (2W Sprint)
    Transition
    (2W Sprint)
    Goal
    Before
    (4W Sprint)

    View full-size slide

  28. Carrying out Ceremonies

    View full-size slide

  29. PO short brief the whole team on the Sprint goal and
    priority.
    Members from all 4 teams pick tickets from the top, and
    quickly trade with other team to maximize productivity.
    Sprint Planning 1 ( Overall Planning )
    Each team takes the selected tickets and begin planning
    independent from other teams.
    Base on estimation and story break down, quickly
    negotiate with service planners
    Sprint Planning 2 ( Single Team Planning )

    View full-size slide

  30. Product Backlog Refinement
    PBR
    Group
    discussion
    Group
    discussion
    Group
    discussion
    Group
    discussion
    Converge

    View full-size slide

  31. Product Backlog Refinement
    PBR
    Group
    discussion
    Group
    discussion
    Group
    discussion
    Group
    discussion
    Converge
    Overall PBR
    Single Team
    Pick / Trade
    ticket as if
    Planning 1

    View full-size slide

  32. Sprint Review

    View full-size slide

  33. Sprint Review
    › Difficult to organize bazaar-like
    style
    › Big screen, presentation is clearer
    › Stakeholders can easily watch all
    presentations
    › Comments / suggestions can be
    discussed with everyone present

    View full-size slide

  34. Overall Retrospective
    › Team velocity healthcheck
    › Resource issues requiring
    manager assistance
    › Cross team / function collaboration
    improvement
    › Any good lessons learned worth
    sharing with other team
    Team Representatives
    Scrum Masters
    Product Owner
    Managers

    View full-size slide

  35. Continuous Improvements

    View full-size slide

  36. Continuous Improvements
    2 Week Release Goal
    (Community)
    Knowledge sharing
    Function-wise,
    Cross-team
    More responsible
    teams
    Gradual rollout, Feature
    toggle, Automation
    coverage, QA regression
    shortened
    Planning/PBR
    Task breakdown,
    Estimation, ticket
    exchange, align
    PBR/Planning teams
    Scrum/Kanban?
    Split into leading
    team for V2
    architecture revamp

    View full-size slide

  37. Current State

    View full-size slide

  38. Where does it leads?

    View full-size slide

  39. Set Next Agile Goal
    › Keep building up trust
    › Keep seeking ways to improve
    collaboration
    › Be Agile

    View full-size slide