LINE TECHPULSE 2020 - Large Scale Scrum (LeSS) Road, Where does it leads?

Large Scale Scrum (LeSS) Road, Where does it leads? by William Fu @ LINE TECHPULSE 2020 https://techpulse.line.me/

1. William Fu / LINE Taiwan Large Scale Scrum (LeSS) Road, Where does it leads?
2. Agenda › Background › LeSS Overview › LeSS Experiment › Current State
3. Background
4. Not a Large Scale Scrum (LeSS) Lecture › Analyze underlying reasoning behind LeSS principles ✘ › Debate what is the best approach ✘ › Provide basic LeSS Overview for the purpose of understanding terms used and content of this session ✓
5. 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
6. LINE TODAY News content delivery platform
7. Stakeholders from multiple locations Requirements increases as user base grew Taiwan Thailand Indonesia Hong Kong
8. Problem as Team and Delivery Item Grow Trust Business owner’s request takes longer to deliver Collaboration Communication / information sync difficulty increases Responding to change Requirement at most may miss current sprint and wait 2 months
9. LeSS Overview
10. Some LeSS Principles Principles most relevant to the session
11. LeSS is Scrum › Transparency › Self-managing teams › Empirical process control For example…
12. More with LeSS Descale to Scale Less › Roles › Artifacts › Processes More › Responsible Teams
13. TODAY’s LeSS Experiment
14. First Target Goal Product Backlog 1 Teams 8 people Sprint 2 week
15. Forming New Teams
16. 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 New Product Team Structure
17. 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 New Product Team Structure
18. 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 New Product Team Structure
19. 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 New Product Team Structure
20. 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 New Product Team Structure
21. Carrying out Ceremonies
22. 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 ) Normal single team planning Sprint Planning 2 ( Single Team Planning )
23. PBR Group discussion Group discussion Group discussion Group discussion Converge Product Backlog Refinement
24. PBR Group discussion Group discussion Group discussion Group discussion Converge Breakdown as if Planning 2 Pick / Trade ticket as if Planning 1 Product Backlog Refinement
25. Sprint Review
26. No need to repeatedly present demo Contain all presentation in 1-1.5 hours Sprint Review
27. Current State
28. Where does it leads?
29. Set Next Agile Goal › Keep building up trust › Keep seeking ways to improve collaboration › Be Agile
30. Thank you