PMP Practice Questions #153
You are developing a release plan for a software project operating under an adaptive lifecycle. Which set of information is most crucial for effectively crafting this release plan?
A) Product Backlog, release goal, and estimated team velocity
B) Product Vision, Product Roadmap, and team availability
C) Release Scope Document, detailed estimation, and resource availability
D) List of User Stories and Features, cost estimate, and resource availability
Analysis
In this scenario, you are developing a release plan for a software project operating under an adaptive lifecycle. The key question is identifying the most crucial set of information needed for effectively crafting this release plan. The goal is to choose the inputs that will best support the development and projection of the release plan in an adaptive project environment.
Analysis of Options:
Option A: Product Backlog, release goal, and estimated team velocity: This option includes a Product Backlog, release goal, and estimated team velocity. The Product Backlog, assuming it is prioritized, provides the list of features and requirements. The release goal gives direction on what needs to be achieved in the release, and the estimated team velocity helps in projecting how many stories or items can be completed in each iteration. This combination is essential for adaptive planning as it balances scope, timeline, and team capacity.
Option B: Product Vision, Product Roadmap, and team availability: This option offers the Product Vision, Product Roadmap, and team availability. The Product Vision provides a high-level direction, and the Product Roadmap offers a timeline for when features will be developed, indirectly providing the release goal. Team availability indicates the number of team members available for the project. However, this option lacks detailed information on the prioritized backlog and team velocity, which are critical for detailed release planning in an adaptive lifecycle.
Option C: Release Scope Document, detailed estimation, and resource availability: This option includes a Release Scope Document, detailed estimation, and resource availability. While it suggests a detailed approach to planning, this is more characteristic of a predictive lifecycle rather than an adaptive one. An adaptive lifecycle relies more on high-level estimations (like story points) and flexibility rather than detailed upfront planning. Additionally, resource availability does not provide the same insight as team velocity in an agile context.
Option D: List of User Stories and Features, cost estimate, and resource availability: This option comprises a list of User Stories and Features, cost estimate, and resource availability. The list of User Stories and Features resembles a prioritized backlog, but it is not explicitly stated. The cost estimate is not typically a primary concern for release planning in an adaptive lifecycle, where the focus is more on delivering value iteratively. Resource availability is similar to team availability but does not provide direct insight into team capacity like velocity does.
Conclusion: Given the need to effectively craft a release plan for a software project operating under an adaptive lifecycle, Option A (Product Backlog, release goal, and estimated team velocity) is the most suitable set of information. This option provides a balanced view of scope, direction, and team capacity, which are critical for adaptive planning.
PMP Exam Content Outline Mapping
| Domain | Task |
|---|---|
| Process | Task 6: Plan and manage schedule |
Topics Covered
- Release Planning
