Discuss IIBA CCBA Exam Topic 1 Question 110

Requirements have been prioritized in the product backlog for inclusion in the upcoming release. One of the project team members fears that at least one requirement from the prioritization list is not finalized and still requires further analysis. Which of the following factors describe the affected requirement?

ABenefit

BDependency

CStability

DRisk

Suggested Answer: C

Stability is the factor that describes the affected requirement, as it indicates the likelihood of the requirement remaining constant and static. Requirements that are not stable or whose definition changes frequently are given a lower priority to minimize recurrence, rework, and time and resource waste.Reference: Please refer to the CCBA guide and other official IIBA resources for specific references and detailed explanations. You can also check out the following web search results for more guidance:

Five Requirements Prioritization Methods - Business Analyst Articles ...

What Are Requirement Prioritization Techniques? - Techcanvass

5 Popular Requirements Prioritisation Techniques - The Business Analyst ...

How to prioritize requirements -- The Functional BA

An Overview of Requirements Prioritization > Business Analyst Community ...

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

39 comments · newest first

Benton 10 months ago

Dependencies could also play a role in this situation.

Jordan 11 months ago

I think it’s more about risk management here.

Veronika 11 months ago

Wait, how can a requirement be prioritized if it’s not finalized?

Izetta 11 months ago

I agree, risk is a big factor in prioritization.

Casandra 11 months ago

Definitely a stability issue if it's not finalized.

Karma 12 months ago

I recall a practice question where benefit was mentioned, but it seems more about the value rather than the requirement's status.

Deja 12 months ago

I think risk is definitely a factor here, especially if there's uncertainty about the requirement's impact on the project.

Nicholle 1 year ago

I'm not entirely sure, but I feel like dependencies could also play a role if the requirement isn't fully analyzed yet.

Jesusa 1 year ago

I remember we discussed how stability is crucial for finalized requirements, so I think that might be the right answer.

Jaime 1 year ago

I've got this! The affected requirement is likely one that has a high dependency on other parts of the system, or maybe it's a less stable requirement that's still being finalized.

Fidelia 1 year ago

Okay, let's see. The question is asking about the factors that describe the affected requirement, so I'll need to consider things like dependencies, stability, and risk.

Izetta 1 year ago

Hmm, I'm a bit unsure about this one. I need to carefully read through the options and think about which factors could be causing issues with the requirement.

Darnell 1 year ago

This question seems straightforward. I'll focus on identifying the key factors that describe the affected requirement.

Raymon 1 year ago

B. Dependency, all the way. Can't have a house of cards, am I right? Or as my grandma used to say, 'You can't build a skyscraper on a foundation of jello.'

Muriel 1 year ago

I'm going with C. Stability. Gotta make sure that requirement is rock-solid, or else it's going to be a real roller coaster ride!

Elden 1 year ago

↳ replying to Muriel

D) Risk

Skye 1 year ago

↳ replying to Muriel

C) Stability

Mari 1 year ago

↳ replying to Muriel

B) Dependency

Abraham 1 year ago

↳ replying to Muriel

A) Benefit

Ulysses 1 year ago

D. Risk, for sure. Better to play it safe and iron out any potential issues before rolling it out.

Arlette 1 year ago

↳ replying to Ulysses

D) Risk

Geraldine 1 year ago

↳ replying to Ulysses

C) Stability

Dorethea 1 year ago

↳ replying to Ulysses

B) Dependency

Candida 1 year ago

↳ replying to Ulysses

A) Benefit

Lezlie 2 years ago

Ah, I see what you mean. B. Dependency sounds like the culprit here. Can't have one part of the system relying on something that's not ready yet.

Anthony 1 year ago

↳ replying to Lezlie

User 3: It's risky to have unfinished dependencies in the mix.

Kenda 1 year ago

↳ replying to Lezlie

User 2: Definitely, we need to make sure all parts are ready to go.

Andree 1 year ago

↳ replying to Lezlie

User 1: I agree, B. Dependency is crucial for a smooth release.

Hermila 2 years ago

Hmm, I think it's gotta be D. Risk. Wouldn't want a shaky requirement to mess up the whole release, you know?

Sherrell 1 year ago

↳ replying to Hermila

Absolutely, we need to make sure all requirements are solid before the release.

Emeline 1 year ago

↳ replying to Hermila

D) Risk

Deane 1 year ago

↳ replying to Hermila

Yeah, I agree. It's definitely a risk if a requirement isn't finalized.

Bev 1 year ago

↳ replying to Hermila

D) Risk

Lewis 1 year ago

↳ replying to Hermila

C) Stability

Reita 1 year ago

↳ replying to Hermila

B) Dependency

Lucy 1 year ago

↳ replying to Hermila

A) Benefit

Jess 2 years ago

But what about dependency? Could it be that the requirement is dependent on something else that is not ready?

Anjelica 2 years ago

I agree with you, Justine. If it's not finalized, it could pose a risk to the project.

Justine 2 years ago

I think the affected requirement might be related to risk.

IIBA CCBA Exam - Topic 1 Question 110 Discussion