PMP Practice Questions #22
You are starting a new software development project with fairly identified features. Senior management has expressed the need for an expedited delivery strategy, emphasizing the release of project features as soon as they are ready to gain an advantage over competitors. Which delivery approach aligns best with this directive?
A) You should plan to deliver the completed features every two weeks.
B) Plan by identifying small groups of features that can be released incrementally to deliver business value.
C) Develop the features in a sequence of business value and release them as they become ready.
D) Propose the establishment of a review board for approving the release of features incrementally.
The scenario involves a new software development project where the features are fairly identified, and there’s an explicit need from senior management for an expedited delivery strategy. The goal is to release project features as soon as they’re ready to gain a competitive advantage. Each option proposes a strategy, but they differ significantly in approach.
Analysis of Options:
Option A: You should plan to deliver the completed features every two weeks. This suggests a bi-weekly delivery schedule, which implies a strict adherence to time-boxed delivery, likely in sprints. While this ensures regular releases, it doesn’t prioritize features by business value or address the management’s need for releasing features as soon as they’re ready. It adopts a one-size-fits-all approach without considering the strategic importance of different features.
Option B: Plan by identifying small groups of features that can be released incrementally to deliver business value. This emphasizes the identification of small groups of features for incremental release, stressing the concept of Minimum Viable Product (MVP) or Minimum Business Increment (MBI). This approach aligns well because it allows for the early and incremental delivery of value, provides flexibility in adapting to changes, and ensures that releases are meaningful (i.e., they deliver actual business value). However, it doesn’t explicitly mention prioritizing features based on business value, which is a slight shortfall.
Option C: Develop the features in a sequence of business value and release them as they become ready. This focuses on developing features in order of business value and releasing them as soon as they are ready. While this option seems to address the senior management’s directive, it oversimplifies the process. Releasing features as soon as they’re ready, without grouping them into meaningful increments, may lead to releases that don’t offer substantial value. This is especially true for a new product, where interdependent features might be necessary to provide any business value.
Option D: Propose the establishment of a review board for approving the release of features incrementally. This suggests establishing a review board to approve feature releases. While this introduces a level of oversight and control, it seems more bureaucratic and doesn’t directly contribute to the expedited delivery strategy that management wants. It also doesn’t address the strategic sequencing of feature development or ensure the delivery of business value.
Conclusion: Given the urgency to deploy software features promptly to outpace competitors, Option B emerges as the superior strategy. It advocates for the thoughtful assembly of feature sets, similar to MVPs or MBIs, that can be progressively rolled out, guaranteeing immediate business impact. This tactic not only responds to the demand for swift action but also ensures each release is meaningful and beneficial. Unlike Option C, which proposes a rapid, context-free release of individual features as they are completed,
PMP Exam Content Outline Mapping
|Business||Task 2: Evaluate and deliver project benefits and value|
|Process||Task 13: Determine appropriate project methodology/methods and practices|
- Incremental Delivery
- Business Value
- Measurement system to track benefits