Project Management Document Set for Security Projects

Template bundles sell forty spreadsheets. A security project needs about twelve documents, each with an owner and a reader. Here they are by phase — and how they look on a real ISO 27001 rollout.

5phases: initiate, plan, execute, control, close
12documents a security project needs
1log that does most of the work: RAID
0documents without an owner and a reader

Security projects fail in familiar ways: the scope grows from “deploy MFA” to “redesign identity”, the business owner never signs off risk acceptance, a dependency on the network team is discovered in week ten, and nobody can show the auditor when a decision was made. Project documents exist to prevent exactly those failures. The test for each one below is simple: who updates it, who reads it, and what decision does it support? A document with no answer is overhead.

1 · The Documents, Phase by Phase

PhaseDocumentMust containRead by
InitiateBusiness caseThe risk or obligation driving the project, options considered, cost, expected risk reductionSponsor, finance
Project charterObjective, scope and exclusions, sponsor, project manager, success criteria, budget, key datesSteering committee
PlanScope & work breakdownDeliverables broken into work packagesProject team
Schedule (Gantt or milestone plan)Milestones, dependencies, critical pathTeam, steering committee
RACI matrixWho is Responsible, Accountable, Consulted and Informed for each deliverableEveryone involved
Communication planWho hears what, how often, through which channelStakeholders
ExecuteTask trackerOwner, due date, status for each taskProject team
Test and acceptance recordsWhat was tested, results, who accepted itAuditors, operations
Monitor & controlRAID logRisks, Assumptions, Issues and Dependencies, each with an owner and a dateProject manager, steering committee
Change logRequested changes to scope, time or cost; impact; decision and approverSteering committee, auditors
Status reportProgress against milestones, red/amber/green, decisions neededSponsor, steering committee
CloseClosure reportObjectives met or not, open items handed to operations, residual risks accepted, lessons learnedSponsor, auditors, operations

▸ For security projects the change log and the closure report matter more than usual: auditors use them to see when a control went live, what was descoped, and who accepted the remaining risk.

2 · A RACI That Avoids the Usual Fights

Exactly one A per row. Example for an MFA rollout:

DeliverableCISOIAM leadIT service deskHRBusiness owners
MFA policyARCCI
Technical configurationIA/RC——
User enrolment and supportICA/RII
Exceptions approvalACI—R
Communications to staffCCRAI

3 · Worked Example: an ISO 27001 Rollout

DocumentWhat it says on this project
Business caseTwo large customers require certification at renewal; losing them outweighs the programme cost
CharterScope: product platform and supporting functions; certification audit in month 10; sponsor: COO
ScheduleGap assessment → risk assessment → Statement of Applicability → controls → internal audit → management review → stage 1 and stage 2 audits
RAID logRisk: HR cannot deliver background-check records in time. Dependency: logging platform upgrade by month 6. Assumption: current cloud provider’s attestation covers physical controls
Change logMonth 4: a newly acquired subsidiary added to scope; audit moved to month 11; approved by steering committee
Closure reportCertified; two minor nonconformities handed to the ISMS owner with dates; project lessons recorded

The documents the ISMS itself must keep after the project ends are a separate set: see ISMS Document Set.

4 · The Minimal Set for a Small Project

  1. One-page charter — objective, scope, owner, dates, success criteria.
  2. Milestone plan — ten lines, not a 400-row Gantt chart.
  3. RACI — one A per deliverable.
  4. RAID log — reviewed weekly.
  5. Change log — every scope, time or cost change with its approver.
  6. Closure note — what was delivered, what was handed over, which risks were accepted, by whom.

Bottom line

  • About twelve documents, not forty — each with an owner, a reader and a decision it supports.
  • The RAID log does most of the work during delivery.
  • One A per RACI row avoids the classic security-project stand-off.
  • Change log and closure report are what auditors read later.
  • Project documents end; ISMS records continue — hand them over explicitly.

Sources & method. Phase structure follows common project-management practice (initiation, planning, execution, monitoring and control, closure). Document lists reflect typical PMO template sets; the selection, RACI and worked example are the author’s analysis. Original analysis; no third-party graphics or text reproduced.

← Back to Cyber security