TL;DR
The last time we presented the scheduled game, We Can’t Say No. Today we present the 13th schedule game, Schedule Chicken. The post is based on a remarkable book written by Johanna Rothman, Manage It!
Schedule Chicken Game Pattern
This game is usually played in the serial project life cycle. The project manager asks each team member about their task status, and we all say that our tasks or on schedule track. The truth is that we are not on schedule track. Each team member waits for other team members to tell the project schedule truth, and we have a deadlock.
How To Play
As a project manager, you could do the following.
Avoid serial status public meetings to get the project status.
Each project task should be broken into pebble tasks. Pebble task duration is one or two days. You will find out that the task is not on schedule track after just two days.
Implement by feature. By knowing how to observe the application feature, it is easier to create pebble tasks.
Use short iterations, one or two weeks. Doing that, you would get real project feedback status after iteration duraiton.
Comments are closed.