What may be included in the Sprint Backlog?
(choose all that apply)
The Sprint Backlog is the Developers' plan for the Sprint. According to the 2020 Scrum Guide, the Sprint Backlog is composed of:
The Sprint Goal
The Product Backlog Items selected for the Sprint
An actionable plan for delivering the Increment
Because Scrum does not prescribe a specific format for Product Backlog Items or for the detailed plan inside the Sprint Backlog, several kinds of items may appear there.
Why A is correct -- User Stories:
Scrum does not require User Stories, but if the selected Product Backlog Items are written as User Stories, then they may be included in the Sprint Backlog. User Stories are a common technique, not a Scrum requirement.
Why B is correct -- Tests:
Tests may absolutely be part of the actionable plan for delivering an Increment. If testing work is needed to meet the Definition of Done, it can be represented in the Sprint Backlog.
Why C is correct -- Tasks:
Tasks are a common way Developers break down work in the Sprint Backlog. Scrum does not require tasks, but they may be used as part of the Developers' plan.
Why D is correct -- Additional decomposition items:
This is directly aligned with Scrum thinking. The Sprint Backlog may contain additional items that decompose the selected Product Backlog Items into actionable work.
Why E is correct -- Use Cases:
Like User Stories, Use Cases are not required by Scrum, but they may be used if that is how the team expresses selected Product Backlog Items or supporting detail for Sprint work.
Key Scrum point:
Scrum defines the purpose and content of the Sprint Backlog, but it does not force teams to use only one documentation style. Therefore, all of these items may be included.
2020 Scrum Guide -- Sprint Backlog: https://scrumguides.org/scrum-guide.html#sprint-backlog
2020 Scrum Guide -- Sprint Planning: https://scrumguides.org/scrum-guide.html#sprint-planning
===========
Which of the following might the Scrum Team discuss during a Sprint Retrospective?
(choose the best answer)
According to the Scrum Guide, the purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness.The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done1. Therefore, all of the options A, B, C, and D are possible topics that the Scrum Team might discuss during a Sprint Retrospective, as they relate to the aspects that the team can improve or adapt.For example, the team might discuss how to communicate better, how to plan the Sprint more effectively, how to acquire new skills or knowledge, or how to update their Definition of Done23.The Sprint Retrospective is a formal opportunity for the team to focus on inspection and adaptation, and to identify the most helpful changes to implement in the next Sprint1.
Who determines when it is appropriate to update the Sprint Backlog during a Sprint?
In Scrum, the Sprint Backlog is a living artifact that evolves throughout the Sprint as the team gains new insights. The responsibility of updating the Sprint Backlog lies exclusively with the Developers, as they are the ones executing the work.
Roles and Responsibilities:
Developers:
They are solely responsible for creating, managing, and updating the Sprint Backlog.
They continuously update it as they learn more about the work needed to achieve the Sprint Goal.
Any changes, additions, or deletions to the Sprint Backlog are determined by the Developers based on new information.
Product Owner:
The Product Owner is responsible for managing the Product Backlog, not the Sprint Backlog.
However, they collaborate with Developers if the scope of the Sprint Backlog needs renegotiation.
They prioritize product value but do not directly modify the Sprint Backlog.
Scrum Team:
The term Scrum Team includes the Developers, Product Owner, and Scrum Master.
While they collaborate, only the Developers make changes to the Sprint Backlog.
Project Manager:
Scrum does not define a Project Manager role.
Traditional project management responsibilities are distributed across the Scrum roles.
The Developers are self-organizing, meaning they do not need external direction to update their plan.
Key Scrum Guide Principles Supporting This:
The Sprint Backlog is a plan by and for the Developers.
The Developers own and manage their work throughout the Sprint.
The Sprint Backlog is adapted daily to reflect progress toward the Sprint Goal.
No one else, including the Product Owner or Scrum Master, is allowed to modify the Sprint Backlog.
Conclusion:
Only the Developers have the authority to update the Sprint Backlog during a Sprint. This ensures that they maintain ownership of their work and adapt as necessary to successfully achieve the Sprint Goal.
What typically happens if Product Backlog items are not sufficiently clear during Sprint
Planning?
(choose the best answer)
If Product Backlog items are not sufficiently clear during Sprint Planning, the Developers will typically have difficulty creating a forecast of work for the Sprint (B). This is because the clarity of the Product Backlog items is crucial for the Developers to understand what is expected and to plan their work accordingly.The Scrum framework emphasizes the importance of a well-refined Product Backlog for effective Sprint Planning
Who owns the Sprint Backlog?
(choose the best answer)
Self-Management:The Developers have autonomy over how they achieve the Sprint Goal. The Sprint Backlog reflects their plan for turning Product Backlog items into a valuable Increment.
Accountability:The Developers are held accountable for delivering the Sprint Goal, and thus own the detailed plan within the Sprint Backlog.
Scrum Guide:The Scrum Guide explicitly states, 'The Sprint Backlog is a plan by and for the Developers'
Deborah Nguyen
5 days agoCrystal Davis
26 days agoDennis Perez
1 month agoDorothy Thompson
2 months agoAndrew Reed
2 months agoJeffrey Mitchell
3 months agoMaria Flores
3 months agoJason Gonzalez
4 months agoWilliam Bailey
4 months agoNathan Rivera
5 months agoJeffrey Williams
5 months agoMark Rogers
5 months agoPaul Gonzalez
5 months agoMatthew Allen
5 months agoJohn Martinez
5 months agoAnthony Rogers
5 months agoMa
6 months agoIvette
6 months agoCassie
6 months agoBronwyn
7 months agoMaryanne
7 months agoTracey
7 months agoStephaine
8 months agoTuyet
8 months agoShay
8 months agoVelda
8 months agoVirgina
8 months agoGilma
9 months agoMicah
9 months agoMitsue
9 months agoNaomi
9 months agoReena
10 months agoRodney
10 months agoLashonda
10 months agoLyla
10 months agoArlene
11 months agoMarshall
11 months agoScot
11 months agoJaleesa
12 months agoIvette
12 months agoClement
12 months agoStefany
1 year agoBulah
1 year agoJacquelyne
1 year agoFrance
1 year agoMoira
1 year agoHayley
1 year agoMarge
1 year agoGaston
1 year agoGoldie
1 year agoLinsey
1 year agoKeneth
1 year agoFlorinda
1 year agoLettie
1 year agoCatalina
2 years agoFloyd
2 years agoPura
2 years agoJolene
2 years agoSol
2 years agoFlo
2 years agoBlythe
2 years agoNaomi
2 years agoTiera
2 years agoTruman
2 years agoBrunilda
2 years agoUlysses
2 years agoKathrine
2 years agoElfrieda
2 years agoTamesha
2 years agoChaya
2 years agoGoldie
2 years agoNorah
2 years agoKristal
2 years agoIsabella
2 years agoStevie
2 years agoThurman
2 years agoMarnie
2 years agoHermila
2 years agoLavonda
2 years agoAsha
2 years agoRomana
2 years agoGussie
2 years agoBrunilda
2 years agoCarmela
2 years agoRaina
2 years agoPeggie
2 years agoHan
2 years agoLayla
2 years agoRia
2 years agoGilma
2 years agoBlair
2 years ago