Resource Management and Team Building: RACI, Resource Leveling and Team Development Stages

Software is made by people, and the best plan fails if the right people are not available, clear about their roles or working well together. Resource management covers identifying, acquiring and organising the team and equipment a project needs; team development covers helping those people work effectively. For an IT project manager, this is where planning meets leadership.

Planning Resources

Start from the WBS and schedule: for each work package, identify the skills, people, tools and environments needed. Typical IT resources include business analysts, solution architects, developers, testers, DevOps engineers, designers, data specialists, trainers and the supporting infrastructure such as development and test environments, licences and devices. Document them in a resource management plan covering how resources will be identified, acquired, trained, managed and released.

Estimate not only how many people but when. A resource histogram shows demand per role over time, exposing peaks and valleys. A tester needed at 100 per cent for two weeks is different from a tester needed at 20 per cent for ten.

Roles and Responsibilities: The RACI Matrix

Confusion over who decides, who does and who must be told wastes huge amounts of time. A RACI matrix assigns, for each task or deliverable, one of four codes:

  • R, Responsible: does the work.
  • A, Accountable: ultimately answerable and approves it. Only one A per item.
  • C, Consulted: gives input before the work is done (two-way).
  • I, Informed: told of progress or results (one-way).
DeliverableSponsorProject managerBusiness analystTech leadTest lead
Approve charterARCCI
Requirements documentACRCC
Solution architectureICCA/RC
Test planIACCR
Go-live decisionARCCC

If a row has no A, nobody is accountable; if it has two, decisions stall. Review the matrix with the people named in it.

Acquiring the Team

In practice, you rarely get your ideal team. Resources come through:

  • Negotiation with functional managers who own the people.
  • Pre-assignment, where key people were named in the proposal or charter.
  • Recruitment of new employees or contractors.
  • Virtual teams spread across locations and time zones.
  • Procurement of vendor staff; see Vendor and Procurement Management.

In a matrix organisation, team members report to a functional manager and also work for you. They have two bosses, so agree early on how priorities, performance feedback and time allocation will be handled.

Resource Leveling and Smoothing

When the schedule demands more of a person than is available, you have an overallocation. Two techniques resolve it:

  • Resource leveling: adjust the schedule to fit resource limits. Tasks may be delayed or split, and the project end date often moves.
  • Resource smoothing: adjust activities within their float so resource peaks reduce, without changing the critical path or end date.

Leveling protects people; smoothing protects the date. Often you need both. See Project Scheduling for float.

Tuckman’s Stages of Team Development

StageWhat it looks likeWhat the project manager does
FormingPoliteness, uncertainty, dependence on the leaderClarify goals, roles and ways of working
StormingConflict over approach, status and workloadFacilitate, resolve conflict constructively, keep focus on goals
NormingAgreed practices, growing trustReinforce norms, delegate more
PerformingHigh collaboration and autonomyRemove obstacles, recognise results, stay out of the way
AdjourningProject ends, team disbandsCelebrate, capture lessons, support transitions

Teams may move back when members join or leave, so expect storming to return. Do not treat early conflict as failure; skipping it usually means problems are hidden.

Team Building Practices That Work

  1. Hold a proper kick-off where the team hears the purpose and shapes the ways of working.
  2. Create team agreements on communication, meeting norms, decision making and quality standards.
  3. Co-locate or create virtual routines such as short daily stand-ups and shared channels for distributed teams.
  4. Recognise contributions specifically and publicly.
  5. Develop skills: pairing, workshops and cross-training reduce single points of failure.
  6. Protect the team from constant interruption and excessive overtime.

For Agile teams, see Building High-Performing Scrum Teams.

Leadership and Motivation

Project managers use different power bases: formal authority, expertise, reward, and, most effective, referent power (being respected). Most IT project managers rely on influence rather than command. A few principles help: explain the why behind the work, give people autonomy over the how, offer honest feedback early, and make it safe to raise problems. Motivation theories such as Herzberg’s distinguish hygiene factors (pay, conditions) from motivators (achievement, recognition, meaningful work); remove dissatisfaction first, then build motivation.

Managing Conflict

Common sources of project conflict are schedule pressure, resource contention, technical disagreements and priorities. Typical responses, from most to least effective in the long run, are collaborating or problem solving (find a solution that satisfies both parties), compromising, accommodating or smoothing, forcing or directing, and withdrawing. Choose the style to suit the situation: forcing may be right in an emergency, but poor for building trust. See Conflict Management for Scrum Masters for practical techniques that apply to any team.

Managing Performance and Releasing Resources

Track team performance informally through conversations and formally through feedback and, where relevant, input to line managers. Address problems early and privately. When people finish their part of the work, release them promptly and thank them; keeping idle people on the project inflates cost, while releasing too soon leaves gaps in knowledge.

Common Mistakes

  • Planning people at 100 per cent availability.
  • Leaving roles undefined, so tasks are dropped or duplicated.
  • Adding people to a late project without allowing for ramp-up.
  • Avoiding conflict until it becomes a crisis.
  • Neglecting remote team members.
Key takeaways
  • Plan resources by skill, quantity and timing; use histograms to spot overloads.
  • RACI clarifies who does, approves, advises and is informed, with one accountable person per item.
  • Leveling changes the schedule to fit resources; smoothing uses float.
  • Teams move through forming, storming, norming and performing; manage each stage deliberately.

Related Lessons