The Discipline of Delivery · companion to Chapter 3
Project Management Basics
The lifecycle, the iron triangle, methodologies and the key documents — the ground rules everything else sits on.
Project management basics mastery for software PMs
🏠
What is project management?
The science of delivering outcomes under constraints
Project management is the application of knowledge, skills, tools, and techniques to deliver a defined outcome within constraints of scope, time, cost, and quality. A project is temporary — it has a defined start, end, and purpose. Operations are ongoing. PMs manage projects; operations managers manage the steady state.
Project vs programme vs portfolio
A project delivers one outcome. A programme is a group of related projects managed together for strategic benefit. A portfolio is the collection of all projects and programmes an organisation runs. PMs manage projects; programme managers coordinate dependencies across them.
PM vs Scrum Master vs Product Owner
A PM owns delivery: scope, timeline, budget, risk, stakeholders. A Scrum Master is a servant-leader facilitating agile ceremonies and removing team blockers. A Product Owner owns the backlog and business value. In SAFe, all three roles coexist.
Waterfall vs Agile vs Hybrid
Waterfall: sequential phases, requirements locked upfront. Best for stable, well-understood scope. Agile: iterative delivery in sprints, embraces change. Best for evolving requirements. Hybrid: waterfall governance + agile execution — most common in enterprise software.
What a PM actually does daily
Track progress against plan, manage risks and issues, communicate status to stakeholders, remove blockers, manage scope changes, coordinate dependencies, escalate decisions, update the project charter and logs. The PM is the integration point — everything passes through them.
Core PM knowledge areas (PMBOK)
↻
Project lifecycle — 5 process groups
What the PM does in each phase
🔺
Triple constraint simulator
Change one — see what must give. The iron triangle never lies.
Every project is constrained by Scope, Time, and Cost — plus Quality running through the middle. Change any one and at least one other must flex. This is the most fundamental law of project management. Drag any slider to see the impact.
Feasibility score
Balanced
Quality risk
Low
Constraint pressure
Moderate
Real-world triple constraint scenarios
Sponsor says "deliver faster"
Time decreases → you must either reduce scope (MVP approach) or increase cost (add resources). Quality suffers if you do neither. The PM's job: make this tradeoff explicit and get the sponsor to choose.
Sponsor says "cut the budget"
Cost decreases → reduce scope or extend timeline. You cannot reduce cost, keep full scope, and hit the same deadline. Surface the options — don't absorb the cut silently.
Sponsor adds new requirements
Scope increases → extend timeline or increase cost. Any scope addition without a corresponding adjustment is scope creep and a quality risk. Always raise a change request.
"Do it all, fast, and cheap"
The classic impossible ask. All three constrained simultaneously = quality collapses. The PM's response: "We can do any two of these well. Which two matter most?" Force the prioritisation conversation.
▦
Methodologies compared
Click a card to see when to use it and how it works
📄
Key PM documents — decoded
What each doc is, who owns it, when it's needed
⚖️
Good vs bad PM communication
✓ Strong PM habits
Documents decisions and action items in writing after every meeting
Raises issues early — before they become crises
Gives status as: RAG + 1 sentence why + next action
Separates facts from assumptions in all reports
Confirms verbal agreements with a follow-up email
✕ Weak PM habits
Waits for weekly meetings to surface problems
Says "we're on track" without evidence
Lets action items go unassigned or untracked
Absorbs scope changes silently to avoid conflict
Sends 500-word status emails nobody reads
⚠️
Top 10 software PM mistakes
With root cause and what good looks like
0 / 8
correct
Running a project that is slipping? Book a 30-minute delivery review with Siva: we look at your plan, your numbers and the one thing to fix first.
Companion to Chapter 3 of The Discipline of Delivery by Siva Prasad. Read the chapter to understand why the discipline matters, then use this guide to practise the how.