- Scrum is an iterative, incremental and holistic agile framework to building software.
- Scrum is based on agile manifesto, values and principles.
- Scrum is easy to understand but not easy to implement – often requires a change in mindset.
- Scrum is not a complete process or methodology.
- Scrum contains influences from observed software development patterns and the Theory of Constraints.
- Focuses on desired outcomes and does not provide details about how everything is done on the project – ‘how’ parts are left upon the team.
- Scrum encourages the team to become more spontaneous and adaptive rather than planning driven.
- Scrum relies on cross functional, self-directing team.
- Scrum eliminates the need of a team leader or a project manager.
- Scrum may conflict with the goals of utmost efficiency and speed.
- In scrum, issues are solved by the whole team, not by an individual team leader.
- Two individuals support the whole scrum team: a ScrumMaster and a Product Owner.
- ScrumMaster is the one who coaches the team and help the team members to perform at a higher level to build the software right.
- Product Owner represents the customer and guides the team toward building the right software.
- Scrum projects advance as time-boxed iterations of 2 to 6 weeks called sprints.
- Scrum team follows four ceremonies: Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
- At the beginning of a sprint, team members commit to delivering select features that were listed on the product backlog.
- When the sprint is over, these features are completed – designed, coded, tested and integrated into the continuously evolving product.
- At the end of the sprint, a sprint review is carried out during which the newly developed features are demonstrated to the product owner and other interested stakeholders for their feedback which might shape the next sprint.
- Scrum inspires team members to continuously learn, communicate and evolve.
- In Scrum, deliveries are made in Business-Focused phases – each phase is done as end-to-end functional slices.
- In scrum, cost of change is low – offers better return-on-investment for projects.
- Scrum team focuses on reducing waste by having a lean mindset.
- While Scrum was originally formalized for software development projects, it works well for other complex scope of work as well.