FIT5057 Chap.6 Agile Fundamentals
Agile Fundamentals
Agile Fundamentals introduces Scrum as an empirical framework for complex work. Transparency, inspection and adaptation operate through accountabilities, events, artefacts and their commitments. You will connect Product Goal, Sprint Goal and Definition of Done, write bounded user stories with acceptance criteria, and decide whether work can join a usable Increment when item-specific and shared quality tests differ.
The chapter treats events as purposeful inspection points rather than calendar meetings. Sprint Planning establishes why, what and how; the Daily Scrum adapts the Developers' plan toward the Sprint Goal; the Review examines product value with stakeholders; and the Retrospective improves the team's way of working.
Accountabilities remain distinct: the Product Owner orders product work, Developers own the Sprint Backlog and the Scrum Master serves through coaching and facilitation. Original cases turn broad feature requests into user stories and observable acceptance criteria. A separate Done scenario shows why passing an item's tests is not enough when shared quality work remains incomplete.
Use the chapter to connect persona, need, story, commitment and usable Increment without inventing command authority. Refinement supports that chain without fixing the solution prematurely.
What this chapter covers
- 01
Transparency, inspection and adaptation
- 02
Product Owner, Developers and Scrum Master
- 03
Sprint Planning and Daily Scrum
- 04
Sprint Review and Sprint Retrospective
- 05
Product, Sprint and Increment commitments
- 06
User stories, acceptance and Done
Worked example · free
Decide whether an item is Done
- +1Confirm that item-specific acceptance criteria are satisfied.
- +1Compare the work with the shared Definition of Done and identify the missing accessibility evidence.
- +2Conclude that it is not Done and cannot be represented as part of a usable Increment.
- +1Make the remaining work visible and adapt the Product Backlog or next plan.
Key terms
- Empiricism
- Decision-making based on observed experience through transparency, inspection and adaptation.
- Product Backlog
- The emergent ordered list of work needed to improve the product and move toward its Product Goal.
- Sprint Backlog
- The Sprint Goal, selected Product Backlog items and Developers' actionable delivery plan.
- Increment
- A usable addition to the product that meets the Definition of Done and advances the Product Goal.
Agile Fundamentals FAQ
What are the three Scrum accountabilities?
The Product Owner maximises value and manages the Product Backlog effectively. Developers create a usable Increment and own the Sprint Backlog. The Scrum Master serves the team and organisation through coaching, facilitation and impediment removal.
How are acceptance criteria different from the Definition of Done?
Acceptance criteria apply to a specific item and describe its expected behaviour or result. The Definition of Done is a shared quality commitment applied to every Increment. Work must satisfy both before it is Done.
Why is the Daily Scrum not a manager status report?
Developers use it to inspect progress toward the Sprint Goal and adapt their plan. The purpose is coordination and empirical control of the Sprint, not reporting individual activity to a manager or Scrum Master.
How do the three Scrum commitments fit together?
The Product Goal guides longer-term product direction, the Sprint Goal gives one Sprint coherence and the Definition of Done establishes shared Increment quality. Each commitment makes inspection against its artefact more meaningful.
Assessment move
Draw Scrum as a system rather than memorising separate lists. Connect each accountability to the decisions it owns, each event to its inspection purpose, and each artefact to its commitment. Write one user story for a bounded need and add observable acceptance criteria. Then test a scenario against both those criteria and the Definition of Done.
Use the Scrum values to explain behaviour when pressure encourages hidden work, direct task assignment or a misleading release claim. Start with the Product Goal and ask how the ordered Product Backlog moves toward it. For one proposed Sprint, state the Sprint Goal before choosing items so the selected work has a coherent purpose. At each event, name what evidence is inspected and what may adapt.
Keep the Daily Scrum focused on progress toward the goal rather than individual reporting. Build two contrasting quality scenarios: one item fails its acceptance criteria, and another passes those criteria but fails the shared Definition of Done. Explain why neither can be represented as a usable Increment.
Practise accountabilities with short prompts involving a Product Owner, Developer, Scrum Master and stakeholder, making sure no role acquires authority the framework does not give it. Finish by connecting persona, requirement, story, acceptance evidence and Done quality to the same bounded pilot feature.
Working through Agile Fundamentals in FIT5057? Sia is AskSia’s AI Project Management tutor — ask any FIT5057 Agile Fundamentals 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.