Artifacts Flashcards
What are the Comittments to each of the 3 Artifacts:
- Product Backlog
- Sprint Backlog
- Increment
Product Backlog => Product Goal
Sprint Backlog => Sprint Goal
Increment => Definition of Done
What is the Product Goal?
And where is it contained?
- describes a future state of the product which can serve as a target for the Scrum Team to plan against.
- stepping stones towards the Product Vision
Contained:
=> in the Product Backlog.
Could you have multiple Product Goals?
=> yes
but Scrum Team must focus on one Product Goal at a time
Who is responsible for developing and explicitly communicating the Product Goal?
=> the Product Owner
Can the Product goal be the Product itself?
No
What is the Product Backlog?
And name 2 Characteristics of it.
=> an ordered list of the work to be done in order to create, maintain and sustain a product. (pflegen & aufrechterhalten)
=> it is dynamic and emergent
Who manages the Product Backlog?
the Product Owner
Can there be more Product Backlogs per Product?
No
All the Product Backlog items are detailed.
True or False.
=> False
The Product Backlog follows „Just-in-time“ requirements
=> Only top Product Backlog items are detailed, the ones ready for the upcoming Sprint
(„ready“ => when it can be done in 1 Sprint)
not wasting time with the remaining ones
What do the Product Backlog items contain?
a description which might be using notations as EPICS and USER STORIES
(Eine Beschreibung, die als Epics oder User Stories notiert werden kann)
Why do we have just-in-time requirements?
because we expect things to change
What are Epics?
=> large Product Backlog items
(too large to fit a Sprint)
What are User Stories
(or bug descriptions)?
=> small refined items
that can be delivered whithin a Sprint
Name the 3 compenents of User Strories.
Card
* written description (from the perspective of a customer or user) of the functionality that will be valuable to them
* Usually they are written on paper cards
Conversation
* represents the collaboration between the PO and the developers (business & technical people)
Confirmation
* List of criteria, the Scrum Team will define to serve as a verification if the product delivered suits the needs
How is the Product Backlog ordered?
=> Scrum guide does not give details about how the Product Backlog should be ordered
=> therefore it can be ordered using whatever factors or techniques that the PO judges as appropriate
Name 4 widely used techniques/factors to order the Product Backlog.
- Size
- Risk
- Value
- Dependencies
Who is responsible for sizing the Product Backlog (Ordnen nach Größe)?
=> The Developers
since they are the ones who will transform the Product Backlog Item into part of a Definition of Done Increment
=> The PO may influence the Developers by helping them understand and select trade-offs, but only Developers estimate the Product Backlog Items
What is one of the most popular measure units to size the Product Backlog items in Agile?
And which Scale do you use?
=> Story point
(agile alternative to hours and days)
In Story they use a very particular scale: Semi-Fibonacci scale
1, 2, 3, 5, 8, 13, 20, 40, 100
What is Planning Poker?
=> Most used estimation technique to size Poduct Backlog Items
- each Developer has an deck of cards with the Semi-Fibonacci numbers
- the “rank” each Product Backlog item with their cards
- If everyone has the same estimate => perfect!
- if not they do another round, until consensus is reached
What is the Kano Model?
=> one technique to define the value for Product Backlog items
by classifying it into 1 of 3 categories:
* Mandatory
* Linear
* Exiter
What is the Product Backlog Refinemet?
=> Verfeinerung
- is the act of breaking down and further defining Product Backlog items into smaller more precise items (adding details, e.g. description order, size, …)
- to get them ready in the Timebox of one Scrum
Who does the refinement of the Product Backlog item?
The Scrum Team
What is the Definiton of “Ready”?
=> a set of criteria that defines when a Product Backlog Item is ready to be executed
Name the 3 default criteria of the Definition of “Ready”.
Usually we have at least these criteria (default):
- Acceptance criteria defined
- Team understands what has to be done
- Fit a sprint
Is the Definition of “Ready” a checklist?
=> No,
it is not a checklist or contract!!
=> it is more about a helpful guide for the product backlog refinement that may not always be achievable
=> Because it might becomes a gate that gets into the way of the Scrum Team, instead of supporting it
Is it okay for the Scrum team to attempt working on a Product Backlog item that is not 100% ready?
Yes
Name 3 practices for a Monitoring Progress towards goals.
- The Burn-Down Chart
- The Burn-Up Chart
- The Cumulative Flow Chart
What is the Burn-Down chart?
a chart which shows the amount of work which is thought to remain in a backlog
BUT
the amount of work (Story Points) can increase, what’s not visible in this chart
What is the Burn-Up chart?
a chart which shows the amount of work which has been completed
=> shows the work done by the team and also the amount of work to be done on the Product Backlog (scope Variation)
What is the Cumulative Flow chart?
a chart that shows the distribution of all Product Backlog items across various states over time
What is the Definition of Done?
=> defines what is needed for work to be considered done,
promoting transparency and visibility
What happens when a Product Backlog item meets the Definition of Done?
an Increment is born
What happens if a Product Backlog item does not meet the Definition of Done?
- can not be released
- can not presented at the Sprint Review
- returns to the Product Backlog for future consideration
What is the difference between the Definition of Done and the Acceptance Critera for User Stories?
The Acceptance Criteria are specific for one single user story
The Definition of Done englobes all of them.
Who defines the Definition of Done?
=> the organization
all Scrum Teams must follow it as a minimum
If the organization doesn’t have one, the Scrum Team must define an appropriate one for the product.
When is the Definition of Done defined?
=> is a continuous effort
because DoD might evolve,
(Adding, removing or editing the existing criteria whenever the organization or Scrum team feels like it is necessary)
=> might be a topic of discussion for Sprint retrospective meetings
If there are multiple Scrum Teams working together on a product, do they mutually define and comply with the same Definition of Done?
=> yes, they must!
When is an Increment developed?
during Sprints
When is an Increment born?
=> the moment a Product Backlog item meets the Definition of Done
Do Scrum Teams need to release the Increment at the end of each Sprint?
=> No
=> The Scrum team can release it whenever it feels like it is valuable
=> the Increment must be usable
Does the Scrum Team need to wait until the end of a Sprint, to release a version of the Increment?
=> No
=> The Scrum team can release it whenever it feels like it is valuable
=> the Sprint Review should never be considered a gate to releasing value
What is an Increment?
a usable Product,
something concrete users or stakeholders can use / have an authentic experience with to give quality feedback
Can multiple Increments be delivered in each Sprint?
yes
What is the Sprint Backlog?
=> is a real-time picture of the work that the Developers plan to accomplish during the Sprint, in order to achieve the Sprint Goal
=> is a plan by and for Developers
What is the Sprint Backlog composed (zusammengestellt) of?
- the Sprint Goal (WHY)
- the selected Product Backlog Items (WHAT)
- the plan for delivering the Increment (HOW)
What is fixed and what is flexible in the Sprint Backlog?
Sprint Goal
is defined during the Sprint Planning and remains the same throughout the Sprint
selectec PBIs & Plan
can change
As more is learned it is possible to change the work to be done (update the Sprint Backlog) during a Sprint, without affecting the Sprint Goal.
It should have enough detail that they can inspect their progress in the Daily Scrum.
What happens if the Developers need to change the Sprint Backlog?
=> If the work turns out different than Developers expected, they collaborate with the PO to negotiate the scope of the Sprint Backlog within the Sprint, without affecting the Sprint Goal.
What if someone else wants to change the Sprint Backlog?
=> The Sprint Backlog is by and for the Developers. No one can force them to change it.
If someone wants to change it, they need to talk to the PO, which will then have to negotiate with the Developers.
When is the Sprint Goal created?
during the Sprint Planning event
What are the Developers committed to?
The Developers commit to the Sprint Goal.
The Sprint Backlog is a forecast.
What is a technical dept?
the typically unpredictable overhead of maintaining the product, often caused by less than ideal design decisions, contributing to the total cost of ownership. May exist unintentionally in the Increment or introduced purposefully to realize value earlier.
