Professional Documents
Culture Documents
Vini-Vivero Scrum
Vini-Vivero Scrum
Scrum Essentials The Increment (cont) The Increment (cont) Scrum Artifacts
Scrum Definition Each sprint should deliver an Scrum’s artifacts represent work
Scrum is a lightweight increment. A potentially It creates transparency, so or value. They are designed to
framework that helps people, releasable increment is created everyone knows what needs maximize transparency of key
teams and organizations to each sprint. completing and to what information. Thus, everyone
generate value through adaptive Multiple increments may be standards. inspecting them has the same
solutions for complex problems created within a sprint. If a Product Backlog item basis for adaptation.
Increment may be delivered does not meet the Definition of Each artifact contains a
Agile Manifesto
to stakeholders prior to the end Done, it cannot be released or commitment to ensure it
1. Individuals and interactions
of the Sprint. even presented at the Sprint provides information that
over processes and tools.
Sprint Review should never Review. enhances transparency and
2. Working Software over
be a gate to releasing value or a Instead, it returns to the focus against which progress
comprehensive documentation
bottle neck. Showing or Product Backlog for future can be measured:
3. Customer collaboration over
releasing an increment to the consideration. 1. For the Product Backlog it is
contract negotiation.
stake holders should no wait till If the Definition of Done for an the Product Goal.
4. Responding to change over
the sprint review. increment is part of the 2. For the Sprint Backlog it is the
following a plan.
Increments are an additive to standards of the organization, all Sprint Goal.
While there are value in the
all prior Increments and Scrum Teams must follow it as 3. For the Increment it is the
items on the right, we value more
thoroughly verified, ensuring that a minimum. Definition of Done.
the items on the left.
all Increments work together.
If it is not an organizational
In order to provide value, the Scrum Principles
Pillars of Empiricism standard, the Scrum Team must
Increment must be usable.
create a Definition of Done 1. Satisfy 7. Working
1. Transparency The commitment for the appropriate for the product. Customers software is the
2. Inspection increment is: The Definition od The scrum team can add Through Early primary
3. Adaptation Done (DoD) standards. & Continuous measure of
The Definition of Done is a The Developers are required Delivery. progress.
Scrum Values formal description of the state of to conform to the Definition of 2. Welcome 8. Agile
the Increment when it meets the Done. Changing Processes to
1. Commitment 2. Focus 3.
quality measures required for If there are multiple Scrum Requirements support a
Openness 4. Respect 5.
the product. Teams working together on a Even Late in consistent
Courage
DoD creates transparency by product, they must mutually the Project. development
providing everyone a shared define and comply with the pace.
The Increment
understanding of what work was same Definition of Done.
Definition
completed as part of the Key Points
Is a concrete stepping stone
Increment. Once the developers meet
toward the Product Goal.
the Definition of Done of a
Key Points
product backlog item, and
increment is born.
Once a Product Backlog Item
meets the DoD is ready to
present to the stakeholders and
be considered for releasing to
the users.
Scrum Principles (cont) The Sprint Backlog (cont) The Sprint Backlog (cont) The Product Backlog (cont)
3. Frequent 9. Attention to Developers are always The sprint Backlog is initially Developing and explicitly
Delivery of technical accountable for creating a plan created during sprint planning communicating the product goal.
working detail and for the sprint. session, developers are accoun‐ Creating and explicitly
software. design The Sprint Backlog is a plan table of the amount work they communicating product backlog
enhances by and for the developers. can deliver. items.
agility. It is a highly visible, real-time The developers can modify Ordering product backlog items.
4. Collabor‐ 10. Simplicity picture of the work that the the sprint backlog through out Ensuring that the product
ation between (the art of Developers plan to accomplish the sprint. And the sprint backlog is transparent, visible,
the business maximizing during the Sprint in order to backlog emerges during the and understood.
stakeholders the amount of achieve the Sprint Goal sprint. Key points
and developers work not The Sprint Backlog is composed This emergence occurs as
Anyone can add details to a
throughout the done) is of: the scrum team works through
BLI with the Product Owner´s
project. essential the plan and learns more about
The Sprint Goal (why) discretion.
the work needed to achieve the
5. Support, 11. Self-orga‐ The set of Product Backlog Multiple teams can work
sprint goal.
trust and nizing teams items selected for the Sprint together on the same product,
As more work is required, the
motivate the encourage (what) but a single product backlog is
developers add it to the sprint
people great archit‐ Actionable plan for delivering used to describe the upcoming
backlog.
involved. ectures the Increment (how). work on the product.
requirements The commitment for the sprint Commitment to the product Goal
The Product Backlog
and designs. backlog is: Sprint Goal The Product Goal is the long-
Definition
6. Enable face- 12. Regular The Sprint Goal is the single term objective for the Scrum
to-face intera‐ reflections on The Product Backlog is an
objective for the Sprint. Team. They must fulfill (or
ctions. how to emergent, ordered list of what is
Although the Sprint Goal is a abandon) one objective before
become more needed to improve the product.
commitment by the Developers. taking on the next.
effective. It is the single source of work
The sprint goal should be The Product Goal describes a
undertaken by the Scrum Team.
flexible enough in terms of the future state of the product which
The Sprint Backlog exact work that is needed to Product Backlog is: can serve as a target for the
Definition achieve. Emergent : Means that you add Scrum Team to plan against.
The Sprint Goal is created to it and change it over time as {{fa- circle}}The scrum team
It is a list of work that need to be
during the Sprint Planning event you inspect and adapt should use this goal to plan the
completed within the sprint.
and then added to the Sprint Ordered: Is ordered by priorities work to achieve this goal.
The Developers owns the Sprint
Backlog. and/or dependencies. Product Definition
Backlog
As the Developers work Single Source : Product Backlog
A product is a vehicle to deliver
during the Sprint, they keep the is the single source of work
value. It has a clear boundary,
Sprint Goal in mind. undertaken by the scrum team
known stakeholders, well-d‐
If the work turns out to be
The product owner owns the efined users, or customers. A
different than they expected,
product backlog product could be a service, a
they collaborate with the
physical product, or something
Product Owner to negotiate the
more abstract.
scope of the Sprint Backlog
within the Sprint without
affecting the Sprint Goal.
Key Points
Scrum Roles and Responsib‐ Developers (Developers & Developers (Developers & Daily Standup (cont)
ilities Testers) Testers) (cont)
It is held at the same time and
Role Accountable For: Key Points Creating a plan for the sprint, place every working day of the
Product The product Scrum teams are cross-fun‐ the sprint backlog sprint.
Owner owner(PO) is ctional. Instilling quality by adhering Is is a 15 minutes event for
accountable for Developers must be to a definition of done the Developers of the Scrum
maximizing the empowered and respected, they Adapting their plan each day Team.
value of the should be self-managed. They toward the sprint goal Developers are the only ones
product resulting are structured and empowered Holding each other accoun‐ are required.
from the work of to manage their own work. table as professionals. Developers can select
the scrum team. Developers are trusted to whatever structure and
manage themselves to complete Scrum Events techniques they want, but they
Developers Developers are
the work in the sprint backlog must focus on progress toward
(Devel‐ the people in the Daily Sprint Sprint Sprint
and holds themselves accoun‐ the sprint goal and produce and
opers & scrum team Standup Planning Review Retros
table for the success of the actionable plan for the next day
Testers) accountable for pective
sprint. of work.
create any aspect
Developers are also accoun‐ The Daily Scrum is not the
of a usable Daily Standup
table to internally decide who only time Developers are
increment each Definition
does what, when and how. allowed to adjust their plan. They
sprint. (Devel‐
The purpose of the daily scrum often meet throughout the day
opers and It is up to the developers as a
is to inspect progress toward the for more detailed discussions
Testers) self-managed team to create a
Sprint Goal and adapt the Sprint about adapting or re-planning
plan to complete the sprint goal
Scrum The scrum master Backlog as necessary, adjusting
(Sprint backlog). the rest of the Sprint’s work.
Master is accountable for the upcoming planned work.
If some of the developers are
the scrum team Daily Scrums improve commun‐
struggling with assigned work Sprint Planning
effectiveness. ications, identify impediments,
they need to help each other. Definition
They do this by promote quick decision-making,
Developers should meet the
enabling the Sprint Planning initiates the
and consequently eliminate the
Definition of Done for each task.
scrum team to Sprint by laying out the work to
need for other meetings.
They should adapt their plan
improve its be performed for the Sprint. This
During Daily Scrum you can
each day toward the sprint goal.
practices within resulting plan is created by the
answer this questions:
Developers should meet
the scrum collaborative work of the entire
1- What I did Yesterday.
every day at daily scrum.
framework. Scrum Team.
2- What I plan to do today.
There are no sub-teams or
3- What is Blocking me. Key Points
hierarchies, developers are a
cohesive unit of professionals. Key Points
Sprint Planning (cont) Sprint Planning (cont) Sprint Review Sprint Review (cont)
The Product Backlog must be Developers select items from Definition Inspect the outcome of the
refined. the Product Backlog to include The purpose of the Sprint Sprint and determine future
The whole Scrum Team is in the current Sprint. Review is to inspect the adaptations
required, that means that more The Scrum Team may refine outcome of the Sprint and To transparently inform about
than just the scrum team can be these items during this process, determine future adaptations. work which has been done
involved. which increases understanding The Scrum Team presents the (including adding work) and
The Scrum Team may also and confidence. results of their work to key work has not been done
invite other people to attend Selecting how much can be stakeholders and progress (including work removed).
Sprint Planning to provide completed within a Sprint may toward the Product Goal is Take advantage to receive
advice. be challenging. However, the discussed. feedback from the stakeholders
The Product Owner ensures more the Developers know and adapt.
Key Points
that attendees are prepared to about their past performance,
Scrum Team and stakeh‐
discuss the most important their upcoming capacity, and Product Owner
olders review what was
Product Backlog items and how their Definition of Done, the
Key Points
accomplished in the Sprint and
they map to the Product Goal. more confident they will be in
what has changed in their The Product Owner is a
Every participant must know their Sprint forecasts.
environment. value maximizer.
what the Sprint Goal is. 3- How will the chosen work get
Based on this information, Is accountable for effective
Sprint Planning results in a done?
attendees collaborate on what to product backlog management.
plan for the sprint, The Sprint
For each selected Product do next. Decides work tasks priority,
Backlog
Backlog item, Developers plan The Product Backlog may is accountable for ordering
Deciding the Sprint Goal the work necessary to create an also be adjusted to meet new product backlog items
The Scrum Team can decide the Increment that meets the opportunities. Must understand the market
sprint goal by considering the Definition of Done. The Sprint Review is a and the product to understand
following three topics during the Developers decomposed working session and the Scrum what makes a valuable product.
planning session: Product Backlog items into Team should avoid limiting it to a Accountable to clearly
1- Why is this Sprint valuable? smaller work items of one day or presentation. communicate the Product
2- What can be Done this less. Backlog Items.
Product Owner Role in the
Sprint? No one else tells the Accountable to ensure the
Sprint Review
3- How will the chosen work get Developers how to turn Product Product Backlog is Transparent,
Should be keeping on top of
done? Backlog items into Increments of visible and understood.
changes in the market place and
1- Why is this Sprint valuable? value. Represents the needs of
be ready to make decisions on
The Sprint Goal, the Product many stake holders in the
The Product Owner proposes how to maximize the value of the
Backlog items selected for the product backlog.
how the product could increase product.
Sprint, plus the plan for The Product Owner Vision is
its value and utility in the current
delivering them are together Goals called "The Product Goal"
Sprint.
referred to as the Sprint
Then, the whole Scrum Team The Product Goal
Backlog.
then collaborates to define a Is the Product Owner Vision, is a
Sprint Planning is timeboxed
Sprint Goal that communicates long term objective for the
to a maximum of eight hours for
why the Sprint is valuable. Scrum Team
a one-month Sprint. For shorter
The Sprint Goal must be
Sprints, the event is usually
finalized prior to the end of Sprint
shorter.
Planning.
2- What can be Done this
Sprint?
Key Points Helping find techniques for The purpose of the Sprint
The Scrum master is a effective product goal definition Retrospective is to plan ways to
servant leader, who serves the and product backlog manage‐ increase quality and effective‐
scrum team, the product owner ment. ness.
and the organization. How to decompose BLI to be The Scrum Team inspects how
The Scrum master is accoun‐ ready for the sprint. the last Sprint went with regards
table for stablishing scrum as Helping the scrum team to to:
defined in the scrum guide. They understand the need for clear individuals
do this by helping everyone to and concise product backlog Interactions
understand scrum theory and items. Processes
practice, both within the scrum Helping establish empirical Tools
team and the organization. product planning for a complex Definition of Done. {{nl}
The scrum master is accoun‐ environment. This event is a good chance
table for the scrum team effect‐ Facilitating stakeholder to add to the wealth and improve
iveness. They do this by collaboration as requested or the definition of done.
enabling the scrum team to needed Scrum Team discusses:
improve its practices within the Promote the inspection and
what went well during the
scrum framework. adaption opportunities for
Sprint
empirical product planning.
Scrum master serves the Scrum what problems it encountered
team by: Scrum master serves the how those problems were (or
organization by: were not) solved. Key Points
Coaching team members to
work together on the sprint goal Leading, training, and Key Points
through self management and coaching the organization in its
focus on How you are
cross-functionality. scrum adoption.
working as a team
Helping the scrum team focus Planning and advising scrum
The Scrum Team identifies
on creating high-value implementation within the
the most helpful changes to
increments that meet the organization.
improve its effectiveness.
definition of done. Helping employees and
Impactful improvements are
Encourage the scrum team to stakeholders understand and
addressed as soon as possible.
raise problems, discover any enact an empirical approach for
They may even be added to the
dependencies or impediments complex work.
Sprint Backlog for the next
and help to remove them finding Removing barriers between
Sprint.
solutions so the team can stakeholders and scrum team
The Sprint Retrospective
progress. concludes the Sprint.
Ensuring all scrum events Sprint Retrospective
happen are positive, productive Definition
and kept within the time box.
Scrum masters coach the
team on how to do scrum
properly.
Scrum master serves the
Product Owner by: