"Schedule chicken" is most likely to happen in project progress meetings that report progress one by one. The project manager will ask you about the progress. Everyone says they are on schedule. But in reality, no one does. Everyone is waiting for others to blink and admit that they are not keeping up with the progress. And unless it's too late, no one will admit that they missed the project schedule.
Schedule chicks
A practical project manager has the following options.
- Avoid one-by-one progress report meetings (see section 10.1.2 ). The method in section 10.5 can be used to determine the real progress of the project.
- Divides tasks into smaller parts, so that each person can deliver a small task every day, up to two tasks. (For details, see section 5.8)
- One by one by function. If more people can focus on a small deliverable feature, they can complete it as soon as possible, and people can easily see how much progress they have made. In some cases, people play the "schedule chicken" game because it starts late (see the tip in section 8.10 ). Regularly see the integration of various parts of the product so that everyone can see the progress of the project and help them know when no progress has been made.
- Consider using iterations, especially agile lifecycles. With short-term iterations, you don't have to sit down and hold weekly group project progress meetings (and this meeting should never be held ). With daily meetings, people cannot hide their real progress.
The first time I talked about "calendar chicks" was with Dave Smith and Jerry weberger ).