An agile team is working on a new product. To ensure that all unknown issues are clarified before committing to the scope, the team plans to work only on spike user stories for the next three sprints. What should an agile coach do in this situation?
A.
Ensure that the spikes identify the risks early in the project to increase the chances of success
B.
Ensure that the business sponsor accepts the proposal and agrees to fund the additional spike sprints
C.
Recommend that, in the first sprint, user stones with higher priority be executed in addition to the spike
D.
Support the decision, because release planning will be improved, and the product backlog can be better groomed after all spikes are executed
C. Recommend that, in the first sprint, user stories with higher priority be executed in addition to the spike
Explanation:
Balanced Approach: By executing high-priority user stories alongside spikes, the team can continue delivering value while addressing uncertainties.
Risk Mitigation: This approach allows the team to identify and mitigate risks early without halting the delivery of valuable features.
Stakeholder Confidence: Delivering high-priority user stories helps maintain stakeholder confidence and demonstrates progress.
Iterative Learning: Working on both spikes and user stories enables the team to iteratively learn and adapt, which is a core principle of agile methodologies.
focusing exclusively on spikes for three sprints may slow down overall progress. Balancing spikes with delivering features helps in managing both risks and value delivery simultaneously.
D. Support the decision, because release planning will be improved, and the product backlog can be better groomed after all spikes are executed.
In this situation, the agile coach should support the team's decision to work on spike user stories for the next three sprints. Spikes are used to explore and address unknowns, clarify requirements, and mitigate risks before committing to larger portions of work. By focusing on spikes initially, the team aims to improve release planning by gaining a better understanding of the project's complexities and risks.
--------
Option A is closely related to the benefits of using spikes to identify risks early, but it doesn't directly address the coach's role in this situation.
Option B refers to involving the business sponsor and funding, which might not be necessary if the team has already decided to work on spike stories.
Option C suggests mixing user stories with spikes in the first sprint, which could potentially dilute the focus on addressing unknown issues, which is the purpose of the spike-driven approach.
Why not D?
D. Support the decision, because release planning will be improved, and the product backlog can be better groomed after all spikes are executed
I don't thing agile coach can "ensure" anything
A. Ensure that the spikes identify the risks early in the project to increase the chances of success
Nevertheless, only solution C brings value to the customer. Working only on spike user stories for the next three sprints is a bad approach and practice - practically it is a waste.
Thus, I change to C.
PS: non of the offered choices are good options (in my opinion)
This section is not available anymore. Please use the main Exam Page.PMI-ACP Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
thewalker
8 months agoPuranDom
8 months, 1 week agoyassoraa88
8 months, 2 weeks agohankun
1 year, 8 months agoLucyPMI
1 year, 8 months agoPetrevski
1 year, 12 months agoPetrevski
1 year, 7 months agoMinhha3
2 years agoInvisibleBeing
2 years, 2 months ago