Mind map
Typical scrum timeline
Map content
Typical scrum timeline
Pre-sprint
- 1.Vision statement
- Concise description of goals
- helps team stay focused
- 2.Product roadmap
- visual timeline of major product features
- Usually defined by product owner
- 3.Gather user requirements
- Turn them into deliverable features
- Called stories
- Usually written by product owner
- Made from requirements acquired from customer
- 4.Stories make up the product backlog
- backlog not need to be 100% to start sprint
- Sprint starts when backlog mature enough
- Keep updating backlog during the project
- 1.Vision statement
Sprint activities
- 5.Sprint planning meeting
- Plan what will go into sprint
- Product owner priorities requirements & decides on sprint backlog
- 6.Sprint backlog is list of stories to be developed in next sprint
- 7.Team expands on stories into tasks
- 8. Sprint usually 30 days to deliver agreed stories
- 9. Daily scrum meetings: 15 mins.
- 10.End of sprint team demo's complete stories.
- 11.Scrum retrospective meeting: Review sprint and figure out ways to improve
- 12.Scrum master ensures everyone followed process & offers coaching to everyone
- 5.Sprint planning meeting
Information
- Description
- The Scrum Master Training Manual: Chapter 2
- Created by
- Deleted user · Jul 2018
- Updated
- Jul 17, 2018
- Views
- 18
- Tags
- History
-
- Created by Matthew Swart · Jul 17, 2018
- Copied by Matthew Swart · Jul 17, 2018
- Rating