history Last updated

Templates for the paperwork that keeps a project defensible: what was agreed, what changed, who decided, and what is currently at risk. Each one is short on purpose — a charter nobody reads is worth less than a one-page charter everybody signed.

  • Requirements & Analysis — where the scope a charter fixes becomes statements someone can build and test against.
  • Testing & QA — the acceptance gates a plan’s milestones usually depend on.

Linked from

  • Meeting Minutes — Decisions and actions, captured in a form that survives the disagreement three months later.
  • Overview — Copy-paste document templates for IT work, each with a worked example and the mistakes that usually spoil it.
  • Project Charter — The one-page authorisation that says a project exists, who runs it, and what 'done' means.
  • Project Plan — Schedule, dependencies, resourcing and the critical path, in a form a delivery team will actually maintain.
  • RAID Log — One table for Risks, Assumptions, Issues and Dependencies — the project's short-term memory.
  • Requirements & Analysis — BRDs, SRSs, user stories, use cases and traceability matrices.
  • Status Report — A weekly one-pager that reports the delta, the decisions needed, and the truth about the date.