PMBOK Agile and Hybrid Approaches 4 — Questions and Answers
Question 1: A project team using a hybrid approach has fixed regulatory deliverables but uncertain technical requirements. How should the project manager structure the work?
- Use waterfall for the entire project to maintain control
- Apply waterfall planning to regulatory milestones and agile iterations for technical development (Correct answer)
- Use agile for everything and adjust regulatory deliverables as needed
- Outsource regulatory work to avoid conflicts with the agile team
Correct answer: Apply waterfall planning to regulatory milestones and agile iterations for technical development
Hybrid approaches strategically apply waterfall where constraints are fixed (regulations) and agile where flexibility is needed (uncertain technical scope).
Question 2: What is the purpose of a 'Definition of Ready' (DoR) in agile?
- Criteria that must be met before a user story can enter a sprint (Correct answer)
- Standards that determine when a product is ready for release
- Requirements for a team member to join the project
- Guidelines for when a sprint can be cancelled
Correct answer: Criteria that must be met before a user story can enter a sprint
The Definition of Ready ensures user stories are sufficiently understood, estimated, and small enough before the team commits to completing them in a sprint.
Question 3: In agile, which practice BEST supports the principle of 'responding to change over following a plan'?
- Creating a comprehensive Gantt chart at project start
- Holding regular backlog refinement sessions to reprioritize based on new information (Correct answer)
- Requiring formal change control board approval for all scope changes
- Freezing the product backlog after the first sprint
Correct answer: Holding regular backlog refinement sessions to reprioritize based on new information
Regular backlog refinement allows teams to incorporate new information and changing priorities, embodying the agile principle of embracing change.
Question 4: A Scrum team consistently fails to complete all sprint backlog items by the end of the sprint. What is the MOST appropriate first action?
- Extend the sprint until all items are complete
- Reduce sprint commitments based on historical velocity data (Correct answer)
- Add more team members immediately
- Remove the incomplete items from the product backlog
Correct answer: Reduce sprint commitments based on historical velocity data
Teams should use their actual velocity (historical data) to make realistic sprint commitments rather than over-committing and consistently under-delivering.
Question 5: What is 'continuous integration' in the context of agile software development?
- Weekly meetings between the development team and stakeholders
- Frequently merging code changes into a shared repository and automatically running tests (Correct answer)
- Integrating new team members into the sprint every two weeks
- Combining multiple agile teams into one large team
Correct answer: Frequently merging code changes into a shared repository and automatically running tests
Continuous integration is the practice of frequently merging code and automatically verifying it through builds and tests to catch integration errors quickly.
Question 6: In a hybrid project lifecycle, a 'phase gate' or 'stage gate' review is MOST similar to which agile concept?
- Daily standup
- Sprint review with stakeholder feedback and go/no-go decision (Correct answer)
- Sprint retrospective
- Product backlog refinement
Correct answer: Sprint review with stakeholder feedback and go/no-go decision
Phase gates involve inspecting deliverables and deciding whether to proceed, which is analogous to sprint reviews where stakeholders evaluate increments and provide direction.
Question 7: Which statement about agile contracts is MOST accurate according to PMBOK guidance?
- Fixed-price contracts are always preferred in agile projects
- Agile-friendly contracts focus on collaboration, value delivery, and flexible scope rather than rigid deliverables (Correct answer)
- Time-and-materials contracts are never appropriate for agile projects
- Contracts are not needed in agile because teams self-organize
Correct answer: Agile-friendly contracts focus on collaboration, value delivery, and flexible scope rather than rigid deliverables
PMBOK recommends that contracts for agile projects be designed to allow for flexibility and collaboration, with an emphasis on delivering value over following a fixed plan.
PMBOK Agile and Hybrid Approaches 4
A project team using a hybrid approach has fixed regulatory deliverables but uncertain technical requirements.
How should the project manager structure the work?