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

IIBA Exam CCBA Topic 1 Question 110 Discussion

Actual exam question for IIBA's CCBA exam
Question #: 110
Topic #: 1
[All CCBA Questions]

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?

Show Suggested Answer Hide Answer
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 ...


by Marti at Apr 06, 2025, 08:43 PM

Limited Time Offer

25%

Off

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

Contribute your Thoughts:

Submit Cancel
Raymon
20 days 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.'
upvoted 0 times
...
Muriel
23 days 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!
upvoted 0 times
Abraham
A) Benefit
upvoted 0 times
...
...
Ulysses
27 days ago
D. Risk, for sure. Better to play it safe and iron out any potential issues before rolling it out.
upvoted 0 times
Candida
2 days ago
A) Benefit
upvoted 0 times
...
...
Lezlie
1 months 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.
upvoted 0 times
Andree
2 days ago
User 1: I agree, B. Dependency is crucial for a smooth release.
upvoted 0 times
...
...
Hermila
1 months ago
Hmm, I think it's gotta be D. Risk. Wouldn't want a shaky requirement to mess up the whole release, you know?
upvoted 0 times
Bev
D) Risk
upvoted 0 times
...
Lewis
4 days ago
C) Stability
upvoted 0 times
...
Reita
5 days ago
B) Dependency
upvoted 0 times
...
Lucy
9 days ago
A) Benefit
upvoted 0 times
...
...
Jess
1 months ago
But what about dependency? Could it be that the requirement is dependent on something else that is not ready?
upvoted 0 times
...
Anjelica
2 months ago
I agree with you, Justine. If it's not finalized, it could pose a risk to the project.
upvoted 0 times
...
Justine
2 months ago
I think the affected requirement might be related to risk.
upvoted 0 times
...

Save Cancel
a