6.4Toolbox
The essentials in 30 seconds
- Secure: a short checklist (need, SMART, scope, stakeholders, charter, governance, approach, risks) avoids most blind starts.
- Draw: ready landmarks (golden triangle, WBS then Gantt, effort ≠ duration, critical path, remaining work, change, agile, closure) for decision moments.
- Rule: one checklist ticked every time beats a long ignored method — adapt to your context and approach.
Bilal thread — 1 year on: landmarks at hand
One year on, both checklists below are posted at Bilal's place: the pre-launch one on his wall, the landmarks-to-draw one near his Gantt. “What saved me, he says in substance, is not knowing the landmarks, it is ticking them every time — especially on rush days.”
Adapt wordings to your context (predictive or agile), keep the structure: it is what avoids omissions and overruns.
Ready-to-use landmarks
A good checklist makes a task fast and forget-free; good landmarks speed decisions. Adapt to your context and approach (predictive or agile).
Before launching a project
- Is the need clarified (scoping note)?
- Are objectives SMART?
- Is scope written (included / excluded / assumptions)?
- Are stakeholders analyzed (power/interest)?
- Is the charter signed by the sponsor?
- Is governance defined (steering / project committee)?
- Is the approach (predictive / agile / hybrid) chosen by need?
- Is a risk register started?
Landmarks & reflexes at hand
- Golden triangle: cost / schedule / quality — arbitrate, don't maximize everything
- WBS first (the WHAT), Gantt next (the WHEN)
- Effort ≠ duration (calendar time); target ~80% load
- Critical path = zero-float tasks → priority vigilance
- Steer by REMAINING WORK; SPI<1 = behind, CPI<1 = overrun
- Change: formalize → impact → decide → trace
- Agile: prioritized backlog, increment per sprint, limit WIP
- Closure: acceptance + delivery + archiving + review (blameless)
Ready-to-say script — pick your landmark in 30 seconds (30 s)
“Starting: I check need, SMART, written scope, signed charter. Planning: WBS then Gantt, critical path identified. Steering: remaining work and risks. I picked, I tick, I decide.”
Copy-paste template — pre-launch tracking (1 line per item)
PROJECT: ...
Need clarified (scoping note) on ...: OK / to redo
SMART OBJECTIVES on ...: OK / to rephrase
SCOPE (included / excluded / assumptions) written on ...: OK / to write
STAKEHOLDERS (power / interest) on ...: OK / to analyze
CHARTER signed by the sponsor on ...: OK / to have signed
GOVERNANCE (steering / project committee) on ...: OK / to define
APPROACH (predictive / agile / hybrid) on ...: ...
RISKS started on ...: OK / to startSmall business / tight budget
Checklists on one page posted on the wall: the essentials (need, scope, risks, review) are enough.
Algeria SME
Plan real lead times and availability into the checklist: what to verify, with whom, with what margin before committing.
Remote / hybrid
Add a written-validation line to tracking: at a distance, scope shared in writing avoids misunderstandings.
Cross-cultural
State governance and roles in writing: what seems obvious is not obvious to everyone.
48h challenge — apply tomorrow
Take 1 ongoing project, run the checklist above and tick where it stands. Fix the missing line before moving on.
- I have ticked the checklist on a real project.
- I can draw a landmark (critical path, remaining work, WIP, review) at the right moment.
- I did the 48h challenge or scheduled its date.
Before launching his project, what should Bilal verify first per the checklist?
Tip: keep these landmarks near your templates (scoping note, charter, risk register, dashboard); adapt them to the project's predictive or agile approach.