- Agile software development
- Planing only for the next minimal implementation
- The implementation phases are called sprints
- Sprints don't take longer than 3 weeks
- Just enough planning to get started with building a minimal feature set
- Building the small feature set
- Test the small feature set
- Review the small feature set
- Getting the feature set ready to ship
- This cycle is repeated for 1-3 weeks until you end up with a feature complete product
Product owner
- Defines the features that are needed in the product
Scrum master
- Runs the meetings
- Keeps things going
Team
- Gets shit done
Product backlog:
- A prioritized list of features -> user stories that could go into the product. This list changes with every sprint
- Format: As a [user, x], I need [feature x], so that [possibility x]
- The size of the task gets estimated
- The highest priority user stories go into the sprint backlog
Sprint backlog:
- Estimated for size
- Commited to for the next sprint burndown
Burndown Charts:
- Show the progress during a sprint by logging the completion of the tasks
- Should approch zero points when the project is in its finishing phases
Sprint planning: Product owner + Scrum master + Team meet to discuss the user stories and estimate their relative sizes
Daily scrum: Brief stand-up meeting where the team discusses, what they've done since the previous meeting and what they're currently working on. If they need help, they can say it here
Sprint review: Occures at the end of the sprint. The team presents their completed work to the product owner and then the team discusses, what can be improved in the next sprint
mhmmmm i smell scrum