click below
click below
Normal Size Small Size show me how
Scrum
Question | Answer |
---|---|
What are the Scrum values? | commitment, courage, focus, openness, and respect. |
What are the Scrum roles? | product owner, scrum master and the development team members. |
What are the Scrum steps? | Step 1: Product Backlog Creation. ... Step 2: Sprint planning and creating backlog. ... Step 3: Working on sprint. ... Step 4: Testing and Product Demonstration. ... Step 5: Retrospective and the next sprint planning. |
Developers | - On a scrum team, a developer is anyone on the team that is delivering work, including those team members outside of software development. |
Product Owner | - Holds the vision for the product and prioritizes the product backlog |
Scrum Master | - Helps the team best use scrum to build the product. |
What are the three Scrum artifacts? | Scrum artifacts help manage the work: Product Backlog Sprint Backlog Increment |
Product Backlog | - An emergent, ordered list of what is needed to improve the product and includes the product goal. |
Sprint Backlog | - The set of product backlog items selected for the sprint by the developers (team members), plus a plan for delivering the increment and realizing the sprint goal. |
Increment | A sum of usable sprint backlog items completed by the developers in the sprint that meets the definition of done, plus the value of all the increments that came before. Each increment is a recognizable, visibly improved, operating version of the product. |
Scrum Commitments | Each artifact has an associated commitment - not to be confused with one of the scrum values (covered below) Definition of Done Sprint Goal Product Goal |
Definition of Done | - When the increment is delivered, it needs to meet a shared understanding of what “done” means. The definition of done ensures that the standard of quality is met. The definition of done can differ between organizations and teams. |
Sprint Goal | - A specific and singular purpose for the sprint backlog. This goal helps everyone focus on the essence of what needs to be done and why. |
Product Goal | - To plan the work to be done each sprint, teams need an idea of their product's overall objective. Each team may have multiple product goals over its lifetime, but only one at a time. |
Sprint Burndown Charts | A sprint burndown (or burnup) chart is not an official scrum artifact but many teams use it to communicate and track progress toward the sprint goal during the sprint. (Related: The Trouble with Sprint Burndowns) |
What is a sprint burndown chart? | Sprint burndowns are a graphical way of showing how much work is remaining in the sprint, typically in terms of task hours. It is typically updated at the daily scrum. |
What is the purpose of the sprint burndown chart? | Sprint burndown charts help teams gauge whether they will complete the work of a sprint. Burndown charts also reinforce the scrum values of commitment, focus, and openness and one of the three pillars of empirical process control: transparency. |
Scrum Events parts | The Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective |
The Sprint | - The heartbeat of scrum. Each sprint should bring the product closer to the product goal and is a month or less in length. |
Sprint Planning | The entire scrum team establishes the sprint goal, what can be done, and how the chosen work will be completed. Planning should be timeboxed to a maximum of 8 hours for a month-long sprint, with a shorter timebox for shorter sprints. |
Daily Scrum | The developers (team members delivering the work) inspect the progress toward the sprint goal and adapt the sprint backlog as necessary, adjusting the upcoming planned work. A daily scrum should be timeboxed to 15 minutes each day |
Sprint review | The entire scrum team inspects the sprint's outcome with stakeholders and determines future adaptations. Stakeholders are invited to provide feedback on the increment. |
Sprint Retrospective | The scrum team inspects how the last sprint went regarding individuals, interactions, processes, tools, and definition of done. The team identifies improvements to make the next sprint more effective and enjoyable. This is the conclusion of the sprint. |
Scrum Events | Scrum teams work in sprints, each of which includes several events (or activities). The events that are contained within each sprint are valuable opportunities to inspect and adapt the product or the process (and sometimes both). |