PMI-ACP · Question #370
Which of the following is NOT a reason to use a Feature Breakdown Structure (FBS) instead of a Work Breakdown Structure (WBS)?
The correct answer is B. It allows you to baseline your project plan due to absence of change. A Feature Breakdown Structure (FBS) organizes work by customer-facing features and business value, making it ideal for Agile environments that embrace change. The statement that FBS 'allows you to baseline your project plan due to absence of change' is incorrect - FBS is…
Question
Which of the following is NOT a reason to use a Feature Breakdown Structure (FBS) instead of a Work Breakdown Structure (WBS)?
Options
- AIt allows communication between the customer and the development team in terms both can
- BIt allows you to baseline your project plan due to absence of change.
- CIt allows tracking of work against the actual business value produced.
- DIt allows the customer to prioritize the team's work based on business value.
How the community answered
(29 responses)- B93% (27)
- C3% (1)
- D3% (1)
Explanation
A Feature Breakdown Structure (FBS) organizes work by customer-facing features and business value, making it ideal for Agile environments that embrace change. The statement that FBS 'allows you to baseline your project plan due to absence of change' is incorrect - FBS is specifically designed for environments where requirements evolve. Baselining against an 'absence of change' is a characteristic of traditional, plan-driven WBS usage, not a benefit of FBS. The other options (shared language, business value tracking, customer prioritization) are genuine advantages of FBS.
Topics
Community Discussion
No community discussion yet for this question.