I am like this guy on the Discover Card commercials that hates surprises.
At the end (or near the end) of every project, I hate it when we discover a serious miscommunication. And, it happens almost every time that we try to “fast track” a project. Inevitably, we uncover something that was missed or overlooked.
It happened again this week. When prototyping a new project (automating a process that is paper driven), we discovered that our foundational assumptions were wrong. The requirements that we thought were “fixed” are actually supposed to be “fluid” and determined by the user.
Ouch. Back to the drawing board. We are re-writing the entire application.
That is why every project needs contingency. We need contingency in the budget and in the schedule in anticipation for changing requirements.
Why? Because there is ALWAYS miscommunication. We are human. We are finite. We make mistakes. We are not capable of understanding everything about the project in one big launch conversation.
The more contingency in a project, the better you can be prepared for those surprises.
Thanks for listening.