Scrum - An introduction
•
0 likes•412 views
The document provides an overview of Scrum and its key elements. It discusses that Scrum is an iterative, collaborative framework for managing product development. It also summarizes that Scrum uses sprints, daily stand-up meetings, product backlogs and user stories to help development teams work in an agile way. The document outlines the core Scrum roles of Product Owner, Scrum Master and Development Team and how they work together.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Scrum - An introduction
Similar to Scrum - An introduction (20)
More from Hoang Nguyen
More from Hoang Nguyen (20)
Recently uploaded
Recently uploaded (20)
Scrum - An introduction
- 2. An Overview
- 3. Software development is art
- 4. You want to manage well Must be understandable and predicable
- 5. Source: Introduction to Scrum by Michael James
- 6. Succeeded 35% (16%) Failed 19% (31%) Compromised 46% (53%) Why is not work well?
- 10. Source: Introduction to Scrum by Michael James
- 11. The world is full of uncertainties
- 13. So Don’t try to eliminate all uncertainty Don’t try to guess and live on that JUST Open your eyes Open your mind and try to keep up the future
- 14. Late 1980s/ Early 1990s Iterative, Collaborative, Light on planning and process Just is right idea Poorly implemented … because: lack of discipline, awful quality, prohibitive cost of solution ownership
- 15. A positive focus on people, not just a negative focus on process Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value Kent Beck, Mike Beedle, Arievan Bennekum, Alistair Cockburn, Ward Cunningham, Martin Fowler James Grenning, Jim Highsmith, Andrew Hunt, Ron Jeffries, Jon Kern, Brian Marick Robert C. Martin, Steve Mellor, Ken Schwaber, Jeff Sutherland, Dave Thomas
- 17. An Overview
- 18. Scrum Scrum is much more than a simple framework. Scrum supports our need to be human at work: to belong, to learn, to do, to create and be creative, to grow, to improve, and to interact with other people.
- 19. Source: Introduction to Scrum by Michael James
- 20. Sprints Scrum projects make progress in a series of “sprints”
- 21. Scrum Elements The Scrum Team The meetings Artifacts
- 22. The scrum team
- 23. Responsible for maximizing the value of the product and the work of the Development Team Sole person responsible for managing the Product Backlog Clearly expressing Product Backlog items Ordering the items in the Product Backlog to best achieve goals and missions Optimizing the value of the work the Development Team performs Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next Ensuring the Development Team understands items in the Product Backlog to the level needed. The Product Owner
- 25. A servant leader, responsible for facilitating, guiding, and coaching throughout the sprint cycle Protects the team and the sprint Removes impediments for the team Helps communicate vision and goals Helps the Product Owner manage the backlog Helps the Development Team meet its commitments The Scrum Master
- 26. The Development Team Self-organized team (4-9 people) Owns the “How” of implementation Commits to, and delivers, the work requested by the Product Owner Owns the quality of the product Estimates any work items
- 27. Sprints
- 28. Product Backlog Created and prioritized by the product owner A list of requirement items Ideally expressed such that each item has value to the users or customers of the product Reprioritized at the start of each sprint
- 29. User Stories will: Focus on the WHAT, WHO, and WHY – not the HOW Communicate the business case Allow incremental development Allow us to gather feedback to inform future User Stories Enter: User Stories
- 30. Typical User Story As a USER I want A FEATURE so that BUSINESS GOAL. Acceptance Criteria: 1. … 2. … 3. …
- 31. User Stories: Best Practices Independent Negotiable Valuable Estimable Small Testable
- 32. User Stories: Best Practices • The Three Cs 32 CARD CONVERSATION CONFIRMATION
- 33. Sprints
- 34. Sprint Backlog Is the work that the dev. team needs to address during a sprint Is constructed from the product backlog The decision should be taken by the dev. team The decision should be taken depending on the velocity of its previous sprints (the total effort that the team is capable of delivering in a sprint.
- 35. Sprints
- 36. Product backlog grooming Should be grooming Writing, prioritizing, splitting stories Refining the acceptance criteria of individual stories Should not be longer than an hour Don’t break stories into tasks Product Owner owns this, but everyone contributes
- 37. Sprint planning Is held at the beginning of the sprint cycle Sprint backlog is created by selecting items from the product backlog they can commit to completing Break stories down into tasks Eight-hour time limit: ½ - for prioritizing the product backlog ½ - for hashing out a plan for the sprint, resulting in the sprint backlog.
- 38. Daily Scrum What did I accomplish since we last met? What will I work on next? Is anything in your way? These are not status for the Scrum Master. They are commitments in front of peers. Not for problem solving. No detailed discussions shall happen in this meeting. Daily – 15 minutes – Stand-up
- 39. Sprint review Is held at the end of the sprint cycle Did we get everything done that we had committed to? Demonstrate work that has been completed Whole team participates Invite every one: customer and stackholders Gather feedback and, potentially, new stories
- 40. Sprint retrospective Periodically take a look at: What went well, that we should continue doing? What didn’t go so well, that we should stop doing? What are some steps we can take, as a team, to make things better? For the Scrum team only to inspect and adapt the process
- 41. Sprints
- 42. Change Plan sprint durations around how long you can commit to keeping change out of the sprint
- 43. How to implement