vault backup: 2026-07-23 14:57:54
This commit is contained in:
@@ -1,103 +1,115 @@
|
||||
# Project Health
|
||||
Duration: 30–40 minutes
|
||||
|
||||
Duration: 30--40 minutes
|
||||
|
||||
## Definition
|
||||
|
||||
Use evidence to classify projects as healthy, at risk, or off track.
|
||||
**Project health** is a concise assessment of whether a project is
|
||||
likely to achieve its agreed outcome within its current commitments.
|
||||
|
||||
This lesson is part of the Project Management track and builds on the concepts learned in the previous lessons.
|
||||
A common model is:
|
||||
|
||||
- **Green:** on track; no material intervention required.
|
||||
- **Yellow:** at risk; attention or corrective action is needed.
|
||||
- **Red:** off track or blocked; significant intervention or decision
|
||||
is required.
|
||||
|
||||
## Simple Mental Model
|
||||
|
||||
The goal is not to add project-management bureaucracy. The goal is to make the project easier to understand, predict, and manage.
|
||||
> **Project health answers: Do I need to worry or intervene?**
|
||||
|
||||
Green does not mean people are busy. It means the evidence supports
|
||||
confidence in delivery.
|
||||
|
||||
## How It Works
|
||||
|
||||
We will examine this concept through four levels:
|
||||
Health should consider:
|
||||
|
||||
1. What the concept means.
|
||||
2. How a project owner should use it.
|
||||
3. How you should review or challenge it as the manager.
|
||||
4. How it should eventually appear in your project-management system.
|
||||
- Next milestone and target
|
||||
- Current forecast
|
||||
- Scope stability
|
||||
- Dependencies
|
||||
- Risks/issues
|
||||
- Capacity
|
||||
- Quality/acceptance
|
||||
- Decisions required
|
||||
|
||||
## Example
|
||||
Yellow should be an early-warning state, not a punishment.
|
||||
|
||||
The exercises for this lesson should use real projects from your environment such as Umami, Mogador, QA automation, data governance, website/Product initiatives, or projects dependent on DevOps and Security.
|
||||
Example:
|
||||
|
||||
The objective is to move from theory to a repeatable management practice.
|
||||
Umami's production validation is due Aug 20. Development is complete,
|
||||
but DevOps now expects the environment Aug 18 and QA needs four days.
|
||||
The deadline has not passed, but the project is already **Yellow**.
|
||||
|
||||
Do not wait until Aug 21 to discover the problem.
|
||||
|
||||
## How It Fits Into the Bigger Picture
|
||||
|
||||
The course builds progressively:
|
||||
|
||||
- Project vs operations establishes what kind of work we are managing.
|
||||
- Outcomes and Definition of Done establish what success means.
|
||||
- Scope establishes the project's boundaries.
|
||||
- Milestones establish meaningful progress.
|
||||
- Dependencies, estimation, prioritization, capacity, risks, and health make delivery more predictable.
|
||||
- Status reporting, meetings, ownership, and portfolio management make the system scalable.
|
||||
- Closing and the final PM system turn the concepts into an operating method.
|
||||
Milestones provide checkpoints. Dependencies and risks explain threats.
|
||||
Forecasting predicts delivery. Health compresses those signals into a
|
||||
portfolio-level indicator.
|
||||
|
||||
## My Company / Real-World Context
|
||||
|
||||
Your team works across departmental projects, Product work, operational incidents, tickets, data, QA, SEO/WCAG, and dependencies on IT teams such as DevOps and Security.
|
||||
Your Monday board currently shows execution status, but your management
|
||||
need is closer to:
|
||||
|
||||
The lesson should therefore be applied to an environment where:
|
||||
``` text
|
||||
Umami Yellow
|
||||
Supabase Green
|
||||
Mogador Red
|
||||
QA Automation Green
|
||||
Data Governance Yellow
|
||||
```
|
||||
|
||||
- Project owners are usually members of your own team rather than dedicated PMs.
|
||||
- Operational work regularly interrupts project work.
|
||||
- Product and IT are important cross-functional partners.
|
||||
- You need portfolio-level visibility without personally maintaining every task.
|
||||
- Project owners should increasingly draft and maintain their own project plans while you validate, challenge, prioritize, and escalate.
|
||||
Then you focus your attention on Yellow and Red rather than opening
|
||||
every project.
|
||||
|
||||
## CTO Perspective
|
||||
|
||||
The leadership objective is to move progressively from personally coordinating work toward building a management system that produces reliable outcomes.
|
||||
Health indicators enable **management by exception**. But the colors
|
||||
must be trustworthy.
|
||||
|
||||
The expected progression is:
|
||||
|
||||
```text
|
||||
Contributor → manages tasks
|
||||
Project Owner → drives milestones and delivery
|
||||
Manager → manages projects, priorities, risks and escalation
|
||||
Technology Leader → manages portfolio, capacity, outcomes and organizational trade-offs
|
||||
```
|
||||
If owners keep projects Green until failure is undeniable, the system is
|
||||
useless. Make early Yellow reporting useful rather than treating it as
|
||||
failure.
|
||||
|
||||
### Questions to Ask
|
||||
|
||||
- What information do I need to make a management decision?
|
||||
- What should the project owner be responsible for maintaining?
|
||||
- What requires my intervention?
|
||||
- What can be standardized across every project?
|
||||
- Is the process helping delivery, or merely creating administration?
|
||||
- What is the next milestone?
|
||||
- Is the forecast still credible?
|
||||
- What is the biggest risk?
|
||||
- Is scope stable?
|
||||
- Are dependencies committed?
|
||||
- What specifically would return Yellow to Green?
|
||||
- Does this need my intervention?
|
||||
|
||||
## Meeting Scenario
|
||||
|
||||
**Situation:**
|
||||
|
||||
A project owner gives you an update, but the information does not make it clear whether the project will achieve its intended outcome.
|
||||
**Situation:** A project owner reports Green because no deadline has
|
||||
been missed, but a critical vendor deliverable has no confirmed date.
|
||||
|
||||
**Possible response:**
|
||||
|
||||
> Let's bring this back to the project plan. Show me where we are against the next meaningful checkpoint, what is at risk, and what decision or help you need from me.
|
||||
> I would mark this Yellow. Health should reflect whether we're likely
|
||||
> to hit the commitment, not only whether we've already missed it. What
|
||||
> action will give us confidence in the vendor dependency?
|
||||
|
||||
## Key Takeaways
|
||||
|
||||
- The purpose of project management is predictable delivery, not documentation for its own sake.
|
||||
- Project owners should own increasingly more of the planning and maintenance.
|
||||
- Your role is to challenge assumptions, establish priorities, remove/escalate blockers, and manage the portfolio.
|
||||
- Every concept learned should eventually contribute to one lightweight common project template.
|
||||
- The final system should make exceptions and problems visible without requiring you to inspect every task.
|
||||
- Health is forward-looking.
|
||||
- Green/Yellow/Red need shared definitions.
|
||||
- Yellow is an early-warning state.
|
||||
- Percent complete is not project health.
|
||||
- Health should reflect milestones, risks, dependencies, scope, and
|
||||
forecast.
|
||||
- Reliable health enables management by exception.
|
||||
|
||||
## Related Concepts
|
||||
|
||||
- [[Projects vs Operations]]
|
||||
- [[Project Outcome]]
|
||||
- [[Definition of Done]]
|
||||
- [[Scope]]
|
||||
- [[Milestone]]
|
||||
- [[Dependencies]]
|
||||
- [[Capacity]]
|
||||
- [[Risk]]
|
||||
- [[Project Health]]
|
||||
- [[Portfolio Management]]
|
||||
- \[\[Milestones vs Tasks\]\]
|
||||
- \[\[Risk Management\]\]
|
||||
- \[\[Dependencies\]\]
|
||||
- \[\[Status Reporting\]\]
|
||||
- \[\[Portfolio Management\]\]
|
||||
|
||||
Reference in New Issue
Block a user