Scrum Evolution - The Complete Guide to the Agile Framework
Download as PPTX, PDF0 likes118 views
This document provides an overview of Scrum, an agile framework for managing complex software projects. It describes key Scrum concepts like sprints, the product backlog, product owner, daily scrums, sprint planning, reviews, and retrospectives. The goal of Scrum is to deliver working software incrementally in short cycles through self-organizing cross-functional teams.
Scrum Evolution - The Complete Guide to the Agile Framework
- 2. Doug Purcell Author of “Scrum Magic” Founder of Purcell Consult Available on Amazon: https://www.amazon.com/Scrum- Magic-Ultimate-Training-Framework/dp/0997326212
- 3. Scrum in 1 Sentence
- 4. A framework for managing the complexity of building software products
- 5. Visual Overview of Scrum
- 6. The Genesis of Scrum
- 7. The Sprint is the focal point of Scrum. It’s where all the planning, development, and analysis takes place
- 9. Ever went on a roadtrip? You’ll need to traverse roads and read signs that serve as beacons to which route to take
- 10. The Generalities of a Product Roadmap
- 11. The strategic overarching vision for the product
- 12. Provide direction and guidance to internal teams and stakeholders
- 13. Shows high-level initiatives along with a plan on how the company will get there
- 14. Tends to be non-technical in nature; serves primarily as a project management tool
- 15. Is a living document and will evolve throughout the course of the project
- 16. Product Backlog
- 17. The ultimate to do list for the product
- 18. Product Owner
- 19. Is the team member who’s responsible for the product backlog
- 20. They manage, order, and prioritize it
- 21. They should have a strong understanding of the product, and communicate that to the team
- 22. They should have strong business acumen and a solid understanding of the marketplace
- 23. Sprint Planning
- 24. The activities for the upcoming Sprint are brainstormed and decided on during the Sprint planning meeting
- 25. The three team roles: the Scrum Master Product Owner, and development team collaborate to figure out what is feasible during the upcoming Sprint
- 26. It’s timeboxed to 8-hours max for a 4-week Sprint, and shorter for Sprints of lesser duration
- 27. Output = Sprint Backlog Developers forecast the items they can handle in the upcoming Sprint during the Sprint Planning meeting. The product backlog items selected for the upcoming Sprint are known as the Sprint Backlog
- 28. Daily Scrum
- 29. A daily meeting that’s timeboxed to 15-minutes and is primary for the developers to inspect their progress
- 30. Scrum Master
- 31. They teach the team members about the rules of Scrum, is a facilitator, and acts as a servant- leader
- 33. Are the team members who’s responsible for building the potentially shippable product at the end of each Sprint
- 34. They’re limited to 3-9 developers
- 35. They’re self-organizing. They delegate how they do their work
- 36. They’re cross-functional. The team have the skillsets to produce a product Increment
- 37. Sprint Review
- 38. At the end of the Sprint the Sprint Review is held to inspect the Increment and update the product backlog if needed
- 39. The Scrum Team and key stakeholders attend and it’s timeboxed to four hours for one month Sprints
- 40. The Product Owner tracks the outstanding work remaining during the Sprint Review
- 42. This event occurs after the Sprint Review
- 43. Is an opportunity for the team to reflect upon what went well, and what needs improvements
- 44. Timeboxed to a maximum of three hours for one month Sprints
- 45. The Beginnings of a New Sprint
- 46. At the conclusion of the current Sprint, the next Sprint immediately starts. The team should gain a better understanding of the workload they can handle and strive to become more efficient with each Sprint