Download to read offline
Uploaded byXudong Yu
Mini LeSS Huge
The document describes a framework called Mini LeSS Huge used for large-scale Scrum development with multiple teams. It has the following key aspects: - Uses Scrum and LeSS principles with 10 developers split across backend and frontend teams. - Features a single product backlog, product owner, and sprint planning meetings to coordinate work across teams. - Implements "feature teams" where each team works on user stories from end-to-end rather than separating tasks. - Emphasizes continual review of working software, collaboration between teams, and feedback from stakeholders to ensure successful delivery each sprint.
More Related Content
![20260201 [FOSDEM] gomodjail - library sandboxing for Go modules.pdf](https://cdn.slidesharecdn.com/ss_thumbnails/20260201fosdemgomodjail-librarysandboxingforgomodules-260201225659-76609ec4-thumbnail.jpg?width=640&height=640&fit=bounds)
Mini LeSS Huge
- 1.
- 2. Agenda • Scrum Framework •LeSS Framework • Mini LeSS Huge • Summary
- 3. Agenda • Scrum Framework •LeSS Framework • Mini LeSS Huge • Summary
- 4.
- 5. Agenda • Scrum Framework •LeSS Framework • Mini LeSS Huge • Summary
- 6. LeSS “Large-Scale Scrum (LeSS)is Scrum applied to many teams working together on one product. ”
- 7.
- 8.
- 9. Agenda • Scrum Framework •LeSS Framework • Mini LeSS Huge • Summary
- 10. Background •Internal product •10 developers •Backendand frontend develop separately •Don’t know Agile,Scrum and LeSS •1st time cooperation
- 11.
- 12. Overall Structure Prod Requirement Area CI RequirementArea Environment Requirement Area Version
- 13.
- 14.
- 15. Scrum Framework Product Backlog Refinement 2 Weeks 1stWeek Monday 2nd week Monday or Tuesday 2nd week Friday
- 16.
- 17. Planning •No user storyestimation, no task split and estimation, but have a target scope, trust team who can do their best • Precondition • split user story (independent, negotiable, valuable, small, testable)，can change or stop anytime • develop user story based on priority • start finish, finish start • frequently communicate between team and PO • it’s better to understand the technology
- 18.
- 19. Daily Standup Meeting •Nodaily standup meeting • less member per team • working in same meeting room and face to face communication directly and frequently • team manage the dependency between teams • leading team responsible for integration • “Can i help you?” PO ask team at least one time every day
- 20.
- 21. Review&Retrospective •continually review asearly as possible • walk through product demo with stakeholder to test the solution before sprint start • ask PO review when one user story finished to avoid surprise during review meeting
- 22.
- 23. Cooperate with UED frontenddeveloper prepare the demo after the refinement meeting directly review the demo during the planning meeting
- 24. Cooperate with UED frontenddeveloper prepare the demo after the refinement meeting directly review the demo during the planning meeting
- 25.
- 26. Agenda • Scrum Framework •LeSS Framework • Mini LeSS Huge • Summary
- 27. Summary •deliver working productevery sprint •fix time box sprint( e.g. 2 weeks) •one product owner and one product backlog •feature team •user story split(INVEST) and clarification •feedback quickly and continually
- 28.
- 29. There are nosuch things as best practices in product development. There are only practices that are adequate within a certain context.