FIT5057 Chap.7 Advanced Agile
Advanced Agile
Advanced Agile applies Scrum under delivery pressure. You will interpret a burndown against the Sprint Goal, use the Daily Scrum to adapt the plan, handle new stakeholder requests through the correct accountabilities, and distinguish product inspection in the Sprint Review from process improvement in the Retrospective. The chapter closes by defining a defensible hybrid approach through explicit fixed and adaptive boundaries.
The burndown example plots actual remaining work against an ideal decline, then warns against diagnosing cause from the line alone. Developers still need blocker, flow, estimate and quality evidence before adapting the Sprint Backlog. A stakeholder-pressure case routes product ordering to the Product Owner, delivery assessment to Developers and facilitation to the Scrum Master.
Review and Retrospective examples keep product value evidence separate from process evidence while showing how both affect later work. The hybrid section requires more than using two planning tools. It identifies which constraints remain predictive, what product learning can adapt, who owns each decision and how Sprint evidence updates schedule, cost, risk and stakeholder controls.
This keeps adaptation connected to an accountable delivery decision.
What this chapter covers
- 01
Sprint Planning and capacity forecasts
- 02
Burndown interpretation and goal risk
- 03
Daily adaptation of the Sprint Backlog
- 04
Scrum Master service under pressure
- 05
Sprint Review and Retrospective evidence
- 06
Hybrid delivery and governance integration
Worked example · free
Route an urgent stakeholder request
- +1Make the request, its intended value and urgency transparent.
- +2Route product ordering to the Product Owner rather than allowing direct insertion by the director.
- +2Ask Developers to assess capacity, quality and whether an exchange of scope would endanger the Sprint Goal.
- +1Use the Scrum Master to facilitate the decision and protect accountabilities, not approve scope.
Key terms
- Burndown Chart
- A time series showing remaining Sprint work, used as evidence when inspecting progress toward the Sprint Goal.
- Velocity
- An observed amount of work completed in prior Sprints that may inform, but not guarantee, a future forecast.
- Impediment
- A condition that reduces the team's ability to progress and may need help beyond ordinary self-management.
- Hybrid Approach
- A deliberate combination of predictive and adaptive controls with explicit decision boundaries and evidence flows.
Advanced Agile FAQ
What does a burndown chart actually tell a team?
It shows how remaining work changes over Sprint time. A line above the ideal trend prompts inspection, but it does not explain the cause or decide whether the Sprint Goal is at risk without backlog, blocker and quality evidence.
How are the Sprint Review and Retrospective different?
The Sprint Review inspects the product outcome and changing environment with stakeholders, then adapts future product work. The Retrospective inspects team effectiveness, process, tools and quality practices, then selects an improvement.
What makes a delivery approach genuinely hybrid?
It identifies which constraints and decisions remain predictive, which product work may adapt, who owns each decision and how Sprint evidence updates the wider schedule, cost, risk, stakeholder and governance controls.
Who handles an urgent request during a Sprint?
The Product Owner evaluates value and ordering while Developers assess capacity, quality and Sprint Goal effects. The Scrum Master supports transparency and facilitation. A senior stakeholder provides evidence and urgency but does not insert work directly.
Assessment move
Practise interpreting burndown shapes in sentences: state what changed, whether the Sprint Goal may be at risk and what evidence the team should inspect next. Work through stakeholder-pressure scenarios by preserving Product Owner, Developer and Scrum Master accountabilities. Keep Review product evidence separate from Retrospective process evidence.
For hybrid questions, draw two boundaries: fixed governance or constraint decisions on one side, adaptive product learning on the other, with explicit evidence moving between them. Plot a seven-day set of remaining-work values and compare the actual line with an ideal decline. Avoid diagnosing the cause from shape alone; inspect blockers, completion flow, estimate changes and Definition of Done work.
Introduce a senior request midway through the Sprint and write a response that routes product ordering to the Product Owner while Developers assess capacity and goal risk. Use the Scrum Master as facilitator and coach, not command authority. Next, classify three observations between Sprint Review and Retrospective, explaining whether each concerns product value or the team's way of working.
For hybrid practice, choose one fixed constraint, one adaptive product area and one governance threshold. Show how Sprint evidence updates the wider risk, schedule and stakeholder controls. Conclude with the release decision, residual uncertainty and the next inspect-and-adapt point.
Working through Advanced Agile in FIT5057? Sia is AskSia’s AI Project Management tutor — ask any FIT5057 Advanced Agile question and get a clear, step-by-step explanation grounded in how FIT5057 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.