Either you call it a process or not, or you may not be aware of one or not, there is a process always within an organization.
Foe example, if no process is defined, then the vicious cycle, code-test-debug-fix will prevail. Note that, fix == code, and test follows and it goes on.
The most important aspects of a process are visibility and predictability.
Visibility helps all stakeholders to figure out “what the heck is going on with the project?”.
Predictability helps all stakeholders to figure out “what the heck will happen to this project?”.
When visibility diminishes, predictability dies, and FUD creeps in.
The process will help bring in visibility into the project. If it does not, there is something wrong with the process. And better the visibility, we will enhance predictability.
When we say that we will ship the product at the end of next month, we are putting our predictability into test. And if we are not backing up that claim with current project status, then the chances of screwing up are much higher.
If we can predict when we can deliver, that indicates good transparency in the process, because we know what is going on with the project.
Tell others what you are doing, and what you are going to do. That will enhance project visibility a great deal.
When you have to predict when you can deliver, look at the big picture, including what you have done and going to do, as well as what others have done, and going to do. Promising deliverables based on guesstimates, nurtures mistrust over time. Using large buffer times also damage credibility.
Comments