FIT2002 Chap.6 Quality Tools and Agile Mindset
Quality Tools and Agile Mindset
Quality improvement uses evidence to understand variation and focus effort. Check sheets structure observation, Pareto analysis highlights the categories contributing most recorded problems, cause-and-effect diagrams organise possible explanations, and control charts help distinguish expected variation from signals that may require investigation.
A tool does not make the conclusion: the data definition, collection method and context determine what can reasonably be inferred.
The Agile mindset adds a delivery principle. When needs and solutions are uncertain, short feedback cycles can expose learning earlier than a fully predictive sequence. Agile is not the absence of plans, documentation or accountability.
A predictive, hybrid or adaptive approach should be selected from uncertainty, compliance, architecture, stakeholder access and cost of change. Strong scenario answers match the approach to evidence and describe the controls that still protect quality and governance.
What this chapter covers
- 01
Check sheets and consistent operational collection of defect evidence
- 02
Pareto analysis for prioritising the largest recorded categories
- 03
Cause-and-effect analysis for organising testable explanations
- 04
Control charts for detecting unusual variation over time
- 05
Agile values and short feedback cycles under meaningful uncertainty
- 06
Predictive, adaptive and hybrid delivery as contextual choices
- 07
Documentation, governance and quality controls in adaptive work
Worked example · free
Choose a response from defect and uncertainty evidence
- +2Calculate that login and payment account for 56 of 80 defects, or 70%, so those categories deserve initial investigation rather than equal attention to every category.
- +2Use cause-and-effect analysis and targeted evidence before claiming a root cause; the Pareto count identifies priority, not causation.
- +2Recommend a hybrid approach: plan stable provider integration predictively while exploring uncertain search behaviour through short increments and user feedback.
- +2Retain acceptance criteria, automated regression tests and a Definition of Done across both parts of the release.
- +1Review defect definitions and collection consistency so the apparent priority is based on comparable observations.
Key terms
- Agile Values
- Four value preferences that emphasise people and interaction, working outcomes, customer collaboration and response to change while recognising value in the items on the other side.
- Predictive Delivery
- An approach that establishes substantial scope and planning detail in advance and controls execution against baselines. It can suit stable needs and costly late change.
- Adaptive Delivery
- An approach that delivers and learns in short cycles, allowing detail and priorities to evolve from feedback. It still requires objectives, quality standards and transparent governance.
- Hybrid Delivery
- A deliberately integrated combination of predictive and adaptive practices, selected for different uncertainties or components. It should be coherent rather than an accidental mixture.
- Pareto Chart
- A ranked display of categories and frequencies used to identify where recorded problems are concentrated. It supports prioritisation but does not establish root cause.
- Control Chart
- A time-ordered process chart with a centre line and control limits, used to identify patterns or signals that differ from expected process variation.
Quality Tools and Agile Mindset FAQ
Does Agile mean that a team should avoid documentation?
No. Agile values useful working outcomes over excessive documentation, not zero documentation. Record what supports shared understanding, compliance, maintainability, acceptance and future decisions. The question is whether an artefact earns its cost and stays current. A concise decision record or executable test can be more valuable than a long document nobody uses.
When is a hybrid delivery approach defensible?
Hybrid delivery is defensible when different parts of the work have materially different uncertainty or governance needs. A stable regulated interface may need planned approvals, while an unfamiliar user experience benefits from rapid feedback. Explain which practices apply to which work, how dependencies are coordinated, and which shared controls preserve quality. Calling any inconsistent process hybrid is not enough.
What conclusion can a Pareto chart support?
It can show which recorded categories account for the largest share of observations and therefore where investigation may yield the greatest initial benefit. It cannot establish that the largest category has one cause or that small categories are harmless. Check definitions, collection bias, severity and context before choosing corrective action, then verify whether the response changes results.
Assessment move
Make a one-page tool selector. For each quality tool, write the question it answers, the data it needs and one conclusion it cannot support. Practise turning a defect table into percentages and a ranked priority, then add a separate root-cause investigation so prioritisation is not confused with explanation.
For delivery approaches, compare uncertainty of need, uncertainty of solution, compliance burden, stakeholder availability and cost of change. Use mixed scenarios and justify predictive, adaptive or hybrid choices at component level. Add the controls that remain necessary: acceptance criteria, tests, review, traceability and decision rights. Revise the Agile values as preferences with context rather than slogans.
The highest-value practice is to challenge extreme claims such as “Agile needs no plan” and replace them with a precise, evidence-based statement.
Working through Quality Tools and Agile Mindset in FIT2002? Sia is AskSia’s AI Project Management tutor — ask any FIT2002 Quality Tools and Agile Mindset question and get a clear, step-by-step explanation grounded in how FIT2002 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.
