Flow-Based Scheduling in Adaptive Life Cycles

PMBOK v8 Definition

Flow-based scheduling is a project management approach that focuses on optimizing the flow of work through a system, with one goal being to maximize the flow of deliverables based on resource capacity, materials, and other inputs. In adaptive life cycles, iterations are generally 1 to 4 weeks in duration, with a demonstration of accomplishments at the end of each iteration, where team members determine the scope they can achieve based on prioritized requirements in the product backlog.

Why It Matters for the Exam

Flow-based scheduling appears frequently in PMI exam questions about adaptive and hybrid life cycles, particularly in scenarios testing your understanding of how teams plan and execute work in timeboxed iterations. Questions often test your ability to distinguish flow-based scheduling from predictive scheduling approaches, and to identify when each is appropriate based on project characteristics.

Key Points to Remember (for the exam)

• Iteration Duration: Adaptive iterations are generally 1 to 4 weeks in duration, with demonstrations at the end of each iteration
• Team Planning: The entire project team is heavily involved in planning at various levels during the iteration
• Scope Determination: Team members determine achievable scope based on prioritized requirements in the product backlog
• Work Estimation: Teams estimate the amount of work and collaborate to develop the scope during the iteration
• Primary Goal: Maximize flow of deliverables based on resource capacity, materials, and other inputs
• Feedback Integration: Iterations incorporate stakeholder feedback, environmental changes, and unexpected events
• Adaptive vs. Predictive: Adaptive projects have flexible schedules with short-term planning horizons; predictive projects stabilize scope early

Typical PMI Exam Example

A software development team uses 2-week iterations. At the start of each iteration, team members review the prioritized product backlog, select the scope they can complete, estimate work, and collaborate to deliver working increments. At iteration end, they demonstrate accomplishments to stakeholders. This describes: A) Predictive approach B) Flow-based scheduling in adaptive life cycles C) Waterfall method D) Hybrid approach

Answer: B – This matches the PMBOK v8 description of flow-based scheduling in adaptive life cycles.

PMI Exam Traps

• Trap: Confusing iterations with phases in predictive life cycles Reality: Iterations are 1-4 week timeboxes with demonstrations; phases are sequential with planned reevaluation between them

• Trap: Thinking flow-based scheduling means no planning Reality: Teams are heavily involved in planning at various levels, but planning horizons are shorter

• Trap: Assuming all adaptive methods use the same iteration length Reality: Iterations are generally 1-4 weeks but can vary; the key is that duration is fixed and accomplishments are demonstrated

• Trap: Confusing product backlog with project scope statement Reality: Product backlog contains prioritized requirements that evolve; scope statement is fixed early in predictive approaches

Important PMI Connections

Quick Review Questions

1. What is the typical duration range for iterations in adaptive life cycles according to PMBOK v8?

2. How do team members determine the scope they will work on during an iteration?

3. What is the primary goal of flow-based scheduling?

4. What happens at the end of each iteration in an adaptive approach?

5. When might a predictive approach be optimal instead of flow-based scheduling?

PMBOK v8 Reference

Section 4 – Project Life Cycles (Adaptive Approaches and Flow-Based Scheduling)