Skip to content
Tutorials Center
My learning

Topics

Lesson 14 of 41 ยท Scope, Time and Cost

Activities and Resource Management

Learn what an activity is, how to define and sequence activities, the types of project resources, resource planning, histograms, over-allocation and resource management in agile.

The work breakdown structure tells you what to deliver. To plan when and by whom, you turn each work package into activities, then work out which resources are needed. This lesson covers both: defining activities and their dependencies, and planning, assigning and balancing people, equipment and materials.

What is an activity?

An activity is a distinct, scheduled piece of work performed during the project, with a duration, and normally consumes resources. Work packages are decomposed into activities (also called tasks). Activities are written as verb phrases: "Design login screen", "Run load test", "Train support staff".

A good activity:

  • Has a clear start and finish and a single owner.
  • Produces a visible output.
  • Can be estimated (typically a few days).
  • Is described so someone else could understand it.

Milestones are zero-duration points that mark significant events ("Design approved", "Go-live"). They help communication and gates.

Defining and sequencing

For each activity record an ID, description, predecessors, duration, resources. Dependencies come in four types:

Type Meaning Example
Finish-to-start (FS) B starts when A finishes Test after build
Start-to-start (SS) B starts when A starts Write docs while building
Finish-to-finish (FF) B finishes when A finishes Testing ends when fixing ends
Start-to-finish (SF) B finishes when A starts Rare: old system stops when new starts

Dependencies are also mandatory (physical or logical: foundations before walls), discretionary (best practice) or external (waiting for a supplier). Lead lets a successor start earlier; lag adds a delay (concrete must cure for 3 days).

Types of resources

Resources are anything the project consumes or uses.

  • People: developers, designers, testers, analysts.
  • Equipment: servers, devices, test rigs, vehicles.
  • Materials: supplies consumed by the work.
  • Facilities: rooms, labs, offices.
  • Software and licences.
  • Money (budget) and time, considered separately.

Resources are either renewable (a person: available again tomorrow) or non-renewable (materials, cash once spent).

Resource management

Resource management is planning, acquiring, developing and releasing resources so the right capability is available when needed. Steps:

  1. Estimate resources per activity (roles, quantity, skill, hours).
  2. Build a resource plan: calendar, availability, costs, rates.
  3. Acquire: assign internal staff, hire, rent or buy.
  4. Develop the team: training, coaching.
  5. Monitor and control: compare planned and actual usage.
  6. Release: return people and equipment when done.

Histograms and over-allocation

A resource histogram shows the hours or people needed per period. A bar above the available capacity means over-allocation: someone is booked for more than 100%. The schedule must then be changed (see Schedule Compression and Resource Leveling).

Python Find over-allocated people

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Resource cost

Multiply hours by rate to get cost; this ties directly into Cost Estimation.

Python Resource cost of activities

Press Run (or Ctrl + Enter) to see the result here.

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Resources in agile projects

Agile teams manage resources differently: a stable, cross-functional team replaces moving people between tasks, and capacity is measured in velocity or hours per sprint rather than per activity. Practical guidance:

  • Keep the team together; context switching is expensive.
  • Plan with capacity (team size x focus time minus holidays and meetings).
  • Treat one person's multi-project split as a cost; fragmentation reduces output.
  • Use the product backlog to choose work that fits the sprint capacity.
  • Adjust staffing between sprints, not mid-sprint.
flowchart LR
    A[Work package] --> B[Activities]
    B --> C[Estimate effort]
    C --> D[Assign resources]
    D --> E{Over-allocated?}
    E -- Yes --> F[Level or add capacity]
    F --> D
    E -- No --> G[Resource plan baselined]

Resource planning loops until workloads are feasible.

Why resource management matters

Poor resource management shows up as burnout, idle staff, bottlenecks around one key person and slipping dates. A common risk is a single point of failure: only one person can do a task. Plan cross-training and holidays. Also remember that adding people to a late project can make it later, because new people need onboarding and communication paths multiply.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Which is a well-written activity?

    Activities are verb phrases with a clear output.
  2. 2. In a finish-to-start dependency...

    FS is the most common dependency: B cannot start until A is complete.
  3. 3. A resource histogram bar above capacity means...

    More hours are planned than are available.
  4. 4. Which is a renewable resource?

    People are available again next period; materials and spent money are consumed.

Summary

  • Activities are verb-phrase pieces of work with duration and resources; milestones mark events.
  • Dependencies can be FS, SS, FF or SF and mandatory, discretionary or external.
  • Resource management covers estimating, acquiring, developing, monitoring and releasing people, equipment and materials.
  • Use histograms to spot over-allocation and keep agile teams stable.

Next: Cost Estimation