Scrum is a design process. In contrast to the waterfall model it is agile. Other agile design processes are Extreme programming (XP) and Kanban.
- Product owner writes a product backlog
- Decide which user stories to work on
- Assign points to user stories
- Work on them (build, test, review)
- Go back to 2.
- 1-3 weeks; plan, build, test and review one feature set. The outcome is a potentially shippable product.
- Product owner: Responsible for defining the features of the product
- Scrum master: Team leader; protects the team and makes sure the process is done as it should be.
- Team: Creates the product
- Product Backlog
- Prioritized set of features that could go into the product. Each element is called a user story and gets written by the product owner.
- User Story
- A way of describing a feature set. It is written in the following format
As a [role] I need [feature] so that [I can do ...].
- Sprint Backlog
- Subset of the product backlog that gets handled in the current sprint. Each user storys work gets estimated in points.
- Sprint planning
- PO, Scrum Master and Team meet to discuss the user stories and how much work they are.
- Daily Scrum
- Each team member says (1) What did I do yesterday? (2) What do I plan to do today? (3) Where am I blocked / need help?
- Sprint Review
- At the end of the sprint. See what was done / what should be done.
- Sprint Retrospective
- What could be better next time?
- Uzility: Introduction to Scrum - 7 Minutes