Today, let’s talk about the role of the project Kick Off meeting ( KO for short ). Some people think it is very formal, but I think it is very important. In fact, KO only takes about 15 minutes . I will arrange it in the demand review (the participants basically overlap with the KO ). ), the cost is low.
In this 15min , the information that needs to be conveyed is as follows.
Ø Project background and significance
Speaking of the past, the situation before doing the project, why do this project (with the ultimate goal of making the audience heartache).
Ø Project goals and objectives
Speaking of the future, the situation after the project is completed, and the project is a success if the problem is solved (with the ultimate goal of making the audience look peach).
Ø Overview of practices, requirements, and function points
Talk about the present, and what specific method is used to promote the transition from "past" to "future" (with the ultimate goal of making the audience eager to try).
ØProject organization structure
The purpose is to let the present and relevant personnel understand who to call for any matters, and be careful not to omit members who have little to do with development (most activities in small projects are development and related processes): service departments, interface people for cooperating departments, Because if they don't know about the project, even if the project itself is released smoothly, it will bring a lot of coordination problems later.
In particular, I will organize a "Project Steering Committee", which is necessary, and their task is very simple - take the blame (with greater power, greater responsibility). When the project has major changes due to various reasons, such as cost, construction period, requirements, etc., I will apply to them, and only move after approval. This is also the protection of the PM himself and the project members.
ØProject plan
Let everyone understand two key points: 1. Time points and milestones, 2. The resources needed at each time period.
I won't say much about this. It's too esoteric to understand. According to the boss's words, it is actually very simple to do a good project. One is to plan well, and the other is to control it well. All means serve these two points.
ØCommunication plan
I think it is very important to clarify this point with all the members of the project, because too many things are not smooth because of communication problems, and everyone cannot communicate actively and thoroughly all the time, so there is a rule to force some communication work, Can save a lot of trouble. Generally speaking, the common means are: project daily, daily morning meeting, review meeting, product trial meeting, release notice / announcement...