Discuss PMI PMI-PBA Exam Topic 1 Question 104

The project team is early in the development phase of a new product. The project will need to be completed on a tight timeline and with a lean budget.

What should the team do to reduce the risk of rework?

AAsk the project sponsor to prioritize the requirements.

BOrganize a new elicitation workshop.

CPerform a Pareto analysis on the requirements.

DValidate the requirements before continuing with development.

Suggested Answer: D

Validating the requirements is a key activity to reduce the risk of rework, especially for a project with a tight timeline and a lean budget. Validating the requirements means ensuring that they are aligned with the business needs, objectives, and expectations of the stakeholders, and that they are clear, complete, consistent, feasible, and testable.Validating the requirements can help the business analyst and the project team to identify and resolve any errors, gaps, conflicts, or ambiguities in the requirements before they are implemented, and to avoid any unnecessary changes or rework later in the project lifecycle.Reference: PMI Professional in Business Analysis (PMI-PBA) Examination Content Outline1, page 20; Business Analysis for Practitioners: A Practice Guide2, page 100.

Get Premium PMI-PBA Questions as Interactive Web-Based Practice Test or PDF Real Exam Format Detailed Explanations Instant Access Get Your Practice Test

32 comments · newest first

Audria 10 months ago

Validate the requirements first, no doubt about it.

Huey 10 months ago

I think a workshop could help too.

Elin 11 months ago

Prioritizing requirements is key!

Ettie 11 months ago

Wait, can we really avoid rework entirely?

Dannie 11 months ago

Pareto analysis sounds smart, but is it necessary?

Fatima 11 months ago

I’ve seen Pareto analysis used in similar scenarios, but I wonder if it’s really necessary at this early stage of development.

Elmer 12 months ago

Organizing a new elicitation workshop sounds like it could help clarify things, but I feel like it might add more time to the timeline we’re already tight on.

Kizzy 12 months ago

I remember a practice question where prioritizing requirements helped streamline the process, so option A might be a good choice too.

Pete 1 year ago

I think validating the requirements before continuing with development is crucial to avoid rework, but I'm not entirely sure if that's the best first step.

Kimberely 1 year ago

Validating the requirements is definitely the way to go here. With a tight timeline and lean budget, we need to make sure we get the requirements right the first time to avoid rework. I feel confident in this approach.

Yuette 1 year ago

I'm a little confused on this one. Should we organize a new elicitation workshop or just validate the requirements? I'll have to review the material again to make sure I understand the right strategy.

Mila 1 year ago

Okay, I've got this. The best approach is to validate the requirements before continuing with development. That way, we can catch any issues early on and avoid costly rework later.

Tonette 1 year ago

Hmm, I'm not sure. Prioritizing the requirements or doing a Pareto analysis could also help reduce rework. I'll have to think this through carefully.

Elza 1 year ago

This seems like a straightforward question about reducing rework in a project. I think the key is to validate the requirements before moving forward with development.

Fidelia 1 year ago

B) Organize a new elicitation workshop. Really? Didn't they just have one? Sounds like a waste of time and money to me.

Blondell 1 year ago

↳ replying to Fidelia

B) Organize a new elicitation workshop. Really? Didn't they just have one? Sounds like a waste of time and money to me.

Bulah 1 year ago

↳ replying to Fidelia

D) Validate the requirements before continuing with development.

Rocco 1 year ago

↳ replying to Fidelia

A) Ask the project sponsor to prioritize the requirements.

Ivette 1 year ago

I believe performing a Pareto analysis on the requirements could help us focus on the most critical ones and avoid unnecessary rework.

Nettie 1 year ago

I think organizing a new elicitation workshop could also help us gather more insights and reduce the risk of rework.

Antione 1 year ago

D) Validate the requirements before continuing with development. Yep, that's the way to go. Can't afford any surprises down the line, am I right?

Nenita 1 year ago

A) Ask the project sponsor to prioritize the requirements. Sounds like a no-brainer to me. Gotta keep the big boss happy, you know?

An 1 year ago

↳ replying to Nenita

B) Organize a new elicitation workshop.

Loreta 1 year ago

↳ replying to Nenita

A) Ask the project sponsor to prioritize the requirements.

Leonora 1 year ago

I agree with Elza. It's important to make sure we are on the right track early on.

Domonique 1 year ago

C) Perform a Pareto analysis on the requirements. Gotta focus on the vital few, not the trivial many. Efficiency is the name of the game here.

Melina 1 year ago

↳ replying to Domonique

D) Validate the requirements before continuing with development.

Josephine 1 year ago

↳ replying to Domonique

A) Ask the project sponsor to prioritize the requirements.

Elza 1 year ago

I think we should validate the requirements before continuing with development.

Bernardine 1 year ago

D) Validate the requirements before continuing with development. This is key to reducing rework. Skipping this step is a recipe for disaster!

Brett 1 year ago

↳ replying to Bernardine

D) Validate the requirements before continuing with development. This is key to reducing rework. Skipping this step is a recipe for disaster!

Frankie 1 year ago

↳ replying to Bernardine

A) Ask the project sponsor to prioritize the requirements.

PMI-PBA Exam - Topic 1 Question 104 Discussion