Process — Agile, hybrid & flow control
A module focused on PMP scenarios where you must choose between predictive, agile, and hybrid approaches, then protect value flow with backlog, cadence, WIP, Definition of Done, and delivery metrics.
Estimated time : 95 min
Learning objectives
- Recognize the life cycle that best fits the level of uncertainty.
- Identify bottlenecks using flow metrics.
- Apply PMI logic to changes in agile or hybrid contexts.
- Differentiate velocity, throughput, lead time, cycle time, and WIP.
Key concepts
- Predictive life cycle
- An approach useful when scope is stable and detailed planning creates more value than continuous adaptation.
- PMBOK 8 — Project Work / Planning
- Adaptive life cycle
- An iterative and incremental approach used when requirements emerge through feedback.
- Agile Practice Guide
- Hybrid
- A deliberate combination of predictive and adaptive practices across different components of the same project.
- Agile Practice Guide
- WIP
- Work in progress. Limiting it helps reveal bottlenecks and shorten cycle time.
- Kanban / Agile Practice Guide
- Definition of Done
- Shared completeness criterion: testing, review, documentation, and built-in quality as defined by the team.
- Agile Practice Guide
- Velocity
- Average amount of work completed per iteration; useful for forecasting, not for comparing teams.
- Agile Practice Guide
1. Choosing predictive, agile, or hybrid
The PMP exam does not ask you to prefer agile by default. It asks you to tailor the approach to context: requirement stability, regulatory criticality, customer feedback capacity, innovation level, and tolerance for change.
Quick context reading
| Signal | Likely approach | Why |
|---|---|---|
| Stable requirements, fixed contract, strong compliance | Predictive | The baseline and change control provide stability. |
| Innovative product, emerging needs, frequent feedback | Agile / adaptive | Iterations reduce the risk of building the wrong solution. |
| Stable regulatory core + evolving interface | Hybrid | Each component gets the delivery mode that fits it. |
Exam reflex
Always look for the answer that maximizes controlled learning: get feedback early, keep stakeholders engaged, and protect value.
Artifact → decision → PMI action map
Artifact
Product backlog + Definition of Done + flow metrics
Decision
Does the work maximize value without breaking flow?
PMI action
Reprioritize with the PO, limit WIP, protect the sprint, and measure delivery.
Avoid: Adding work to the sprint or changing priority without value trade-off.
Recommendations
- State the context before choosing the approach.
- In a hybrid scenario, separate stable and uncertain components.
Tips
- High-uncertainty question = short feedback before detailed planning.
- The word 'hybrid' is rarely a trap when the scenario shows two different kinds of work.
Chapter quiz
1.A product has unstable requirements and a sponsor available weekly. Which approach is healthiest?
2.An embedded system must meet a frozen safety standard, while its user dashboard evolves after each customer test. Which approach fits best?
2. Flow, WIP, and useful metrics
An agile board is not only a task list. It is an information radiator: it makes visible where work waits, where quality blocks, and where the team overloads the system.
| Metric | Question it answers | PMP trap |
|---|---|---|
| WIP | How much work is started but not finished? | Increasing WIP often worsens delays. |
| Lead time | How long between request and delivery? | Do not confuse it with development time only. |
| Cycle time | How long a task takes once started? | High cycle time often indicates a bottleneck. |
| Throughput | How many items are finished per period? | Throughput does not replace business value. |
Classic trap
If the Test column is full, do not start more development. Help clear the bottleneck, limit WIP, and address the cause.
WIP = Débit × Temps de cycle ⇒ Temps de cycle = WIP / DébitLittle's Law: relationship between work in progress, throughput, and cycle time.
Little's Law in practice
A Kanban board shows 12 items in progress (WIP). The team finishes on average 3 items per week (throughput). What is the average cycle time?
- Little's Law: Cycle time = WIP / Throughput.
- Cycle time = 12 / 3 = 4 weeks.
- To shorten the cycle, reduce WIP or raise throughput, not by starting more work.
Average cycle time = 4 weeks. Cutting WIP from 12 to 6 (same throughput) would bring the cycle down to 2 weeks.
Lead time vs cycle time
Lead time is measured from the customer request to delivery; cycle time, from the moment work starts to its completion. The gap between the two is the time spent queued or waiting before work begins: Lead time = wait/queue time + cycle time.
Artifact → decision → PMI action map
Artifact
Product backlog + Definition of Done + flow metrics
Decision
Does the work maximize value without breaking flow?
PMI action
Reprioritize with the PO, limit WIP, protect the sprint, and measure delivery.
Avoid: Adding work to the sprint or changing priority without value trade-off.
Recommendations
- Reduce started work before adding capacity.
- Use metrics as a conversation aid, not as a blaming tool.
- To reduce lead time, attack queues first, not only cycle time.
Tips
- Kanban + pile-up = bottleneck + WIP.
- A good agile answer protects sustainable pace.
Chapter quiz
1.Tasks pile up in quality review. What does the PM / servant leader do?
2.A board has 12 items in progress and the team finishes 3 per week. What is the average cycle time per Little's Law?
3.Cycle time is short but the customer complains about long delays. Where should you look?
3. Backlog, Definition of Done, and change
In agile, change is not an accident: it is expected, but still governed. The product owner prioritizes value, the team clarifies the Definition of Done, and the PM protects transparency.
Definition of Done
A coded but untested story is not done. The DoD turns quality into a shared rule rather than a late inspection.
- Clarify value and acceptance criteria.
- Prioritize the backlog with the product owner.
- Deliver a finished increment according to the DoD.
- Inspect feedback and adjust what comes next.
Cadence and timeboxing
Cadence is the regular rhythm of agile events (e.g., a 2-week sprint). Timeboxing sets a fixed, non-negotiable maximum duration for an event: if work exceeds the box, you do not extend the box, you reduce scope or defer to the next cycle. A stable cadence makes throughput predictable.
Burndown (work remaining) vs burnup (scope + done)
| Aspect | Burndown | Burnup |
|---|---|---|
| What is plotted | Work remaining trending down to zero. | Work completed rising toward a scope line. |
| Scope change | Hidden: a rise in the line is ambiguous. | Visible: the scope line moves up separately. |
| Best use | Simple tracking of remaining work in a sprint. | Communicate progress when scope changes. |
Artifact → decision → PMI action map
Artifact
Product backlog + Definition of Done + flow metrics
Decision
Does the work maximize value without breaking flow?
PMI action
Reprioritize with the PO, limit WIP, protect the sprint, and measure delivery.
Avoid: Adding work to the sprint or changing priority without value trade-off.
Recommendations
- Do not count partial credit in velocity.
- Every change must remain visible in the backlog or appropriate register.
- Prefer a burnup when scope moves: it separates progress from scope change.
Tips
- The product owner prioritizes; the team estimates; the PM facilitates and removes impediments.
- Quality is built in, not pushed to the end.
Chapter quiz
1.A story is coded but not tested. Can it be counted as done?
2.Scope changes often and the sponsor wants to clearly see progress AND scope additions. Which chart fits best?
Decision toolkit
PMP decision trees & running case
Use this when two answers look right: qualify the context, choose the artifact, then act.
Change request
A sponsor, customer, or user asks to change scope, cost, schedule, or quality.
1. Predictive approach with an approved baseline.
Decision: Analyze impact before acting.
Action: Document the request, assess impacts, then route it through integrated change control/CCB.
2. Agile approach with a product backlog.
Decision: Do not disrupt the current sprint.
Action: Add it to the backlog, clarify value, and reprioritize with the Product Owner.
3. Urgent compliance/safety-related change.
Decision: Protect compliance and transparency.
Action: Analyze quickly, inform governance authorities, and record the decision.
Trap: Implementing directly because the sponsor asked bypasses governance.
Risk vs issue
An event may happen or has just happened.
1. The event is uncertain.
Decision: Treat it as a risk.
Action: Qualify probability/impact, choose response, owner, and reserve.
2. The event has occurred.
Decision: Treat it as an issue.
Action: Create corrective action, assign an owner, and track to closure.
3. The issue creates new risks.
Decision: Update both logs/registers.
Action: Issue log for immediate action, risk register for remaining uncertainty.
Trap: A materialized risk is no longer just monitored: action is required.
Vendor delay
A vendor announces a delay, quality issue, or resource unavailability.
1. The contract defines SLAs, milestones, or penalties.
Decision: Check commitments before negotiating.
Action: Compare contract, actual performance, and project impacts.
2. The delay impacts the critical path or value.
Decision: Evaluate alternatives and reserve.
Action: Analyze fast tracking, replanning, another vendor, or scope trade-off.
3. The vendor relationship is recoverable.
Decision: Collaborate without losing contractual control.
Action: Dated action plan, checkpoints, and risk register update.
Trap: Threatening the vendor before analyzing contract and impact is a poor first response.
Digital project: omnichannel customer portal
Charter
Objective: reduce support calls by 25% in 6 months through secure self-service.
Backlog / WBS
Product backlog, MVP, monthly releases, Definition of Done including security and analytics.
Stakeholders
- CX sponsor, Product Owner, dev team, security, support, pilot customers.
- Success measured by adoption, resolution rate, and satisfaction.
Risks
- Low adoption if the portal does not solve real pain points.
- Security risk around authentication and personal data.
Change
Major change: add an AI chatbot. PMI response: value, risks, compliance, backlog, and prioritization.
EVM
Light EVM: release budget vs delivered value; also track burnup and real adoption.
Closure
Support transition, runbook, training, benefits measurement at 30/60/90 days.
Practical examples
Hybrid e-commerce project
Scenario : Payment compliance is stable, but the user journey evolves after customer tests.
Project manager's action : Treat compliance with lightweight predictive controls and user experience with agile delivery, integrating regularly.
Testing bottleneck
Scenario : Development moves fast, but tickets wait three days in testing.
Project manager's action : Make the bottleneck visible, limit WIP, and help the team strengthen testing capacity.
Exam strategy
- If requirements are unstable, look for short feedback, prioritized backlog, and incremental delivery.
- If one part is contractual and another exploratory, think hybrid rather than all-agile or all-predictive.
- When Kanban work is blocked, the right answer treats the bottleneck and limits WIP instead of starting more work.
- A story is done only when it meets the Definition of Done.
Module assessment
1.Which signal most favors a hybrid approach?
2.Velocity is mainly used to...