Monash University · FACULTY OF PROJECT MANAGEMENT

FIT5057 Chap.5 Stakeholder and Quality Management

- one subject, every graph, every model, every mark
6 Chapters3-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 5 of 7 · FIT5057

Stakeholder and Quality Management

Stakeholder and Quality Management joins engagement, communication, acceptance and resource capacity. Stakeholder analysis should change what evidence is communicated, when and by whom. Quality begins with a testable criterion, uses assurance to improve the process and control to inspect results. Resource loading then checks whether real people have enough capacity to deliver the promised quality and schedule.

An influence-interest map is only a starting posture, so the chapter translates each position into a purpose, format, cadence, sender and feedback route. It also identifies warning signs that engagement may be changing. Quality examples replace subjective claims with observable conditions and keep process assurance separate from deliverable control.

The resource section adds every concurrent task assigned to one person and compares demand with realistic availability. When demand is too high, the response must protect acceptance-critical work and consider dependencies, stakeholders and decision authority. These connections matter because a quality plan that ignores available people, or a communication plan that does not support a decision, cannot operate as promised.

The original worked case shows how to quantify overload and recommend controlled reallocation. Capacity evidence makes the quality promise operational rather than aspirational.

In this chapter

What this chapter covers

  • 01

    Stakeholder identification and analysis

  • 02

    Influence-interest engagement choices

  • 03

    Communication purpose, cadence and feedback

  • 04

    Quality assurance compared with quality control

  • 05

    Acceptance criteria and evidence

  • 06

    Resource loading and over-allocation

Worked example · free

Resolve a weekly resource overload

Q [5 marks]. For this capacity exercise, the marks shown are not an official University mark allocation. A tester has 18 available hours. Regression testing requires 9 hours, accessibility testing 6 hours and release support 7 hours. Quantify the overload and recommend the next decision.
Interest increases from left to right and influence increases upward; the plotted roles indicate different engagement effort rather than personal importance.Interest increases from left to right and influence increases upward; the plotted roles indicate different engagement effort rather than personal importance.SponsorSupportRegulatorUsersInterest increasesInfluence increasesmanage closelykeep satisfied
Interest increases from left to right and influence increases upward; the plotted roles indicate different engagement effort rather than personal importance.
  • +1Total demand = 9 + 6 + 7 = 22 hours.
  • +1Overload = 22 minus 18 = 4 hours.
  • +1Identify which task supports the release acceptance gate and inspect dependencies and stakeholder commitments.
  • +2Recommend controlled reallocation, resequencing or scope trade-off through the relevant authority, then update the plan.
The tester is overloaded by four hours. The team should protect acceptance-critical work, examine dependencies and use the agreed authority path to reallocate or resequence rather than assume extra capacity.
Sia tip — Add hours across all concurrent tasks for one person. A named owner on every task does not prove the combined plan is feasible.
Glossary

Key terms

Engagement Level
The current or desired degree to which a stakeholder understands, supports or participates in project decisions.
Communication Cadence
The planned frequency and timing of an information exchange for a defined stakeholder purpose.
Quality Assurance
Activity focused on whether the process can reliably produce work that meets requirements.
Resource Loading
The assignment of work demand across people or resources during specific periods of the schedule.
FAQ

Stakeholder and Quality Management FAQ

How should an influence-interest grid be used?

Use it to choose an initial engagement posture, then verify the stakeholder's actual information needs, warning signs and decision role. Positions can change as the project moves between planning, testing and release.

What is the difference between assurance and control?

Quality assurance evaluates or improves the process used to create the result. Quality control inspects or tests the actual deliverable against requirements and acceptance criteria. A strong plan includes both process prevention and result evidence.

Why does resource capacity belong with quality management?

Overloaded people are more likely to rush reviews, delay tests or accept defects. Checking realistic capacity protects the schedule and the quality gate, and it gives decision-makers evidence for reallocation, resequencing or scope trade-offs.

What makes an acceptance criterion testable?

It states an observable result, threshold or clear yes-or-no condition connected to an approved requirement. The project should also identify who evaluates the evidence and what happens when the criterion is not satisfied.

Study strategy

Assessment move

Take one stakeholder and write the decision they influence, the evidence they need, the best format, cadence, sender and feedback route. Then choose one deliverable and connect its requirement to an acceptance criterion, assurance activity and control test. Finish with a resource-capacity check for the people performing that quality work.

This sequence prevents stakeholder, communication, quality and resource plans from becoming separate tables with no operational connection. Create an influence-interest map for four roles, then challenge each placement at a later project stage. Translate the map into specific communication actions rather than copying quadrant labels.

For quality, rewrite three subjective statements into observable criteria and identify who decides whether the evidence is sufficient. Label one preventive process review as assurance and one deliverable test as control, explaining why the distinction matters. Add the hours required for review and testing across every concurrent task assigned to the same person.

If demand exceeds capacity, protect acceptance-critical work and trace any proposed reallocation through dependencies and stakeholder commitments. Practise summarising the issue differently for a resource manager, sponsor and operational user, since each needs a different decision level. Close by updating the schedule, risk register and communication plan after the capacity decision.

This creates a connected control story rather than four parallel documents.

Working through Stakeholder and Quality Management in FIT5057? Sia is AskSia’s AI Project Management tutor — ask any FIT5057 Stakeholder and Quality Management 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.

A+Everything unlocked
Unlocks this Bible + all 171 of your subjects at Monash University, plus 1,000+ more Bibles across the AskSia library.
Sia - your FIT5057 tutor, unlimited, worked the way the exam marks it
The full 3-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works