The recent post about What Does a Good Schedule Look Like? brought out a response on What Does A Good Plan Look Like?
This brings up the issue of planning and scheduling inside of projects, especially projects where planning and scheduling is not the normal paradigm - Agile projects. Of course this not not really the case, because Scrum has planning and scheduling as part of the process. Plans are plans, and the schedule is the list of deliverables in the current iteration.
But one reminder for all those who have convinced themselves that scheduling and planning are not really needed and that emergent development and measures of velocity are the replacements.
The definition of velocity is the measurement of the rate and direction of motion. Velocity is a vector.
What is the purpose of a velocity, if you do not know the distance to the end?
- Are you going fact enough?
- Are you going too fast?
- Are you going in the right direction?
- Is the direction you are going the least energy path?
