IS5540 Chap.6 Stakeholders, Resources and Communication
Stakeholders, Resources and Communication
Route information to authority
This chapter treats stakeholder analysis, resource planning and communication design as one system. Stakeholders carry interests and influence, resources add capacity and approval boundaries, and communication routes evidence to a person who can act.
A matrix is complete only when it names the owner, information, format, cadence, decision audience and retained record.
Analyse the relationship, not only the name
A stakeholder register identifies people or groups affected by the project or able to affect it. Analysis then considers interests, influence, impact, attitude, information needs and an appropriate engagement approach.
These characteristics can change as the project moves from planning to implementation and acceptance. A high-level grid is a starting point, not a permanent classification.
Record the evidence behind the position and review it when a decision, risk or deployment effect changes the relationship.
Treat resistance as project information
An opponent may reveal an unrecognised operational impact, a competing objective, weak legitimacy or a missing acceptance condition. More communication is not automatically the correct response.
First determine whether the concern changes scope, risk, priority, resource demand or the decision process. Then document the response and its owner.
Engagement is effective when stakeholder input can influence a relevant decision, not when a message has merely been sent or a meeting attendance box has been checked.
Connect resources to authority and availability
Resource planning identifies the skills, quantities, timing, source and approval route needed for work. A named person in a schedule is not available simply because software accepted the assignment.
Functional managers may control that person's commitment, calendars may restrict capacity and specialist work may have lead time. Validate estimates with the people doing the work, document assumptions and establish escalation for conflicts.
Responsibility for an activity also differs from authority to approve a baseline, accept a result or commit another department's staff.
Design communication around a decision
Start with what the audience must understand or decide, then select the content, detail, format, owner, channel, cadence and retained evidence.
A technical reviewer may need defect-level data, while a sponsor needs the consequence, options and requested decision. Users may need deployment effects and acceptance timing. A functional manager may need skill, duration and priority.
Sending the same spreadsheet to all four audiences transfers the burden of interpretation and can hide the decision that needs action.
Close the feedback and record loop
A communication matrix is incomplete if it ends at distribution. Define how questions, objections or approvals return, where the final decision is retained and who updates affected project records.
Sensitive stakeholder data also needs proportionate access and handling. Review communication effectiveness through observable outcomes: a decision arrived in time, a resource was committed, an acceptance concern changed the plan or an unresolved issue escalated. Volume of messages is not a substitute for those results.
What this chapter covers
- 01
Stakeholder interests and influence
- 02
Sponsor and user roles
- 03
Matrix resource authority
- 04
Resource calendars
- 05
Communication requirements
- 06
Decision audiences
- 07
Meeting and status records
Worked example · free
Redesign one status route
- 3Separate audience decisions.
- 3Choose routes and owners.
- 2Name retained evidence.
Key terms
- Stakeholder
- A person or group involved in or affected by project activity.
- Resource Calendar
- The approved record of when project resources are available and needed.
- Matrix Structure
- An arrangement in which project contributors retain functional reporting relationships.
- Communication Matrix
- A routing plan naming information, owner, recipient, frequency, format and deliverable.
- Decision Audience
- The person or group able to act on the information provided.
- Acceptance Owner
- The authorised role that judges whether a deliverable meets agreed criteria.
Stakeholders, Resources and Communication FAQ
Why is a stakeholder list not enough?
A list identifies people but does not show interests, influence, information needs or engagement actions. Management begins when those attributes are connected to a decision route and evidence showing how stakeholder input can affect requirements, risk, priority or acceptance.
Can a project manager assign any needed specialist?
Not necessarily. In a matrix structure the functional manager may retain authority over availability. The project manager negotiates the assignment, obtains approval and records the timing in the resource calendar before the schedule can rely on that person's capacity.
How do I choose communication frequency?
Frequency should follow the rate at which the relevant decision can change and the cost of delay. Weekly is not automatically correct. Define the trigger, audience and resulting action, then choose a cadence that reaches authority before the consequence becomes unavoidable.
Exam move
Take one issue and write four versions: the technical review, sponsor exception, user acceptance update and resource request. For each, identify owner, audience, decision, format, timing and retained record.
Working through Stakeholders, Resources and Communication in IS5540? Sia is AskSia’s AI Project Management tutor — ask any IS5540 Stakeholders, Resources and Communication 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.