5. Scrum Artifacts

Question 1

1. The product backlog

Answer 1

Ordered list of everything that is known to be needed in the product. Can change over time, living element connected to the product. Single source of requirement for any changes to the product. PO accountable for product backlog, can delegate, but still accountable.

Product backlog items can have attributes, like description, order, size, etc

You might consider adding acceptance criteria.

Based on empiricism, the product is changed and adapted through user feedback.

Question 2

What are three scrum Artifacts?

Answer 2

1. Product Backlog (PO, monitor progress towards product goal)
2. Sprint Backlog (Developers, monitor progress sprint goal)
3. The increment

All create commitment. Maximize transparency!

• Decisions to optimize value and control risk are made based on the perceived state of the artifacts
• Understanding what work has been done and what is left to do
• So you can make decisions on optimizing value and how to reduce or eliminate risk

The scrum artificats must be inspected frequently to detect undesirable variances or problems

Based on inspection, enabling adaption

Scrum events are designed to provoke change and adaption

Question 3

What is Product Backlog refinement?

Answer 3

Product backlog refinement is the act of breaking down and further defining Product backlog items into smaller precise items, one sprint

Scrum team breakdown and add details, ongoing activity
- Detail - who, why, what, user stories
- Ordering - highest prio top
- Size - Effort, time, value - decided by developers

This is done in the previous sprint or during the sprint. Product backlog refinement is ongoing and happens throughout the sprints.
Each Backlog items should be Achievable in one sprint

Responsibility for its content, availability and ordering lies with the Product Owner

Question 4

What is Definition of Done?

Answer 4

A formal description of the state of the increment when it meets the quality measures required for the product

• Everyone must understand and agree what “Done” means
• “Done” should cover integration with the product
• As scrum team matures, the DoD expands to include more criteria for higher quality
• If “Done” for an increment is part of the conventions, standard or guidelines of the organization, all scrum Teams must follow it as a minimum, otherwise the Scrum team defines DoD for the product

Everyone must understand and agree what “done” means, important for transparency. Defines the standards.

Have common standard for all work items, this might include conventions, standards or guidelines for the organization

Definition of done is a quality commitment to the increment

Made by Scrum team

Question 5

2. The sprint backlog

Answer 5

Work items from backlog chosen to be in this sprint via sprint planning session, decided by scrum team

Sprint backlog items become a plan for delivering the product increment and realizing the sprint Goal

A forecast by the scrum Team as to what functionality will be in the next increment,
and what works needs to be completed to deliver that increment

The sprint backlog also includes… improvement that became clear after previous Sprint retrospective. These could be added in upcoming sprint.

goal

The Sprint Backlog is a highly visible, real-time picture of the work that developers plan to accomplish during the Sprint. The daily Scrum is a chance to discuss the Sprint Backlog. Sprint backlog is thus a way of monitoring progress. You can check whether you’re able to achieve the sprint goal, by the remaining work estimates and the time available. developers responsible to achieve sprint goal. Velocity of work → actual time used to finish items. Estimates are very hard in practice. Sprint backlog flexible, focus on sprint goal, not on finishing all sprint backlog items.

Question 6

3. The increment

Answer 6

The increment is a step toward a vision or goal. An additive to previous increments.

All increments should work together

Sprint goal = to produce at least one increment

Multilple increments maybe released in one sprint, even before The Sprint Review (Which should not be a gateway to release), you dont have to wait for sprint review to release. Not a bottleneck for realising. releasing more increments satisfies the need to deliver software early to customers and continuously.

It needs to meet the agreed “Definition of Done”
“the moment a Product Backlog item meets the Definition of Done, an Icrement is born.