Holding a Sprint 0 is the most effective way to: (Choose the best answer)
'Sprint 0' is a concept from pre-Scrum practices and isn't part of the official framework. The Scrum Guide mandates that Sprints deliver value: 'A Sprint is a time-box of one month or less during which a 'Done', usable, and potentially releasable product Increment is created.' A preparatory 'Sprint 0' for architecture, team building, or backlog creation contradicts this by not producing an Increment.
A, B, C: These may occur outside Sprints, but not as a 'Sprint 0.'
D: Correct---Scrum has no such event.
Exact Extract from Scrum Guide: 'Each Sprint may be considered a short project... There is no gap between Sprints.' (Section: 'Sprint')
Thus, D is correct.
What three factors are best considered when establishing the Sprint length? (Choose the best three answers)
Sprint length in Scrum is a critical decision that impacts the team's ability to deliver value and adapt. The Scrum Guide states that Sprints are fixed in length (typically one month or less) to create consistency and enable regular inspection and adaptation. While it doesn't explicitly list factors, practical application and Scrum principles suggest:
A (The ability to go to market with a product release): Shorter Sprints allow faster feedback and releases, aligning with Scrum's focus on delivering value frequently.
D (The level of uncertainty over the technology to be used): High uncertainty may warrant shorter Sprints to mitigate risk and validate assumptions, a key aspect of empirical process control.
E (The risk of being disconnected from the stakeholders): Shorter Sprints ensure frequent stakeholder engagement (e.g., via Sprint Reviews), reducing this risk.
Option B is incorrect because Scrum does not require uniform Sprint lengths across an organization---each team can choose what works best. Option C is irrelevant, as team formation changes are not tied to Sprint length in Scrum. Thus, A, D, and E are the best factors.
True or False: The Scrum Master is a participant in the Sprint Retrospective.
The Sprint Retrospective is an event for the entire Scrum Team, including the Scrum Master, to inspect and improve their processes. The Scrum Guide explicitly states that the Scrum Master participates as a peer: 'The Scrum Master participates as a peer team member in the Sprint Retrospective from the accountability over the Scrum Team's effectiveness.' This ensures a collaborative review of the Sprint, including the Scrum Master's facilitation role.
A: True---the Scrum Master is a full participant.
B: False---exclusion contradicts Scrum's team focus.
Exact Extract from Scrum Guide: 'The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint... The Scrum Master participates as a peer team member in the Sprint Retrospective from the accountability over the Scrum Team's effectiveness.' (Section: 'Sprint Retrospective')
Thus, A is correct.
Who assigns ownership of the Sprint Backlog items during the Sprint? (Choose the best answer)
The Sprint Backlog is collectively owned by the Developers, not assigned to individuals. The Scrum Guide defines it as: 'The Sprint Backlog is a plan by and for the Developers... It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint.' Self-organization means the Developers decide who does what, without fixed ownership of items.
A, B: Individual assignment isn't mandated; it's a team effort.
C: Correct---the Developers as a whole own it.
D: The Product Owner manages the Product Backlog, not the Sprint Backlog.
Exact Extract from Scrum Guide: 'The Sprint Backlog is a plan by and for the Developers. It is composed of the Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), as well as an actionable plan for delivering the Increment (how).' (Section: 'Sprint Backlog')
Thus, C is correct.
True or False: Scrum mandates the use of burndown charts.
Scrum does not mandate specific tools like burndown charts; it focuses on outcomes (e.g., a 'Done' Increment) rather than prescriptive practices. The Scrum Guide mentions progress tracking as optional: 'Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism.'
A: False---burndown charts are optional.
B: Correct---no mandate exists.
Exact Extract from Scrum Guide: 'Various practices exist to forecast progress, like burn-downs, burn-ups, or cumulative flows. While proven useful, these do not replace the importance of empiricism. In complex environments, what will happen is unknown.' (Section: 'Scrum Artifacts')
Thus, B is correct.
Michal
3 days agoLynelle
14 days agoRosendo
28 days agoTheron
1 months ago