Purpose. A written record of the kick-off that people can refer to when memory
and goodwill diverge. Circulate within two working days.
Meeting details
| Field | Detail |
|---|
| Project | |
| Date and time | |
| Location / platform | |
| Chair | |
| Attendees | |
| Apologies | |
Executive summary
Three to five sentences: what the project is, what was confirmed, and what the
immediate next steps are.
Objectives confirmed
| Objective | Success measure | Owner |
|---|
| | |
Scope confirmed
In scope
Out of scope
Assumptions
Approach
A short description of the delivery approach, referencing the standards applied and
the phase structure.
Roles and responsibilities
| Role | Name | Organisation | Responsibility |
|---|
| Sponsor | | Customer | Outcome ownership, escalation, budget |
| Technical owner | | Customer | Access, technical decisions, acceptance |
| Project manager | | Qbits | Plan, risk, change, reporting |
| Technical lead | | Qbits | Architecture, technical quality |
Governance and cadence
| Forum | Frequency | Attendees | Purpose |
|---|
| Delivery stand-up | | | Progress and blockers |
| Status report | | | RAG status, risks, decisions |
| Steering | | | Outcomes, escalations, budget |
| Milestone review | | | Deliverables and acceptance |
Decisions
Actions
| # | Action | Owner | Due | Status |
|---|
| 1 | | | | Open |
Risks and issues
| ID | Description | Impact | Owner | Status |
|---|
| R-01 | | | | Open |
Open questions
Next steps
Distribution: all attendees, the sponsor, and the project distribution list.
Store with the project records and link from the project charter.