Beautiful Teams

Schedules

We had a meeting the following day, just to start develop the rolling wave schedule. I posted the months on stickies across the top of the wall, along with the known major milestones, such as internal demo, initial customer demo, and customer release, under their correct months. I listed the features down the side on a piece of flip-chart paper, in the order the developers told me they were going to implement them.

I asked, "What will it take us to get to these first two features?"

Dan replied, "No, JR, we're working in parallel. That's the wrong question. The real question is who will do what when?"

"OK, as long as we don't plan the whole darn project at once. The idea of doing this on stickies is to make sure we can figure out a Plan B if this plan doesn't work. Remember, when you write your tasks on stickies, make the tasks as small as possible."

Everyone wrote his tasks on stickies. Most of the tasks were one or two weeks long.

"OK, guys, I'm in trouble now."

"Why?"

"Because I am not going to know for too long if anyone is in trouble. Neither will you. You have to make smaller tasks. I bet each of you does something every day, right?"

Heads nodded.

"OK, then write all those things down, just for this first week. If you know enough about the second week, add that, too."

After they'd revised their first two weeks of stickies, I explained, "OK, I'm not going to ask you every day what you're doing. You're going to tell me if you don't make the progress you think you're going to ...