Software projects in small companies differ greatly from those in huge corporations. Often, time to market is such a critical need that small companies cannot spend months gathering requirements and piling up mounds of documentation.
What they want is proof – proof that you understand their business and have a clear grasp on what is to be built. The developers want the same thing – enough detail to get it right, but not a mind-numbing stack of paper that removes all creativity as well as a small forest.
Here are the questions that must be answered in a minimum blueprint:
- Why do you need a solution?
- Who are you creating it for?
- What will it do for them?
- How will they use it?
- What makes it smart?
- How does it all fit together?
Review a sample software blueprint and see how it compares to home construction:
