At the start of a project with the team is in place, it's time for everyone to roll up their sleeves and define the problem to be solved. This may strike some as an unnecessary step, even a waste of time. Let me assure you: it's essential. There's an adage, "a problem defined is half solved." I believe this is especially true in software development. In fact, an IBM study found that well-defined objectives were the number one factor in successful projects.

• A good project definition should include: 
• A project plan defining the vision, Critical Success Factors and areas of responsibility. 
• A requirements document defining when the project is complete. 
• A prototype, mockup or demo that provides a visual tool for clearing up misunderstandings. 
• A Gantt chart or Sprint Plan stating who, when, what and related interdependencies. 
• A risk plan defining what might go wrong and what to do if it does.

Tom's Takeaway: Beginning a project without a clear definition and plan is like building a house without a blueprint.