Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

PMI-ACP Exam - Topic 9 Question 94 Discussion

Actual exam question for PMI's PMI-ACP exam
Question #: 94
Topic #: 9
[All PMI-ACP Questions]

A learn using Kanban identifies mat their cycle time has significant variation After brainstorming, the team determines that the root cause is the stones' varying sizes and risks What should the team do?

Show Suggested Answer Hide Answer
Suggested Answer: C

by Nobuko at Dec 11, 2024, 08:06 AM

Limited Time Offer

25%

Off

Get Premium PMI-ACP Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Joanne
5 months ago
Definitely need to address those varying sizes directly!
upvoted 0 times
...
Eliseo
5 months ago
Overflow swimlane sounds like a band-aid solution to me.
upvoted 0 times
...
Long
5 months ago
Surprised that breaking down stories isn't the first choice!
upvoted 0 times
...
Luz
5 months ago
Nah, I prefer creating a triage step instead.
upvoted 0 times
...
Sylvia
6 months ago
I think reducing WIP limits is a solid move.
upvoted 0 times
...
Owen
6 months ago
The idea of an overflow swimlane sounds familiar, but I’m not convinced it addresses the root cause of the cycle time variation effectively.
upvoted 0 times
...
Gladys
6 months ago
I feel like breaking down larger stories is a common strategy we practiced, but I can't recall if we ever set a specific complexity threshold.
upvoted 0 times
...
Marvel
6 months ago
I think creating a triage step could help us identify risky stories early on, but I wonder if it might complicate our workflow too much.
upvoted 0 times
...
Shaquana
6 months ago
I remember we discussed how reducing WIP limits can help manage risks, but I'm not sure if that's the best approach here.
upvoted 0 times
...
Noel
6 months ago
This is a good one. I think option C is the way to go - setting a policy to break down larger stories and then adjusting the WIP. That should help smooth out the cycle time variation.
upvoted 0 times
...
Caitlin
6 months ago
I'm a bit confused by the options. Reducing WIP limits or creating a triage step don't seem like they'd directly address the root cause. I'm going to go with option C - it seems the most logical approach.
upvoted 0 times
...
Eric
6 months ago
Okay, I think I've got it. The team should create a policy to break down stories that are too large, and then adjust the WIP limits accordingly. That seems like the best way to manage the varying story sizes.
upvoted 0 times
...
Daniel
6 months ago
Hmm, the key seems to be addressing the root cause of the cycle time variation. I'm leaning towards option C - breaking down larger stories to reduce complexity.
upvoted 0 times
...
Ciara
7 months ago
This is a tricky one. I'm not sure if I fully understand the question, but I think it's asking about how to handle varying story sizes and risks in a Kanban process.
upvoted 0 times
...
Ira
12 months ago
Breaking down stories? Sounds like they're trying to put humpty dumpty back together again. But hey, at least it's not as bad as trying to herd cats!
upvoted 0 times
Elke
11 months ago
C: Setting a policy to break down larger stories and adjusting the WIP might be a good solution.
upvoted 0 times
...
Malika
11 months ago
B: I think creating a triage step on the Kanban board to pre-identify risky stones could help.
upvoted 0 times
...
My
12 months ago
A: Let's reduce work in progress limits to accommodate slack for riskier stories.
upvoted 0 times
...
...
Adelina
12 months ago
Option A sounds tempting, but reducing the WIP limits might just lead to a whole new set of problems. Better to address the root cause, like the team is doing.
upvoted 0 times
...
Adria
12 months ago
Option D is intriguing, but I'm not sure creating a separate swimlane is the best solution. Seems like an unnecessary complication to the process.
upvoted 0 times
...
Meaghan
1 year ago
I'm leaning towards Option B. Having a triage step to identify the risky stories upfront could be a game-changer. Proactive planning is key here.
upvoted 0 times
Ocie
11 months ago
I agree, being proactive in identifying risky stories can definitely help improve our cycle time.
upvoted 0 times
...
Providencia
12 months ago
Option B sounds like a good idea. It can help us catch potential issues early on.
upvoted 0 times
...
...
Ruby
1 year ago
Option C seems like the way to go. Breaking down the larger stories and adjusting the WIP accordingly should help manage the variation in cycle time.
upvoted 0 times
Wilda
12 months ago
Creating a dedicated overflow swimlane could also be a good idea to handle the larger stones.
upvoted 0 times
...
Sherly
12 months ago
We should also consider setting a policy to adjust the WIP limits accordingly.
upvoted 0 times
...
Linn
12 months ago
I agree, breaking down the larger stories will definitely help in managing the cycle time.
upvoted 0 times
...
Sanda
12 months ago
Option C seems like the best solution to address the varying sizes and risks.
upvoted 0 times
...
...
Asha
1 year ago
I'm not sure about option C. Maybe we should consider option B as well to pre-identify risky stones.
upvoted 0 times
...
Kathrine
1 year ago
I agree with Cletus. Option C seems like a practical solution to address the root cause of the variation.
upvoted 0 times
...
Cletus
1 year ago
I think we should go with option C. Breaking down larger stories can help reduce variation in cycle time.
upvoted 0 times
...

Save Cancel