A team using Kanban identifies that their cycle time has significant variation. After brainstorming, the team determines that the root cause is the stories' varying sizes and risks. What should the team do?
A.
Reduce work in progress (WIP) limits to accommodate slack for riskier stories
B.
Create a triage step on the Kanban board to pre-identify risky stories
C.
Set a policy to break down stories larger than a specified complexity, then adjust the WIP
D.
Create a dedicated overflow swim lane on the Kanban board for stories that are too large
Option C.
Set a policy to break down stories larger than a specified complexity, then adjust the WIP. This aligns with the Agile principle of "Simplicity" and the Kanban practice of "Visualize Workflow." By setting a policy to break down larger stories into smaller ones, the team can reduce variation in cycle time and increase the predictability of their workflow. This approach also enables the team to better manage risk by breaking down complex stories into smaller, more manageable tasks. After establishing the policy, the team can adjust their WIP limits to reflect the new, smaller stories' capacity.
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.
zvasanth1
Highly Voted 4 years, 3 months agoNervys
Most Recent 11 months agoImrangoshi
1 year, 2 months agoMinhha3
1 year, 7 months agoPetrevski
1 year, 8 months agoSmokeyofficiial
1 year, 8 months agoInvisibleBeing
1 year, 10 months ago7029
1 year, 10 months ago