Scrum User Stories

Correct Answer: Consider the User Story as not 'Done', discuss the issues in the retrospective and include the bugs in the Product Backlog.

The best solution from a Scrum perspective is to consider the User Story as not 'Done', discuss the issues in the retrospective, and include the bugs in the Product Backlog. This handling is in concordance with the foundational principles of Scrum, i.e., transparency and improvement. The retrospective is there for the team to learn and adapt, and if there were critical bugs discovered during user acceptance testing, this symptom points to a problem in their 'definition of done' or testing strategy that should be addressed. Simply ignoring the bugs, because the User Story is already marked as complete, is not a correct approach. It can lead to accumulation of technical debt, and it violates the principles of transparency and continuous improvement. Delaying the Sprint Review until all problems are resolved is also incorrect, Scrum encourages learning from inspecting the increments as they are. Requesting the Product Owner to accept the User Story and create a new User Story for the bug fixing can mislead the tracking of the development progress and is not recommended either.

Correct Answer: Confirm that the user story meets the INVEST criteria and has clear acceptance criteria defined.

The best way to ensure a user story is ready for development during sprint planning is to confirm that it meets the INVEST criteria (Independent, Negotiable, Valuable, Estimable, Small, Testable) and has clearly defined acceptance criteria. This ensures the story is well-understood, properly scoped, and can be completed within the sprint. Assigning it to the most experienced developer doesn't guarantee it will be done quickly and may create a bottleneck. Breaking it down into detailed technical tasks is more appropriate during sprint planning, not for determining if the story is ready. Having the Product Owner explain the business value and priority is important, but not sufficient on its own to confirm the story is ready for development.

Correct Answer: The team should discuss the new user story during the next sprint planning meeting and consider it for the upcoming sprint.

In Scrum, the sprint backlog is fixed once the sprint begins. The team commits to completing the user stories in the sprint backlog during the sprint planning meeting. Adding a new high-priority user story mid-sprint would disrupt the team's focus and commitment. The best approach is to discuss the new user story during the next sprint planning meeting and consider it for the upcoming sprint. This allows the team to maintain their focus on the current sprint goals while ensuring that the new high-priority story is properly planned and estimated before being added to a future sprint.