IS5540 Chap.2 Predictive, Agile and Hybrid
Predictive, Agile and Hybrid
Choose from uncertainty
This chapter compares predictive delivery, adaptive delivery and hybrid boundaries using scope clarity, expected change, release pattern and control cost. It then applies deliberate tailoring to governance and process.
The assessed group project makes the distinction concrete: the pseudo-client receives a predictive plan, while the student team uses Scrum to produce reports and a presentation.
Match control to what can be known
Predictive delivery is useful when the result can be specified with enough stability to support early decomposition, dependency planning and baseline control.
Adaptive delivery is useful when feedback must shape the result through short cycles and reprioritisation. Neither removes uncertainty. Predictive work makes change visible against an approved reference, while adaptive work makes learning visible through increments, reviews and backlog decisions. The correct comparison is therefore not rigid versus flexible.
It is which uncertainty deserves early commitment, which deserves repeated feedback and what evidence will expose the cost of a wrong assumption.
Read constraints together
A fixed external date does not automatically require a fully predictive approach, and uncertain user needs do not automatically make every component adaptive.
Consider scope clarity, cost of late change, integration dependencies, compliance obligations, release pattern and access to reviewers. A regulated interface may hold its protocol and assurance gates predictively while exploring the user workflow through prototypes. The boundary should be explicit: name the stable element, the learning element, the moment they integrate and the authority that accepts the combined result.
Otherwise hybrid becomes a label for unmanaged inconsistency.
Tailor deliberately and retain the reason
Tailoring changes a process, artefact, cadence or governance route to fit the project context. It does not mean omitting inconvenient controls without explanation. Start with the decision the control is meant to support, then adjust detail, frequency or ownership while preserving necessary evidence.
A small team may combine two meetings, but it still needs a visible decision record. A short project may use a compact risk register, but it still needs owners and responses.
Document the rationale so a reviewer can distinguish a purposeful design from accidental noncompliance.
Keep the two assessed systems apart
In the group project, students act as consultants who prepare a predictive management plan for the pseudo-client's information technology project. Separately, the student team uses Scrum and Jira to manage its own reports and presentation.
The client implementation is not the Scrum object in the captured assignment instructions. Write the noun after every method: client scope baseline, student report backlog, client change request, student sprint review.
This language test prevents evidence from one system being claimed as control over the other.
Defend the choice with a risk statement
A strong lifecycle answer states what the chosen approach makes easier and which risk it accepts. Early baselining may protect coordination but raise the cost of late learning. Short iterations may expose user needs but require frequent availability from decision-makers.
A hybrid boundary may localise uncertainty but add integration and governance overhead. Finish with the control that keeps the accepted risk visible, such as change control, scheduled review, interface criteria or a release gate.
What this chapter covers
- 01
Predictive planning and constrained change
- 02
Adaptive delivery and small releases
- 03
Hybrid boundaries
- 04
Scope clarity and uncertainty
- 05
Four-stage tailoring
- 06
Client plan versus student delivery
Worked example · free
Draw a hybrid boundary
- 2Identify fixed constraints.
- 2Identify learnable work.
- 3Define the integration boundary.
Key terms
- Predictive Approach
- A delivery approach that plans most work up front and controls change against an approved plan.
- Adaptive Approach
- A delivery approach that expects change and releases value incrementally.
- Hybrid Approach
- A defined combination of predictive and adaptive work within one initiative.
- Tailoring
- Deliberate adaptation of approach, governance and process to the project context.
- Increment
- A usable addition delivered within an adaptive sequence.
Predictive, Agile and Hybrid FAQ
Is adaptive delivery always the safest modern choice?
No. Adaptive delivery fits uncertain scope, expected change and work that can release in small increments. Fixed external rules, a single cutover or expensive partial delivery can make predictive control stronger for all or part of the initiative.
What makes a hybrid approach defensible?
A defensible hybrid identifies which work follows each rhythm, why that boundary follows from uncertainty and release needs, and how dependencies are reconciled. Merely saying that a project uses the best of both approaches does not define a control.
Why must the student project use two approaches?
The client plan and the class deliverables are different management objects. The assignment requests a predictive client plan and an agile account of how the student team produced the reports and presentation through Scrum and Jira.
Exam move
Build a decision table with scope clarity, release pattern, change cost, external deadline and user-feedback availability. Apply it to three scenarios, then state the risk each chosen approach accepts and the control that keeps it visible.
Working through Predictive, Agile and Hybrid in IS5540? Sia is AskSia’s AI Project Management tutor — ask any IS5540 Predictive, Agile and Hybrid question and get a clear, step-by-step explanation grounded in how IS5540 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.