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

Large-Scale Scrum (LeSS) Road, Where does it Le...

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. 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 ✘
  2. 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
  3. 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
  4. More with LeSS Descale to Scale Less › Roles ›

    Artifacts › Processes More › Responsible teams
  5. Ceremonies in LeSS Overall Retrospective Sprint Planning 2 Sprint Review

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

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

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

    Product Backlog Refinement Team Daily / Retrospective Sprint Planning 1
  9. 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
  10. 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
  11. 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
  12. 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
  13. 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
  14. 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)
  15. 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 )
  16. Product Backlog Refinement PBR Group discussion Group discussion Group discussion

    Group discussion Converge Overall PBR Single Team Pick / Trade ticket as if Planning 1
  17. 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
  18. 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
  19. 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
  20. Set Next Agile Goal › Keep building up trust ›

    Keep seeking ways to improve collaboration › Be Agile