1. The document provides an overview of the Scrum framework for agile software development, outlining its key events, artifacts, roles, and principles.
2. It describes the Scrum events of the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, as well as the artifacts of the Product Backlog, Sprint Backlog, and Increment.
3. The roles of the Scrum Master, Product Owner, and Developers are defined, with their core accountabilities. The document also emphasizes the self-managed and cross-functional nature of the Scrum Team.
1. The document provides an overview of the Scrum framework for agile software development, outlining its key events, artifacts, roles, and principles.
2. It describes the Scrum events of the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, as well as the artifacts of the Product Backlog, Sprint Backlog, and Increment.
3. The roles of the Scrum Master, Product Owner, and Developers are defined, with their core accountabilities. The document also emphasizes the self-managed and cross-functional nature of the Scrum Team.
1. The document provides an overview of the Scrum framework for agile software development, outlining its key events, artifacts, roles, and principles.
2. It describes the Scrum events of the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, as well as the artifacts of the Product Backlog, Sprint Backlog, and Increment.
3. The roles of the Scrum Master, Product Owner, and Developers are defined, with their core accountabilities. The document also emphasizes the self-managed and cross-functional nature of the Scrum Team.
1. The document provides an overview of the Scrum framework for agile software development, outlining its key events, artifacts, roles, and principles.
2. It describes the Scrum events of the Sprint, Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective, as well as the artifacts of the Product Backlog, Sprint Backlog, and Increment.
3. The roles of the Scrum Master, Product Owner, and Developers are defined, with their core accountabilities. The document also emphasizes the self-managed and cross-functional nature of the Scrum Team.
Artifacts and their Commitments thinking and for Inspect & Adapt Empiricism” •Sprint — max 1 calendar month — Product Backlog -> Product Goal Manage risks •Sprint Planning — max 8 hours (usually shorter for shorter Sprints) — The Scrum Pillars Sprint Backlog -> Sprint Goal Team – initiates Sprint. •Daily Scrum — max 15 minutes — The Values Development Team Increment -> Definition of Done •Sprint Review — max 4 hours (usually shorter for shorter Sprints) — The Scrum Mandatory! Team and Stakeholders (invited by the Product Owner) — informal meeting Scrum in a nutshell Scrum Team During the Sprint •Sprint Retrospective — max 3 hours 1. PO orders Product Backlog (ideas) • Self-managed and cross-functional •No changes are made that (usually shorter for shorter Sprints) — • No sub-teams or hierarchies would endanger the Sprint The Scrum Team – closes Sprint. 2. Scrum Team defines turns ideas into • Collective accountability Goal; value durint a Sprint • All product related activities •Quality goals do not decrease; Definition of Done 3. Scrum Team and stakeholder inspects • Valuable, usable Increment, each Sprint and, • Defined by Organization. the results and adjusts for the next Accountabilities •The Product Backlog is refined • If not, mutually defined by Scrum Typically, 10 or Sprint. • Scrum Master as needed Teams. fewer members 4. Repeat • Facilitator •Scope may be clarified and re- • Causes Impediment removal negotiated between the Management • Product Owner Product Owner and Developers Scaled Scrum • Value maximiser as more is learned. • Bottom-up intelligence. • Developers •Only Product Owner can 1. A single PO. A single Product Backlog. A • create any aspect of a usable Increment each cancel it. single Product Goal at a time Sprint. 2. Scrum Teams self-manage Product Backlog Increment Self-managed 1. Don’t need to synchronize Sprints • Only one • Can only be composed of • Internally decide who does what, when, and how. 2. They decide how to handle • Only one Product Goal “Done” work Cross-functional • Estimated by Developers dependencies • Have all the skills to create value each Sprint • Refined by Scrum Team. Continuously. • Pursue one Product Goal at a time.