Kick-off meeting

Goal

The kick-off meeting is the session where the project sponsor states the mandate in front of the team and the people involved, where the roles are settled and where the way of working is agreed. HERMES places it among the activities of the task Manage and control project, in a wording that states two aims: "hold kick-off meeting with everyone involved and create a project culture". The PMBOK Guide lists project kickoffs among the meeting types (§5, entries "Meeting management" and "Meetings") and places meetings among the tools of §2.1.6.1 Initiate Project or Phase, the process that produces the project charter.

The session works on two planes. On the first it transfers information: why this project, on what budget, by what date, within what limits. On the second it builds a working group out of a list of names. Diana Larsen and Ainsley Nies describe that second plane under the name liftoff and give it three parts: the purpose and what will count as success, alignment on shared working rules, the context the team operates in, including its boundaries and the resources committed to it. Bruce Tuckman describes a team's development in four stages: forming, storming, norming, performing. The PMBOK Guide lists the sequence under the name Tuckman ladder, with a fifth stage in which the group disbands (adjourning). Forming happens with or without a kick-off, since everyone discovers the project and their own role in any case. The kick-off makes it explicit. It spares nobody the storming that follows.

Usage

When to use

• Project released and the team never assembled: the mandate is signed, the people named have not yet spoken to one another.
• Phase change with a fresh team: those who will execute are not those who initiated.
• Scattered project organisation: the business, internal IT and the supplier have no established contact.
• New sponsor or amended mandate: picking the work up after an interruption calls for restating what is expected.
• Programme split into projects: every project opens on the same ground rules.
• Diverging expectations between directorates: saying them in the same room costs less than discovering them at acceptance testing.
• Start of an iterative delivery: cadence, decision route and the scope of the first iteration to be settled before the first sprint.

When not to use

• Mandate not settled: the session will produce contradictory expectations; finish the business case first.
• Objective limited to one analysis deliverable: call a workshop framed on that deliverable.

Description

What each method calls it

The same moment goes by different names, and a Swiss reader will meet both vocabularies inside the same company. HERMES writes kick-off meeting in English and Kickoff-Sitzung in German. Agile literature uses liftoff, inception or jump start; Larsen and Nies keep the first and tie the practice to the team's own start, whatever word is used. PRINCE2 has no product and no process named kick-off: its vocabulary is Starting up a Project then Initiating a Project, which covers part of the same work in documentary form.

Deciding to hold the session

The decision rests on three conditions. The mandate has to exist in written and settled form: in HERMES, the project initiation order during the initiation phase, then the execution order. The sponsor has to be available in person, for the whole slot in which the mandate is stated; if they cannot come, the session moves. It has to be possible to draw up the invitation list, which takes an up-to-date stakeholder list and, on a politically exposed project, a stakeholder matrix saying who decides and who is informed.

Two sessions are often better than one. An internal session first, with the project team alone, where the working rules are discussed and the awkward questions get asked. A wider session next, with the sponsor, the users and the supplier, which no longer has to settle what the team has already sorted out among themselves. The split becomes compulsory once an external supplier is in the room: what the internal team needs to say about its own workings does not have to be said in front of them.

Who is in the room

Five functions have to be represented, and one person can cover two. The sponsor states the mandate, the budget and the deadline, then settles the decisions escalated to them. The project manager runs the session and owns the cadence afterwards. The business analyst or the user representative speaks for the need and afterwards receives the requests from the business. The delivery lead, internal or supplier-side, says what is feasible and at what price. The key users, two or three of them, bring the detail of the real work; their absence is the most frequent cause of a scope revised six months later.

Size decides the format. Up to a dozen people, the session can be collective work in which everyone speaks. Past twenty, it has to be split: a broad briefing session, then a small working session. Fitting both into the same slot produces a room where fifteen people watch five people work.

The order of the session

The order counts as much as the content. The mandate and the purpose come first, spoken by the sponsor, in a few minutes and without slides: why this project exists, what will count as success, what the organisation is giving up for the duration. A room that does not yet know why it is there reads everything that follows as procedure.

Then come the people and the roles. The classic round of introductions gives names and job titles; the question that makes the round useful is what each person expects from this project and what they fear. Then the way of working: meeting cadence, the route by which a decision is asked for and given, the escalation rule, the tools where the backlog and the documents live, the availability expected of each person. Larsen and Nies call this part alignment; it is the only point in the session where the room drafts the rule that binds it.

The working format sits at the heart of the session and takes up one slot only. A single format is run, chosen for one objective, which leaves time to take it through to a result. The close reads the action list out loud, assigns every line to a named person and sets the date of the next shared deadline. Half a day is enough for the whole thing; a full day is justified when the room brings together organisations that do not know one another.

Choosing the working format

The objective decides the format. Each of these formats is a technique in its own right, with its own conduct rules and its own success conditions; the kick-off borrows one and runs it inside its slot.

What has to exist when it ends

Three states are distinguished, and confusing them makes the list unreadable. Some items are confirmed: they existed before the session and the session stated them in front of witnesses, the budget or the deadline for instance. Others are produced in the room, such as the split of responsibilities or the working rules. Others stay open. A risk named without an answer is worth more than a risk left unsaid.

The minimum list runs to six lines. The mandate and the success criteria, stated and taken down in writing. A split of responsibilities, which a RACI matrix writes on one page. The shared working rules, which the PMBOK Guide ties to the project team charter. The meeting cadence and the reporting rules, which HERMES requires to be recorded in the project management plan. The risks known at that date, which feed risk analysis and management. An action list, every line carrying a name and a date. The record goes out within twenty-four hours, failing which it becomes minutes nobody reads again.

Pitfalls

The briefing in disguise

Forty slides, an hour of presentation, five minutes of questions. The room leaves informed and nothing has been decided or produced. The symptom shows in the preparation: if that consisted of building a deck, the session will be a talk. The test is one question: what will the session produce that is not already in the deck?

The mandate from the wrong role

The project manager reads the mandate because the sponsor is held up elsewhere. The content gets across, the commitment does not. The first request for a ruling will reach, three months later, someone who promised nothing in front of witnesses. Moving the session costs a few calendar weeks; a ruling nobody promised in public costs more than that.

The working format that overruns

The team spends two hours on games and exercises, then leaves the room delighted. Nobody can say what the budget is or who settles a scope decision. The working format serves an objective written into the agenda, and its place in the session is bounded. The warning sign is a format chosen for its own sake before the objective is written down.

The action list with no owner

"The interface with the fare system needs clarifying" is an intention. An action line carries a verb, a person's name and a date, failing which it is taken up unchanged at the next session. The close is done standing, out loud, line by line.

The session held after work has started

A kick-off held once development is under way ratifies decisions already taken. It opens a discussion that the room believes to be open and that the calendar has already closed, which costs more than holding nothing at all. The session sits after the phase is released and before the first work is committed.

AI considerations

Preparation is where the help is clearest. From the business case and the mandate, a language model produces a one-page summary in the vocabulary of the business, which the sponsor corrects in ten minutes instead of writing it. From the stakeholder register, it proposes an invitation list with the reason for each attendance, which makes the omissions visible: the function that will operate the solution rarely appears in lists built from memory. It also produces candidate working rules, which the room amends rather than invents in front of a blank board.

During and after the session, automatic transcription and action extraction make the close faster and the record more complete, on two conditions. Recording a session requires the participants' consent and a retention regime, a constraint the workshop treats in detail. And an extracted action still has to be assigned: the machine gives back what was said, the room decides who does it.

Three limits hold. The product of the session is a group of people who have met one another, and nothing a machine generates replaces that. The mandate has to be spoken by the sponsor in their own words: a text produced by a tool and read out loud transfers the information without committing the person reading it. And deciding who stays outside the room is a political judgement that nothing in the documents fed to the model supports.

Examples

Transports du Léman is opening the replacement of its ticketing system. The room brings together nine people: the head of operations, who carries the mandate; the project manager; a business analyst; the head of IT and the architect from the selected supplier; the head of customer service; two sales agents and a ticket inspector. Half a day, a single working slot, a RACI matrix built jointly.

The success criteria come into the session as a hypothesis: the written mandate speaks of modernising ticket sales. Asked what will count as success, the head of operations quotes three numbers he has from his executive board: the share of online sales, the time taken to check a ticket on board, the maximum length of a sales outage. The two sales agents contest the second, measured on hardware they do not have. The room settles on eight seconds after a trial on the existing terminal. The line goes into the produced state for that reason: the number did not exist before the session and it now carries the agreement of those who will have to meet it.

The State column makes the document useful a month later. It says which lines have committed the sponsor since before the session, which lines have committed the room since the session and which lines commit nobody yet. The open line on the fare interface shows it: the interface specification due from the regional network on 12 September arrived in November, incomplete. Because the line had been in the open state from the first day, the October steering committee had already put it on its agenda and the project manager had had a manual fare migration costed. The system went live two months late, with no emergency ruling and no budget overrun. The same risk filed among the confirmed lines would have been read again only at the moment it was missing.

Visualisations

Three things call for an image. The session has three stages that do not overlap: deciding to hold it and preparing it, running it, listing what has to exist at the end. A figure puts them in sequence and attaches its conditions and its products to each stage; a prose enumeration gives the same items without their order. The choice of working format is a mapping between an objective and a means, so a three-column table. The third is the record itself: a table whose state column sorts the lines into confirmed, produced, open.

Cost

Tooling

The shared calendar decides the session. The sponsor's slot is booked six to eight weeks ahead, and that booking is the first action of the project.

The meeting pack fits on one page or two: the mandate, the success criteria, the agenda with an expected result per item.

The collaborative whiteboard (Miro, Mural, Excalidraw or a wall and A4 sheets) hosts the working slot. It survives a remote session and leaves a trace that can be photographed, which feeds the record without re-keying.

The project tracking tool (Jira, Azure DevOps, Planner, a shared list) receives the actions the same day. An action that stays in the minutes is not taken up again; the same action opened in the tool where the team already works comes back on its own at the next checkpoint.

The document space (SharePoint, Confluence, a shared folder) is given out in the room as a single link, with the rights already granted to the participants. Distributing access afterwards costs several days.

Video conferencing makes a distributed session workable provided its form changes, which the workshop sets out. What belongs to the kick-off is the camera switched on during the part where people introduce themselves: the product of the session is that they have seen one another.

Sources

• Swiss Confederation, Federal Chancellery, HERMES 2022, Project Management Reference Manual, task 5.4.3.33 Manage and control project: the activity "hold kick-off meeting with everyone involved and create a project culture", the preconditions (project initiation order, project management plan, execution order) and the attachment of the reporting rules to the project management plan.
• A Guide to the Project Management Body of Knowledge (PMBOK Guide), 8th edition, Project Management Institute: §2.1.6.1 Initiate Project or Phase, which places meetings and the responsibility assignment matrix among the tools for starting a project or a phase; §5 Tools and Techniques, entries "Meeting management" and "Meetings", which list project kickoffs among the meeting types and fix the generic discipline (agenda, participants, action record with an owner). The entry "Tuckman ladder" gives the team development stages.
• Diana Larsen and Ainsley Nies, Liftoff: Start and Sustain Successful Agile Teams, 2nd ed., Pragmatic Bookshelf, 2016: the kick-off as the start of a team, the three parts of the charter (purpose, alignment, context) and the competing names of the practice.
• Bruce W. Tuckman, "Developmental Sequence in Small Groups", Psychological Bulletin, vol. 63, no. 6, 1965, pp. 384-399: the developmental sequence of small groups, source of the model PMI lists under the name Tuckman ladder.