in contd....
- Sprint
Review: A ceremony at the end of each sprint
when completed stories are demonstrated to team, stakeholders, and users.
The purpose of the Sprint Review is to inspect the
outcome of the Sprint and determine future
adaptations. The Scrum Team presents the results of their work to key
stakeholders and progress toward the Product Goal is discussed.
During the event, the Scrum Team and stakeholders
review what was accomplished in the Sprint and what has changed in their
environment. Based on this information, attendees collaborate on what to do
next. The Product Backlog may also be adjusted
to meet new opportunities. The Sprint Review is a working session and the Scrum
Team should avoid limiting it to a presentation.
The Sprint Review is the second to last event of
the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint.
For shorter Sprints, the event is usually shorter.
The Sprint Review may include the following
elements and more:
·
Attendees include the Scrum Team and
key stakeholders invited by the Product Owner;
·
Members of the Scrum Team explain
what Product Backlog items have been “Done” and what has not been “Done”;
·
The Developers discuss what went
well during the Sprint, what problems it ran into, and how those problems were
solved;
·
The Developers demonstrate the
work that it has “Done” and answers questions about the Increment;
·
The Product Owner discusses the
Product Backlog as it stands. He or she projects likely target and delivery
dates based on progress to date (if needed);
·
The entire group collaborates on what
to do next, so that the Sprint Review provides valuable input to
subsequent Sprint Planning.
·
Review of how the marketplace or
potential use of the product might have changed what is the most valuable thing
to do next; and,
·
Review of the timeline, budget,
potential capabilities, and marketplace for the next anticipated releases of
functionality and capability of the product.
The result of the Sprint Review is a revised
Product Backlog that defines the probable Product Backlog items for the next
Sprint. The Product Backlog may also be adjusted overall to meet new
opportunities.
- Backlog Refinement: An ongoing team activity of
collaboratively updating the Product Backlog via reprioritization,
adding/deleting/rewriting stories, splitting, and estimating. This
practice ensures that the backlog is always actionable.
- Transparency: The idea that information should be
shared freely within and between all Agile teams, projects, and
stakeholders.
- Iteration (Inspect and Adapt): A problem-solving and development
approach that solves large problems by decomposing them into smaller,
discrete problems which are each easier to solve, then solving the smaller
problems. As each smaller problem is solved, new information is uncovered
(Inspect) and decisions can be made and re-made based on the new
information (Adapt).
- Potentially Shippable Product Increment: In Agile software development, a fully
tested and usable version of a product that is produced at the end of each
sprint.
- Self-organizing
Teams with Empowered Product Owners: Agile teams are composed of peers who share ownership of the
team’s work and decision-making processes. Self-organizing teams in Scrum
are given ownership of their work process, their commitments, and their
approach to meeting their commitments. Product Owner is the role in Scrum
that represents the business and customer directly within the development
team. The Product Owner must be empowered to make product decisions in
response to feedback from stakeholders and customers. Taken together, a
Scrum team has complete control over how it does its work and what work it
does.
