Please enable JavaScript.
Coggle requires JavaScript to display documents.
SCRUM, 12-agile-principles-infographic - Coggle Diagram
SCRUM
Events
The Daily Scrum
- The Daily Scrum is typically held at the same time and place each do to reduce complexity.
- During the meeting, members of the Development Team explain their progress and plans in three areas:
- What did I do yesterday to help the Development Team meet the Sprint Goal?
- What will I do today to help the Development Team meet the Sprint Goal?
- Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
- Other great questions: What are you working on and who is involved? Moves away from status to relationships
The outputs:
- The Adapted Sprint Backlog is the primary output of the Daily Scrum Meeting.
The Goal:
- The Goal of the meeting is to inspect and adapt the ongoing work of the Sprint A brief daily alignment meeting
The inputs to the meeting:
- the Sprint Goal
- the Sprint Backlog
The Sprint Review
The input to the meeting:
- The Sprint Review Meeting is held at the end of the Sprint.
- The primary input is the Increment developed in the Sprint.
The Goal:
- The Goal of the meeting is to inspect that increment, and adapt the Product Backlog as needed.
- To review the product
Who attends:
- The attendees of the meeting are the Scrum Team and any stakeholders invited to attend by the Product Owner.
The approach to the meeting is focused around three key areas:
- First, the Development Team demonstrates the Product Increment developed during the Sprint. They then answer any questions that might arise about the demonstrated increment.
- Next, the attendees have a collaborative discussion of the business context for the product, including any new developments in the marketplace, feedback from users, projected release dates, if applicable, and any other relevant details that help the team decide what would be the most valuable thing to work on next.
- Finally, the Product Backlog is adapted based on the discussion so that the Scrum Team enters the next Sprint with a shared understanding of the priority and context of their work.
And the output:
- a revised Product Backlog that defines the probable Product Backlog items for the next Sprint.
The Sprint
- If, as is more common, the work turns out to be different than the Development Team expected, they collaborate with the Product Owner to negotiate the scope of Sprint Backlog within the Sprint.
- No new work can be pushed into the Sprint. In Scrum, the only way for work to be part of a Sprint is for the Development Team to pull it in. This is one of the primary purposes of the Sprint Planning meeting.
- If a development team finds that they have additional capacity while the Sprint is in progress, they may choose to pull additional work into the Sprint.
- At all times, meeting the Sprint Goal is the guiding principle.
- The Sprint is the heartbeat of scrum.
- It can be viewed as a container for all of Scrum’s Inspect and Adapt loops.
- The Scrum Team delivers a new iteration of the Working Product every Sprint.
- Each sprint lasts 2-4 weeks (max)
The Sprint Retrospective
- The Sprint Retrospective Meeting is the final event of the Sprint, held after the Sprint Review Meeting.
- The Sprint Retrospective is one of the most important parts of Scrum. When done well, it enables the Scrum Team to continuously improve their approach to their work, Sprint after Sprint.
The Goal:
- The Goal of the meeting is to inspect and adapt the Scrum Team’s approach to their work:
- To review the process
Who attends:
- All members of the Scrum Team attend.
There are many effective patterns to approach running the Sprint Review Meeting. Three elements are common across most of these patterns:
- First, the team inspects how the work was completed in the last Sprint, focusing on areas such as People, Relationships, Process, and Tools.
- Next, the attendees have a collaborative discussion to identify and order major items that went well and opportunities for improvement.
- Finally, the Team creates a plan for how they will roll out any chosen improvements. The plan should be specific, so that improvements are actually carried out in the next Sprint. A planned improvement that is not carried out does not help the team.
-
Artifacts
The Sprint Backlog
It is their plan for how they will deliver the Sprint Goal and related Product Backlog Items during the current sprint.
-
It is regularly updated throughout the Sprint as the Development Team learns more.
It is a transparent, real-time picture of all of the work in the current Sprint.
The Product Increment
The Product Increment provides an accurate, transparent picture of the state of the Product at the end of each Sprint.
It helps realize the Agile principle that “Working Software is the primary measure of progress”, which can be rephrased as “Working Product” for non-software uses of Scrum.
The Product Increment is the sum of all Product Backlog items completed in a given Sprint, plus the value of previous increments.
Since the Product Increment meets the team’s definition of done, it is usable by stakeholders, providing an opportunity for inspection of the current state of the Product.
The Product Backlog
The Product Backlog is the ordered list of everything we might want the development to work on related to the Product under development.
A single Product Owner is responsible for the ordering of the Product Backlog, which provides transparency to the organization about the decision making process used to arrive at the order.
The Product Owner collaborates with the Development Team to refine the Product Backlog. This is an ongoing activity that can require up to 10% of the Development Team’s time.
This dynamic, ongoing, and collaborative refinement of the Product Backlog promotes a shared understanding of the work.
-
-
-
