Project Resource and Stakeholder Management
Open in the Padhaiko app13.1 Developing the resource management plan and team charter
ICT projects rely on two categories of resources: team (human) resources (developers, architects, QA engineers, UI/UX designers, DevOps engineers) and physical resources (servers, cloud compute quotas, testing devices, networking gear, software licenses). Plan Resource Management defines how to estimate, acquire, manage, and use both categories.
13.1.1 Resource Management Plan and RACI Matrix
The Resource Management Plan documents:
- How team and physical resources are identified, acquired, and released.
- Clear roles, authority, responsibility, and competency definitions.
- Project organization charts and Responsibility Assignment Matrices (RAM)—most commonly a RACI Chart.
RACI Responsibility Assignment Matrix
A RACI chart maps project deliverables or activities (rows) against team roles (columns) using four codes:
- R — Responsible: The person(s) who perform the actual work.
- A — Accountable: The single owner with final decision/approval authority (strictly one
Aper activity to avoid ambiguity). - C — Consulted: Subject-matter experts providing two-way input before work is finalized.
- I — Informed: Stakeholders kept updated via one-way communication after decisions or milestones.
13.1.2 Team Charter
The Team Charter is a collaborative document created by the project team early in the project to establish clear behavioral expectations and reduce interpersonal friction:
- Team Values & Working Agreements: Core hours, code-review turnaround expectations, definition of done.
- Communication Guidelines: Preferred tools (Slack for quick queries, Jira for task state, email for formal sign-off).
- Decision-Making & Conflict Resolution: How technical deadlocks are resolved (e.g., consensus first, then Architecture Lead tie-break).
- Meeting Etiquette: Punctuality, cameras-on norms for remote stand-ups, preparation rules.
13.2 Estimating activity resources
Estimate Activity Resources determines the type and quantities of team members, equipment, materials, and supplies required to perform each schedule activity. Accurate resource estimation is directly coupled with cost and duration estimation.
Key Estimation Techniques:
- Bottom-Up Estimating: Estimating resource requirements (e.g., developer-days, cloud VM hours) at the lowest activity level and aggregating up to work packages and control accounts.
- Analogous & Parametric Estimating: Using historical ratios from similar ICT projects (e.g., , or ).
- Alternatives Analysis: Evaluating trade-offs between different resource mixes—for instance, hiring senior vs. junior engineers, buying automated test infrastructure vs. manual testing hours, or renting cloud GPUs vs. purchasing on-premise servers.
- Resource Breakdown Structure (RBS) & Resource Calendars: The RBS hierarchically categorizes resources by type (Personnel Developers/QA; Hardware Servers/Test Phones), while Resource Calendars record when specific people or lab equipment are actually available (holidays, shared shifts, maintenance windows).
13.3 Acquiring resources
Acquire Resources is the process of obtaining team members, facilities, equipment, materials, supplies, and other resources necessary to complete project work. Because project managers in matrix organizations often do not have direct administrative authority over staff, resource acquisition relies on negotiation and clear criteria.
| Technique | When and How It Is Used in ICT Projects |
|---|---|
| Pre-Assignment | Key specialists (e.g., Lead Architect) are named in advance inside the project charter or winning vendor proposal |
| Negotiation | Project Manager negotiates with functional managers (for internal developers) or other PMs (for shared QA/DevOps) |
| Acquisition (Procurement) | External contractors, cloud capacity, or specialized hardware are procured from outside vendors via contracts |
| Virtual Teams | Geographically distributed specialists collaborate across time zones via Git, video conferencing, and cloud IDEs |
| Multi-Criteria Decision Analysis | Candidate staff or tools are scored objectively on weighted attributes (availability, cost, technical skill, domain experience) |
13.4 Developing the project team
Develop Team focuses on improving individual competencies, strengthening team member interaction, and fostering a collaborative environment to boost project performance and reduce staff turnover.
13.4.1 Tuckman Ladder of Team Development
Psychologist Bruce Tuckman identified five sequential stages that teams pass through (and may temporarily regress through when new members join):
Tuckman's Five Stages of Team Development
- Forming: Members meet, learn project goals, and behave politely and independently; reliance on PM direction is high.
- Storming: Technical disagreements, role conflicts, and clashes over work style emerge as real work begins.
- Norming: Members resolve differences, establish trust and shared workflows (team charter norms), and collaborate smoothly.
- Performing: The team operates as a cohesive, autonomous, high-trust unit focused on problem-solving and delivery.
- Adjourning: Work finishes, deliverables are handed over, and the team disbands or transitions to new projects.
13.4.2 Motivation Theories and Team-Building Tools
- Maslow's Hierarchy of Needs: Physiological Safety Social/Belonging Esteem Self-Actualization (engineers perform best when pay/job security are settled and work offers autonomy and mastery).
- Herzberg's Two-Factor Theory: Distinguishes Hygiene Factors (salary, workspace, company policies—prevent dissatisfaction when adequate, but do not motivate) from Motivating Agents (recognition, challenging technical work, growth, responsibility).
- McGregor's Theory X and Theory Y: Theory X assumes workers dislike work and need strict micromanagement; Theory Y assumes skilled knowledge workers are self-motivated and thrive under empowerment.
- Practical Tools: Colocation ("war room" for intense release sprints), Training (upskilling on new cloud/AI stacks), Recognition & Rewards (tied to achievable behaviours rather than zero-sum competition), and Individual/Team Assessments.
13.5 Managing the project team
Manage Team tracks team member performance, provides constructive feedback, resolves interpersonal and technical issues, and manages team changes to optimize delivery.
13.5.1 Powers of a Project Manager
- Legitimate (Formal): Authority granted by organizational position.
- Reward: Ability to grant bonuses, promotions, or desirable assignments.
- Penalty (Coercive): Ability to impose disciplinary consequences (least effective long-term).
- Expert: Respect earned from deep technical or domain competence.
- Referent: Influence gained through personal trust, charisma, and credibility.
(Research shows Expert and Reward power are the most effective for ICT teams, whereas relying heavily on Penalty erodes morale.)
13.5.2 Conflict Management Techniques
Conflict in ICT projects most commonly stems from schedules, project priorities, and resource competition (not personality alone). The five standard conflict resolution strategies are:
| Technique | Outcome Style | Behavior & Best Use Case |
|---|---|---|
| Collaborate / Problem Solve | Win–Win | Confronts the root issue openly, integrates multiple viewpoints for consensus (best long-term solution) |
| Compromise / Reconcile | Lose–Lose | Each party gives up something to reach a middle ground quickly when neither can win fully |
| Smooth / Accommodate | Yield–Win | Emphasizes agreement and downplays differences to preserve harmony temporarily |
| Force / Direct | Win–Lose | Imposes one viewpoint using formal power; reserved for emergencies or safety/security crises |
| Withdraw / Avoid | Lose–Leave | Retreats from or postpones the conflict; useful for trivial issues or when tempers need to cool |
13.6 Monitoring and controlling resources
Control Resources ensures that the physical resources (servers, cloud environments, test devices, licenses, facilities) assigned to the project are available as planned, monitors planned versus actual utilization, and takes corrective action when shortages or bottlenecks occur. (Note: Human team dynamics are handled by Manage Team, whereas physical/equipment allocations are governed by Control Resources.)
Key techniques include:
- Performance Reviews & Trend Analysis: Comparing planned vs. actual server/lab utilization, cloud burn rates, and equipment downtime.
- Resource Optimization Techniques:
- Resource Leveling: Adjusts activity start/finish dates based on resource constraints (e.g., only one load-testing lab available) so demand never exceeds supply—often extends the critical path.
- Resource Smoothing: Adjusts activities only within their free/total float to flatten peaks in resource demand without delaying the project end date.
- Alternatives & Cost–Benefit Analysis: Deciding whether to burst into paid cloud nodes versus delaying non-critical batch jobs.
1
A PM must acquire a Senior DevOps Engineer using Multi-Criteria Decision Analysis with four weighted criteria: Cloud/CI Skill (), Immediate Availability (), Cost Fit (), and Domain Experience (). Candidate scores (out of ) are:
| Criterion | Weight | Candidate 1 | Candidate 2 | Candidate 3 |
|---|---|---|---|---|
| Cloud / CI Skill | ||||
| Immediate Availability | ||||
| Cost Fit | ||||
| Domain Experience |
Compute each candidate's weighted score, select the best candidate, and construct a 3-activity RACI row covering CI/CD Setup, Security Audit, and UAT Sign-off across the roles PM, DevOps, and QA Lead.
Weighted Candidate Scores:
- Candidate 1:
- Candidate 2:
- Candidate 3:
Candidate 2 scores highest () due to immediate availability and strong cost fit.
Constructing the RACI Matrix (Exactly One A per Row):
| Activity | PM | DevOps | QA Lead |
|---|---|---|---|
| CI/CD Setup | A | R | C |
| Security Audit | I | C | A / R |
| UAT Sign-off | A | I | R |
(Each row has exactly one A for clear accountability.)
Weighted scores: Candidate 1 , Candidate 2 , Candidate 3 select Candidate 2. The RACI matrix assigns clear R, A, C, and I roles with strictly one A per activity.
2
During a deployment sprint, four tasks require specialized Staging Servers as follows:
- Task A: Days , requires servers/day (Critical, Total Float )
- Task B: Days , requires servers/day (Non-critical, Total Float — can start Day 1 or Day 2)
- Task C: Day , requires servers/day (Non-critical, Total Float — can run Day 2, 3, or 4)
- Task D: Days , requires servers/day (Critical, Total Float )
- Compute the total server-days required and the daily server demand under the Early-Start schedule.
- Only staging servers are available per day. Use Resource Smoothing (within available float, keeping the deadline) to eliminate the overload.
Total Server-Days and Early-Start Daily Demand:
Average demand . Under Early-Start:
- Day 1: A () + B () servers
- Day 2: A () + B () + C () (exceeds limit of !)
- Day 3: B () + D () servers
- Day 4: D () servers
Applying Resource Smoothing Within Float:
- Day 1: A () + B () servers
- Day 2: A () + B () servers
- Day 3: B () + D () servers
- Day 4: D () + C () servers
Peak demand drops from to servers/day, staying within the capacity with zero schedule delay.
- Total demand is (average ); Early-Start peaks at servers on Day 2.
- Shifting Task C within its float to Day 4 smooths daily demand to , keeping peak demand without extending the sprint.
13.7 Identifying stakeholders
Project Stakeholder Management includes the processes required to identify the people, groups, or organizations that could impact or be impacted by the project, analyze stakeholder expectations and impact, and develop management strategies to engage them effectively.
13.7.1 Stakeholder Identification and Classification Models
Identify Stakeholders begins during initiation (when the Project Charter is created) and repeats continuously as the project evolves. An ICT project's stakeholders typically include the sponsor, end users, system administrators, cybersecurity/compliance officers, external vendors, regulators, and support teams.
Power/Interest Grid and Salience Model
- Power/Interest Grid: Classifies stakeholders along two axes—level of Power (authority) and level of Interest (concern)—yielding four distinct strategies:
- High Power, High Interest: Manage Closely (key players—e.g., Project Sponsor, Product Owner).
- High Power, Low Interest: Keep Satisfied (e.g., Chief Financial Officer, Regulatory Auditor).
- Low Power, High Interest: Keep Informed (e.g., End-User Representatives, Helpdesk Staff).
- Low Power, Low Interest: Monitor with minimal effort (e.g., peripheral departments).
- Salience Model: Evaluates stakeholders across three attributes—Power (ability to impose their will), Urgency (need for immediate attention), and Legitimacy (appropriateness of their involvement).
The primary output is the Stakeholder Register, containing:
- Identification Info: Name, organizational position, location, contact, project role.
- Assessment Info: Major requirements, expectations, potential influence, phase of highest interest.
- Stakeholder Classification: Internal/external, supporter/neutral/resistor, Power/Interest quadrant.
13.8 Planning, managing and monitoring stakeholder engagement
13.8.1 Planning Stakeholder Engagement
Plan Stakeholder Engagement develops tailored strategies to effectively involve stakeholders throughout the project life cycle based on their needs, interests, and potential impact. Its central analytical tool is the Stakeholder Engagement Assessment Matrix, which compares each key stakeholder's Current () engagement level against their Desired () engagement level across five states:
| Level | Description |
|---|---|
| Unaware | Unaware of the project and its potential impacts |
| Resistant | Aware of the project and resistant to the change it brings |
| Neutral | Aware of the project, neither supportive nor resistant |
| Supportive | Aware of the project and supportive of its goals and deliverables |
| Leading | Aware of the project and actively engaged in ensuring its success |
Where a gap exists between and (e.g., a high-power department head is currently Resistant when Supportive is needed), the Stakeholder Engagement Plan defines targeted actions to close the gap.
13.8.2 Managing and Monitoring Stakeholder Engagement
- Manage Stakeholder Engagement: Proactively communicating and working with stakeholders to satisfy their needs, address concerns before they escalate into blockers, resolve conflicts, and secure timely approvals (e.g., early UI demos, executive briefings, user-champion workshops).
- Monitor Stakeholder Engagement: Continuously tracking overall stakeholder relationships, reviewing the Stakeholder Register as personnel or priorities shift, and adjusting engagement tactics whenever support drops or new stakeholders emerge.
3
Exam-Style Design Example: A university is migrating from paper grading to a digital ERP grading portal. Four stakeholders are identified: (1) Vice-Chancellor / Sponsor, (2) Senior Faculty Union Chair (worried about extra workload), (3) Exam Office Clerks, and (4) Campus Maintenance Supervisor. Classify each on the Power/Interest Grid, build a Stakeholder Engagement Assessment Matrix ( vs. ), and propose targeted engagement actions to close any gaps.
Power/Interest Classification:
- Vice-Chancellor (High Power, High Interest): Manage Closely — holds budget/policy authority and actively sponsors digital transformation.
- Senior Faculty Union Chair (High Power, Low-to-Moderate Interest initially / High impact): Keep Satisfied / Manage Closely — can block faculty adoption if concerns go unaddressed.
- Exam Office Clerks (Low Power, High Interest): Keep Informed — daily system users affected directly by workflow changes.
- Campus Maintenance Supervisor (Low Power, Low Interest): Monitor — minimal involvement beyond basic server-room power notifications.
Stakeholder Engagement Assessment Matrix and Action Plan:
| Stakeholder | Unaware | Resistant | Neutral | Supportive | Leading | Gap-Closure Action |
|---|---|---|---|---|---|---|
| Vice-Chancellor | Bi-weekly executive demos and steering sign-offs | |||||
| Faculty Union Chair | Early prototype demo showing time saved; co-design UAT | |||||
| Exam Office Clerks | Hands-on training workshops and dedicated helpdesk | |||||
| Maintenance Supervisor | Send brief rollout notice for UPS/power continuity |
By pairing the Power/Interest Grid with the Engagement Matrix, the PM prioritizes closing the Faculty Union Chair's Resistant Supportive gap through early co-design and workload-reduction demos, keeps Exam Clerks informed via training, empowers the Vice-Chancellor to lead sponsorship, and lightly monitors peripheral stakeholders.
Exercises
Practice Exercises — Project Resource and Stakeholder Management
Explain the purpose of a Team Charter and a RACI Matrix in ICT resource planning. Why must every row in a RACI matrix have strictly one Accountable (A) owner?
Team Charter vs. RACI Matrix:
- Team Charter: Team-authored agreement setting shared values, communication norms, meeting etiquette, and conflict resolution guidelines to prevent friction.
- RACI Matrix: Maps tasks/deliverables against team roles using Responsible (
R), Accountable (A), Consulted (C), and Informed (I).
Why Strictly One A per Activity: If zero roles are marked A, nobody takes final ownership when an activity stalls; if two or more roles share A, accountability blurs and decisions deadlock. One A ensures clear sign-off authority even when multiple people share R.
The Team Charter aligns team working norms, while the RACI Matrix clarifies task roles (R, A, C, I). Strictly one A per row guarantees unambiguous final ownership and prevents deadlocks.
An IT manager evaluates two QA Lead candidates using Multi-Criteria Decision Analysis with weights: Automation Skill (), Domain Knowledge (), and Availability (). Candidate Alpha scores and Candidate Beta scores . Compute each candidate's weighted score and identify the selected lead.
Computing Weighted Scores:
- Candidate Alpha:
- Candidate Beta:
Selection: Candidate Beta scores and is selected.
Candidate Alpha , Candidate Beta ; select Candidate Beta.
Describe Tuckman's five stages of team development and compare the five conflict resolution techniques, stating which produces a Win–Win outcome and when Force/Direct is justified.
Tuckman's Five Stages:
- Forming: Team assembles politely; high reliance on PM guidance.
- Storming: Technical and role conflicts emerge.
- Norming: Trust develops and team norms stabilize.
- Performing: Autonomous, high-efficiency collaboration.
- Adjourning: Project closes and team disbands.
Five Conflict Resolution Techniques:
- Collaborate / Problem Solve (Win–Win): Best long-term technique; resolves root causes via open dialogue.
- Compromise / Reconcile (Lose–Lose): Mutual concessions for quick resolution.
- Smooth / Accommodate (Yield–Win): Emphasizes harmony temporarily over differences.
- Force / Direct (Win–Lose): Imposes one decision via authority; justified only in emergencies or critical security/safety failures requiring immediate action.
- Withdraw / Avoid (Lose–Leave): Defers conflict when issues are trivial or emotions need to cool.
Tuckman's stages are Forming Storming Norming Performing Adjourning. Conflict techniques are Collaborate (Win–Win), Compromise (Lose–Lose), Smooth (Yield–Win), Force (Win–Lose—justified only in emergencies), and Withdraw (Lose–Leave).
Distinguish between Manage Team and Control Resources, and between Resource Leveling and Resource Smoothing. Suppose a 3-day test cycle has tasks requiring for Days , for Days (with float), and on Day . Compute total server-days and show how Resource Smoothing fits the workload within a limit.
Manage Team vs. Control Resources & Leveling vs. Smoothing:
- Manage Team handles human performance, feedback, and conflict; Control Resources monitors and regulates physical resources (servers, labs, hardware, licenses).
- Resource Leveling resolves over-allocation even if it extends the critical path; Resource Smoothing adjusts activities strictly within float without changing the project end date.
Total Server-Days and Resource Smoothing:
Early-Start demand is , which already peaks at ; however, shifting the floating task by to Days yields , balancing late-sprint utilization within the deadline and cap.
Manage Team governs human teams while Control Resources governs physical assets; Leveling can extend end dates whereas Smoothing stays inside float. Total demand is , and smoothing shifts the floating task within its float while keeping peak demand servers and preserving the finish.
Explain how the Power/Interest Grid and the Stakeholder Engagement Assessment Matrix work together to plan, manage, and monitor stakeholder engagement in an ICT system rollout.
Power/Interest Grid (Categorization): Groups stakeholders into four quadrants: Manage Closely (High Power, High Interest), Keep Satisfied (High Power, Low Interest), Keep Informed (Low Power, High Interest), and Monitor (Low Power, Low Interest), determining communication intensity.
Engagement Assessment Matrix ( vs. ) and Ongoing Management: Maps each key stakeholder's Current () vs. Desired () state across Unaware, Resistant, Neutral, Supportive, Leading. Where , the PM executes targeted actions (Manage Stakeholder Engagement) such as demos or training, and continuously reassesses relationships as phases or personnel change (Monitor Stakeholder Engagement).
The Power/Interest Grid prioritizes communication effort by authority and concern, while the -to- Engagement Assessment Matrix identifies exact engagement gaps so the PM can convert resistant or neutral key stakeholders into supportive/leading partners and continuously monitor shifts.