weekly planning

Weekly planning

Every week we plan ...

In the weekly TaskCycle planning we check:
  • Are we doing the right things, in the right order, to the right level of detail for now
  • Optimizing estimation, planning and tracking abilities to better predict the future
  • Select highest priority tasks, never do any lower priority tasks, never do undefined tasks
  • There are only about 26 plannable hours in a week (default1: ~2/3 of the gross available time)
  • In the remaining time: do whatever else you have to do
  • Tasks are always done, 100% done
The planning then goes like:
  • How much time do we have available
  • 2/3 of available time is net plannable time
  • What is most important to do
  • Estimate net effort needed to do these things
  • Which most important things fit the net available time (see figure)
  • What can, and are we going to do
  • What are we not going to do
  • Not producing waste !

"But we have to do ALL the things next week, not just what fits in the available time!"
You just determined what you can do and what you cannot do in the available time. So you now know that the other things will not be done anyway. The earlier you know that someting will not be done, the earlier you can do something about it, for example:

  • Telling your customer: the earlier he knows, the more he can adapt
  • Asking someone to help you because the FatalDay is really fatal
  • Doing things more efficiently, which is an option we should better use always even if there is no shortage of time!

Don't waste your time thinking you can do more than you can do.

Find a more detailed explanation in booklet "How quality is Assured by Evolutiopnary Methods", chapter 6.1.
(see Booklet#2 on the downloads page)

  1. 2/3 is a default start value. This value works well in development projects. Change only if you experience that you should use an other value.