Cyber Monday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Scaled Agile Exam SAFe-APM Topic 5 Question 17 Discussion

Actual exam question for Scaled Agile's SAFe-APM exam
Question #: 17
Topic #: 5
[All SAFe-APM Questions]

Feature estimates are aggregated back into the Epic estimate as part of which artifact?

Show Suggested Answer Hide Answer
Suggested Answer: B

Feature estimates are aggregated back into the Epic estimate as part of the lean business case. The lean business case is a lightweight and collaborative artifact that captures the rationale, assumptions, and financial projections for an Epic. The lean business case includes the Epic value statement, which consists of the value proposition, the benefit hypothesis, and the Epic estimate. The Epic estimate is the total effort required to implement the Epic, expressed in story points. The Epic estimate is derived from the sum of the Feature estimates, which are the effort required to implement each Feature that contributes to the Epic, also expressed in story points. The Feature estimates are aggregated back into the Epic estimate as part of the lean business case to provide a realistic and data-driven projection of the cost and duration of the Epic.


Lean Business Case - Scaled Agile Framework

Epic - Scaled Agile Framework

Feature estimates are aggregated back into the Epic estimate as part of ...

Contribute your Thoughts:

Margurite
2 months ago
The correct answer is probably written in invisible ink, and we have to use our Agile superpowers to reveal it.
upvoted 0 times
...
Celeste
2 months ago
This question is really testing our understanding of Agile terminology. I'm going to have to say B) Lean business case.
upvoted 0 times
...
Dannie
2 months ago
D) Capabilities seems more logical to me. The Epic estimate should be a part of the overall Capabilities of the product or solution.
upvoted 0 times
Roy
1 months ago
B) Lean business case could also play a role in aggregating feature estimates back into the Epic estimate.
upvoted 0 times
...
Tom
2 months ago
C) Customer journey map might provide a different perspective on how feature estimates are aggregated back into the Epic estimate.
upvoted 0 times
...
Boris
2 months ago
I think A) Portfolio Roadmap could also be a valid option for aggregating feature estimates back into the Epic estimate.
upvoted 0 times
...
Becky
2 months ago
I agree, D) Capabilities makes the most sense for aggregating feature estimates back into the Epic estimate.
upvoted 0 times
...
...
Micaela
2 months ago
I'm going to go with A) Portfolio Roadmap. That's where all the feature and Epic estimates come together, right?
upvoted 0 times
...
Willard
3 months ago
I bet the person who wrote this question loves to play 'Guess the Buzzword' at the office parties.
upvoted 0 times
Tyisha
2 months ago
I would go with D) Capabilities.
upvoted 0 times
...
Marilynn
2 months ago
D) Capabilities
upvoted 0 times
...
Suzi
2 months ago
I think it's A) Portfolio Roadmap.
upvoted 0 times
...
Kaitlyn
2 months ago
A) Portfolio Roadmap
upvoted 0 times
...
...
Shenika
3 months ago
I think it could also be B) Lean business case, as it involves analyzing the financial impact of the features and how they contribute to the Epic estimate.
upvoted 0 times
...
Maryann
3 months ago
I see your point, but I still think it's A) Portfolio Roadmap because it helps in aligning feature estimates with the overall project goals.
upvoted 0 times
...
Rolande
4 months ago
I disagree, I believe it is D) Capabilities.
upvoted 0 times
...
Maryann
4 months ago
I think the answer is A) Portfolio Roadmap.
upvoted 0 times
...

Save Cancel
az-700  pass4success  az-104  200-301  200-201  cissp  350-401  350-201  350-501  350-601  350-801  350-901  az-720  az-305  pl-300  

Warning: Cannot modify header information - headers already sent by (output started at /pass.php:70) in /pass.php on line 77