The problem is that we do not document project assumptions and validate them. Instead, we keep on going with the broad leap of faith.
These 11 project assumptions are causing immense grief:
- The new enterprise software we choose will meet our current and future business needs
- There are enough resources to undertake Business As Usual (BAU) and project work
- We have competent resources to deliver the project
- The end-users will use the custom solution we are developing
- The project team will not resign or take unplanned leave
- The priorities of the software vendor will not change. The vendor will continue to provide the best possible service.
- We have covered all the requirements and not missing any critical feature
- The team will thoroughly test the solution before rolling it out to the production
- The project budgets are correct
- The project schedule/plan is logical and practical
- These will be minimal change management issues
We can keep on going with the assumptions list above. The point is that we assume the assumptions to be true. We seldom take the opportunity to document assumptions and validate them.
Therefore, don’t be disappointed when your assumptions are not met. Let your team to document and validate all assumptions to avoid grief later.
