Kick-off agenda

Purpose. Align the full project team on scope, objectives, roles, cadence and access — and record that alignment.

Meeting details

Field	Detail
Project
Date and time
Location / platform
Chair
Minutes taken by

Attendees

Name	Role	Organisation	Present
	Project sponsor	Customer
	Technical owner	Customer
	Project manager	Qbits
	Technical lead	Qbits
	Delivery engineers	Qbits

Agenda

Time	Item	Lead	Output
10 min	Welcome and introductions	PM	Shared understanding of who is involved
15 min	Business context and objectives	Sponsor	Confirmed objectives
20 min	Scope — in and out	PM	Confirmed scope boundaries
15 min	Architecture and approach	Technical lead	Shared understanding of the target
10 min	Roles and RACI	PM	Agreed responsibilities
10 min	Cadence, reporting and escalation	PM	Agreed meeting rhythm
15 min	Access, tooling and prerequisites	Technical lead	Access request list
10 min	Risks and assumptions	PM	Initial risk list
10 min	Next steps and actions	PM	Assigned actions

Discussion prompts

Business context

• What does success look like in twelve months?
• What happens if this project does not happen?
• Is there a date or event this must be ready for?

Scope

• What is explicitly included?
• What is explicitly excluded?
• What has been assumed that has not been confirmed?

Roles

• Who can approve a scope change?
• Who accepts deliverables?
• Who is the escalation point when a decision is stuck?
• Who on the customer side can grant access?

Access and prerequisites

• AWS account access and the role we will assume.
• Repository access.
• Documentation the customer will provide.
• Named customer staff and their availability.

Decisions made

#	Decision	Owner	Date
1

Actions

#	Action	Owner	Due
1	Issue access requests	Qbits PM
2	Provide existing architecture documentation	Customer
3	Confirm workshop dates	Qbits PM

Risks identified

Risk	Impact	Owner

Next meeting

Field	Detail
Date
Focus

---

Circulate the post-kick-off summary within two working days.