PMBOK FREE PMBOK Agile and Hybrid Methodologies Questions and Answers 3

Question 1

According to PMBOK, what distinguishes a hybrid life cycle from a purely agile life cycle?

Accepted Answer

Hybrid projects combine predictive and adaptive elements within the same project

Answer

Hybrid projects never use a product backlog

Answer

Hybrid projects are only used for software development

Answer

Hybrid projects eliminate the need for a project manager

Question 2

What is the recommended approach when an agile team consistently fails to meet sprint commitments?

Accepted Answer

Facilitate a retrospective to identify root causes and adjust the team's capacity planning

Answer

Extend the sprint duration to four weeks

Answer

Add more team members immediately

Answer

Replace the Scrum Master with a traditional project manager

Question 3

In a hybrid project, how should a project manager handle dependencies between agile and waterfall workstreams?

Accepted Answer

Use integration points and milestone synchronization to coordinate deliverables

Answer

Ignore dependencies since each workstream operates independently

Answer

Convert all workstreams to agile to eliminate dependencies

Answer

Delay the agile workstream until the waterfall workstream is complete

Question 4

Which agile practice helps ensure that the product increment remains potentially releasable at the end of each iteration?

Accepted Answer

Definition of Done

Answer

Daily standup meetings

Answer

Sprint planning poker

Answer

Stakeholder email updates

Question 5

What is the primary benefit of using story points instead of hours for estimation in agile projects?

Accepted Answer

Story points account for complexity, uncertainty, and effort rather than just time

Answer

Story points are more accurate than hour-based estimates

Answer

Story points eliminate the need for sprint planning

Answer

Story points allow managers to compare individual developer productivity

Question 6

When applying agile methodologies within a PMBOK framework, how should changes to project scope be managed?

Accepted Answer

Scope changes are managed through backlog refinement and prioritization by the product owner

Answer

All scope changes must go through a formal change control board before implementation

Answer

Scope changes are prohibited once the project charter is signed

Answer

Scope changes require a new project charter each time