Scrum is an agile methodology that can be applied to nearly any project; however, the Scrum methodology is most commonly used in software development. The Scrum process is suited for projects with rapidly changing or highly emergent requirements. Scrum software development progresses via a series of iterations called sprints, which last from one to four weeks. The Scrum model suggests each sprint begins with a brief planning meeting and concludes with a review. These are the basics of Scrum project management.
Scrum is a development framework in which cross-functional teams develop products or projects in an iterative, incremental manner.
• It is the most popular framework to implement agile in Software Development.
• It structures development in cycles of work called Sprints.
• Vision is that the product is potentially shippable at the end of each sprint.
• Product Owner – responsible for maximizing the value of the work that the Scrum Team.
• Scrum Master – responsible for ensuring the process is understood and followed.
• The Team (also called Development Team) – does the work.
• Other Stakeholders (Not part of Scrum Team) – Sponsors, Managers, Business Users, etc.
• A Time-box is a maximum duration in which a Scrum team hopes to achieve desired purpose.
• A typical Scrum has 5 Time-boxes – Sprint, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective.
• Additionally, Scrum may have a Time-box called Product Backlog Refinement.
• A larger projects/releases may have a Time-box called Release Planning.
• Product Backlog – is a prioritized list of everything called PBIs (Product Backlog Items) that might be needed in the product.
• Sprint Backlog – is a list of PBIs approved for a Sprint.
• Sprint Burndown Chart – measures remaining Sprint Backlog items across the time of a Sprint.
• Release Backlog – is a list PBIs identified for a Release.
• Release Burndown Chart – measures remaining Product Backlog across the time of a release plan.