One of the teams you manage has committed to delivering 45 story points for this Sprint, but it looks like they will only complete 25. As an Agile Manager, what should you do?
One of the teams you manage has committed to delivering 45 story points for this Sprint, but it looks like they will only complete 25. As an Agile Manager, what should you do?
A . Coach the team to identify a set of User Stories that sum up 25 story points and will meet the Sprint Goal.
B. Ask Developers to work overtime.
C. Add more Developers to the team.
D. Be transparent and remove 20 points from Sprint Backlog. The remaining 20 points can be completed in the next Sprint.
E. Extend the Sprint.
Answer: A
Explanation:
Sprints are ‘fixed length’ events of one month or less to create consistency. During the Sprint: No changes are made that would endanger the Sprint Goal; Quality does not decrease; The Product Backlog is refined as needed; and, Scope may be clarified and renegotiated with the Product Owner as more is learned. The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. As the Developers work during the Sprint, they keep the Sprint Goal in mind. If the work turns out to be different than they expected, they collaborate with the Product Owner to negotiate the scope of the Sprint Backlog within the Sprint without affecting the Sprint Goal.
Latest PAL-I Dumps Valid Version with 305 Q&As
Latest And Valid Q&A | Instant Download | Once Fail, Full Refund