Project Management Templates

A project management framework uses a defined set of documents to establish, plan, track, and close projects: the project charter (the formal document that authorises the project, defines its objectives, scope, constraints, and stakeholders, and names the project manager), the project plan (the schedule of activities, milestones, dependencies, resources, and budget), the RAID log (Risks, Assumptions, Issues, and Dependencies — the living document tracking everything that could affect project delivery), the stakeholder register (a record of all stakeholders, their interest and influence, and the engagement approach for each), the change register (a log of all changes to scope, schedule, or budget — recording who requested, who approved, and the impact assessment), and the project close report (a structured retrospective documenting outcomes versus objectives, budget performance, schedule performance, lessons learned, and outstanding actions). The minimum effective set depends on project size and complexity — a large capital project requires all of these; a small internal initiative may use a simplified subset.

A structured sprint planning process covers four phases: backlog refinement (the product backlog is reviewed and the highest-priority items are in a ready state — sufficiently detailed, estimated, and small enough to complete within a sprint), sprint goal definition (a clear, measurable objective for the sprint that gives the team a shared focus beyond the individual stories), capacity planning (available team capacity calculated based on the sprint duration minus planned leave, meetings, and other commitments — preventing the sprint from being over-committed by default), and story selection and commitment (the team selects the user stories that fit within capacity and meet the Definition of Ready, discusses them sufficiently to break them into tasks, and commits to the sprint goal and the selected scope). Sprint planning that is skipped or rushed produces sprints that are either over-committed (and end with carry-over) or under-committed (and waste capacity).

A capital project is a significant investment in a physical asset — construction, major refurbishment, infrastructure installation, or large-scale equipment procurement — that appears on the organisation's balance sheet as a capital expenditure. Capital project management differs from standard project management in several ways: the approval process is more formal (capital expenditure typically requires board or investment committee approval with a business case), the procurement process is more regulated (competitive tendering, contractor qualification, and formal contracts are standard), the delivery involves physical construction or installation with specific health and safety, quality, and commissioning requirements, the handover to operations is a formal process (the asset is transferred to the operational team with documentation, warranties, and maintenance manuals), and the financial close involves capitalising the expenditure on the balance sheet at the correct value. A capital project checklist must address all of these phases, not just the construction or installation activities.

Every CheckFlow template is fully customisable for any project methodology. For Agile/Scrum: the sprint planning and sprint review templates provide the ceremony structure; the project documentation templates are adapted to the lighter-touch artefacts appropriate for Agile (product vision, user story map, and sprint backlog rather than Gantt chart and detailed project plan). For Waterfall: the project documentation templates cover the full set of traditional project artefacts; milestone gates are defined as phase completion checkpoints with formal sign-offs. For hybrid: different phases of the project can use different methodologies — discovery using Agile sprints, delivery using a more structured waterfall approach — with the checklist templates adapted to each phase's requirements. The capital project and IT project templates provide starting points that can be adjusted to the governance requirements of the specific organisation and project type.