# Project Management

## Course Progress

- [x] [[Projects vs Operations]]
- [x] [[Outcomes and Definition of Done]]
- [x] [[Scope and Scope Creep]]
- [x] [[Milestones vs Tasks]]
- [ ] [[Dependencies]]
- [ ] [[Estimation and Forecasting]]
- [ ] [[Prioritization]]
- [ ] [[Capacity and WIP]]
- [ ] [[Risk Management]]
- [ ] [[Project Health]]
- [ ] [[Status Reporting]]
- [ ] [[Meetings and Follow-up]]
- [ ] [[Ownership and Delegation]]
- [ ] [[Portfolio Management]]
- [ ] [[Closing Projects]]
- [ ] [[Building My PM System]]

---

## Learning Path

### Foundation

1. [[Projects vs Operations]]
2. [[Outcomes and Definition of Done]]
3. [[Scope and Scope Creep]]
4. [[Milestones vs Tasks]]

### Planning and Delivery

5. [[Dependencies]]
6. [[Estimation and Forecasting]]
7. [[Prioritization]]
8. [[Capacity and WIP]]
9. [[Risk Management]]

### Managing Projects

10. [[Project Health]]
11. [[Status Reporting]]
12. [[Meetings and Follow-up]]
13. [[Ownership and Delegation]]

### Managing the Portfolio

14. [[Portfolio Management]]
15. [[Closing Projects]]

### Build the System

16. [[Building My PM System]]

---

## End Goal

Build a repeatable project management system where:

- Every project has a clear outcome and Definition of Done.
- Scope and major milestones are agreed before commitment.
- A project owner within the team drives each project.
- Project owners maintain their own project information.
- Dependencies, risks and blockers become visible early.
- Estimates account for actual capacity and operational interruptions.
- Scope changes result in explicit trade-offs.
- I manage through milestones and outcomes rather than individual tasks.
- Project health tells me where my intervention is required.
- The portfolio shows what the team has committed to and whether we have capacity for more work.
- Monday.com becomes a management tool rather than a project list that nobody updates.