Skip to content
Tutorials Center
My learning

Topics

Lesson 40 of 41 ยท Projects and Practice

Capstone: Plan a Project End to End

A hands-on capstone: build a WBS, compute the critical path, size the budget with risk reserves, simulate schedule uncertainty and track earned value, all in runnable Python.

In this project you plan a small but realistic project from start to finish: a community event app launched in time for a conference. You will build the work breakdown structure, find the critical path, estimate cost and reserves, simulate the schedule risk, and compute earned value halfway through. Each step is a runnable Python program and builds on the one before; it ties together the whole course.

Work through it like a real planner: run the code, change the numbers, and write down what you decide.

The brief

  • Goal: deliver a mobile-friendly event app (schedule, speakers, notifications) in 12 weeks, before the conference.
  • Budget ceiling: 120,000.
  • Team: 2 developers, 1 designer, 1 tester, part-time product owner, project manager.
  • Constraints: the conference date cannot move; venue Wi-Fi is unreliable; the payment of ticket data comes from an external vendor.
  • Sponsor wants a weekly one-page report.

Step 1: Work breakdown structure

A WBS breaks the deliverable into smaller pieces until each piece can be estimated, assigned and tracked. Aim for work packages of roughly 1 to 10 days.

flowchart TD
  A["Event app"] --> B["1 Plan"]
  A --> C["2 Design"]
  A --> D["3 Build"]
  A --> E["4 Test and launch"]
  B --> B1["Requirements"]
  C --> C1["UX flows"]
  C --> C2["Visual design"]
  D --> D1["Backend and data"]
  D --> D2["Frontend"]
  D --> D3["Notifications"]
  E --> E1["Testing"]
  E --> E2["Launch"]

Each leaf becomes an activity with an owner, an estimate and a cost.

Python Activities with durations, owners and dependencies

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.

Step 2: The critical path

The critical path is the longest chain of dependent activities; any delay on it delays the project. We compute earliest start and finish in a forward pass, latest times in a backward pass, and the float (slack) of each activity.

Python Forward and backward pass

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.

The path A, B, C, E, G, H is critical; D and F have float. The schedule is about 40 working days (eight weeks), which leaves about four weeks of buffer in the 12-week window; the next steps check how much of that buffer uncertainty eats. Activities with float (the backend D, notifications F) can slip a little without moving the launch, which is useful for resource leveling.

Step 3: Budget and reserves

A professional budget adds contingency for identified risks (see risk management) and sometimes a management reserve for unknowns.

Python Budget with contingency

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.

The total fits the 120,000 ceiling with margin. Adding more scope would eat into the margin, so every addition must go through change control.

Step 4: Schedule risk

Now check the 12-week commitment against uncertainty using the three-point estimates and a simulation, as in Monte Carlo schedule risk.

Python Probability of finishing within 9 and 10 weeks

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.

If the P80 date is inside the 12-week window you have a defensible commitment; if not, discuss options with the sponsor: reduce scope, add a developer to the frontend, start the vendor integration earlier, or move the launch date.

Step 5: Track with earned value

Suppose that at the end of week 6 you have this status.

Python Earned value at week 6

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.

The team is behind (SPI 0.84) and slightly over cost. At this pace the project would finish at about 14 weeks, after the conference. That is a trigger for decisions, not for hoping.

Your tasks

Do these exercises, using the programs above:

  1. Recovery plan. Which activities are on the critical path? Choose one to crash (add a person) and recompute the duration and cost. Then try fast tracking: start Frontend before Visual design is finished.
  2. Scope trade. Notifications are not on the critical path. Delete them. How much money and risk do you save? What would you tell the sponsor?
  3. Risk register. Write ten risks for this project with owners, triggers and responses (use the risk lesson).
  4. Stakeholder plan. List six stakeholders, place them on the power-interest grid and write the engagement approach (stakeholder management).
  5. Status report. Write the week 6 one-pager for the sponsor, with RAG status, top risks, decisions needed.
  6. Closure. List closure tasks and the lessons you think you will record.

Keep your answers. Comparing your plan with a colleague's is one of the best ways to find blind spots.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. In the capstone plan, why are D (Backend) and F (Notifications) not on the critical path?

    Activities with float can slip without delaying the end date; critical path activities have zero float.
  2. 2. At week 6 SPI = 0.84. What does it mean?

    SPI = EV / PV, so it measures progress against plan.
  3. 3. Which technique adds people to critical-path activities to shorten the schedule?

    Crashing trades cost for time on the critical path; fast tracking overlaps activities.
  4. 4. Why simulate the schedule instead of using the PERT total only?

    Simulation handles path merges and gives confidence levels such as P80.

Summary

  • A project plan chains WBS, estimates, dependencies, critical path, budget with reserves, risk analysis and tracking.
  • Float tells you where the schedule can absorb delays; the critical path is where it cannot.
  • Contingency comes from risks; the baseline plus management reserve gives the budget.
  • Simulation turns the schedule into confidence levels; earned value tells you where you stand.
  • Decisions, not charts, are the output: recover, trade scope, or reset expectations.

Next: Practice Questions and Certifications