·         No vision? You may lose track of where you are going and may be easily distracted on detours.
·         No process? Without a common process, the team may have miscommunications and misunderstandings about who is going to do what – and when.
·         No plan? You will not be able to track progress.
·         No risk list? You may be focusing on the wrong issues now and may explode on an unsuspected mine 5 months from now.
·         No business case? You risk losing time and money on the project. It may be cancelled or go bankrupt.
·         No architecture? You may be unable to handle communication, synchronization, and data access issues as they arise; there may be problems with scaling and performance.
·         No product (prototype)? As soon as possible, get a product in front of the customer. Just accumulating paperwork doesn’t assure you or the customer that the product will be successful-and it maximizes risk of budget and schedule overruns and/or outright failure.
·         No evaluation? Don’t keep your head in the sand. It is important to face the truth. How close are you really to your deadline? To your goals in quality or budget? Are all issues adequately being tracked?
·         No change requests? How do you keep track of requests from your stakeholders? How do you prioritize them? And keep the lower priority ones from falling through the cracks?
·         No user support? What happens when a user has a question or can’t figure out how to use the product? How easy is it to get help?

Do you agree?

Advertisements