An agile team has been given a complex project with a basic set of requirements which need further elaboration and review. How should the team iteratively build out the backlog of requirements with the stakeholders?
Suggested Answer: C
Get Premium PMI-ACP Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
34 comments · newest first
JA
Jaime
11 months ago
Definitely not D, that could lead to a lot of misunderstandings.
VA
Valentine
11 months ago
Wait, stakeholders filling out the backlog before starting? That seems risky!
AS
Ashlee
12 months ago
Not sure about option C, the product owner shouldn't do it alone.
RE
Reita
12 months ago
I think delivering the basic requirements iteratively is the way to go.
BE
Belen
1 year ago
A requirements gathering workshop sounds like a solid plan!
HA
Harrison
1 year ago
I recall a practice question where we emphasized collaboration, so I think A could be the right choice for gathering requirements effectively.
AI
Aimee
1 year ago
I feel like option C might not be the best since the product owner shouldn't do it alone; we need stakeholder input too.
CO
Colette
1 year ago
I’m not entirely sure, but I think delivering iteratively, like in option B, helps refine requirements as we go.
JU
Judy
1 year ago
I remember we discussed the importance of involving stakeholders throughout the process, so maybe A or B could be good options.
SO
Son
1 year ago
Option C - having the product owner fill out the requirements backlog - seems like the easiest solution. But I'm not sure if that would really engage the stakeholders enough. I'll have to think this through carefully.
VE
Vernell
1 year ago
Hmm, I'm a bit unsure about this one. Option B seems reasonable, but I'm not sure if that's the best approach for a complex project. Maybe I should review the agile principles again before deciding.
AL
Alease
1 year ago
This seems like a classic agile scenario. I'd probably go with option A - a requirements gathering workshop. That way we can get the stakeholders involved early and iteratively build out the backlog.
HU
Hubert
1 year ago
I think the key here is to involve the stakeholders as much as possible. Option A, the requirements gathering workshop, seems like the best way to do that. It'll take some work, but it's probably the most effective approach in the long run.
DA
Daron
1 year ago
Hmm, I'm a bit unsure about this one. I'm not sure if the Activity Stream or Labels would be as helpful as the other options. I'll need to think it through carefully.
PA
Paul
1 year ago
Hmm, I'm a bit unsure about the difference between agent-based and GRT-enabled backups. I'll need to review that to determine the invalid scenarios.
AL
Alishia
1 year ago
Okay, let me see. The company is shipping bulk product from Asia to Europe, so they'd want to find the most efficient and cost-effective way to transport it. I'm leaning towards B, last mile delivery, but I'm not 100% confident.
MA
Mary
1 year ago
You know, I heard the last team that tried option D ended up with a backlog that was longer than War and Peace. I'm going with B - iterative development is the way to go, especially for a complex project. And it's the only option that doesn't involve me having to decipher the stakeholders' hieroglyphics.
SH
Sheron
1 year ago
I'm torn between B and C. As a product owner, I'd love to just fill out the backlog myself, but I know that's a recipe for disaster. Maybe I'll just hire a skywriter to spell out the requirements and hope the stakeholders get the hint.
BU
Buck
1 year ago
I'm torn between B and C. As a product owner, I'd love to just fill out the backlog myself, but I know that's a recipe for disaster. Maybe I'll just hire a skywriter to spell out the requirements and hope the stakeholders get the hint.
KE
Kelvin
1 year ago
C) Have the product owner fill out the requirements backlog.
MI
Mignon
1 year ago
B) Deliver the basic requirements iteratively.
AR
Aretha
1 year ago
A) Conduct a requirements gathering workshop.
CA
Carline
1 year ago
Definitely B. Agile is all about iterating and adapting, not trying to get everything set in stone from the beginning. Plus, I hear the stakeholders can get a little, shall we say, 'creative' with their requirements. Better to take it one step at a time.
LO
Lonna
1 year ago
D seems like a good option, but I'm worried the stakeholders might not have a complete understanding of the project at the start. I'd go with B to stay agile and responsive to changes.
HO
Hoa
1 year ago
C) Have the product owner fill out the requirements backlog.
CA
Cassi
1 year ago
B seems like a good option to keep the project moving forward.
LA
Lashandra
1 year ago
B) Deliver the basic requirements iteratively.
LA
Latricia
1 year ago
A) Conduct a requirements gathering workshop.
BR
Brett
2 years ago
I think the answer is B. Delivering the basic requirements iteratively allows the team to gather feedback and refine the backlog as they go, which is crucial for a complex project with evolving requirements.
CE
Cecilia
2 years ago
B) Deliver the basic requirements iteratively.
HE
Herschel
2 years ago
A) Conduct a requirements gathering workshop.
TA
Tammi
2 years ago
I believe having the product owner fill out the requirements backlog is the best approach.
KE
Keith
2 years ago
I agree with Val, getting input from stakeholders is crucial.
VA
Val
2 years ago
I think we should conduct a requirements gathering workshop.