Blueprinting for software products

I always liked manual engineering drawing tools. As a kid, I assumed all engineers are supposed to carry a drafter and charts. But I never got around to using a drawing board after the 1st year of my engineering. With CAD tools, there came a better way to create the designs. But the idea of blueprint for building something remained, Blueprint for mechanical or civil structures communicate the design and details better.

Advantages of creating a blueprint:

1. Gives more details for developing.
2. Makes it easy to understand the capabilities and limitations of the product that is being built

Unfortunately, the software industry has somehow failed to adapt to this engineering practice. A lot of startups start the product development with code rather than a blueprint. It is appalling to see how many such startups get lost after some iterations. Imagine trying to construct a bridge without a blueprint.

When I'm talking about the blueprint for a software product, I am talking about a culmination of following documents.

1. Product specs —Usually created by product managers/owners based on business and strategic requirements for the business.
2. UI/UX — Aesthetics and usability of the product which reflects the brand identity
3. Technical implementation document — System architecture and Implementation details to build the product with given specifications.
4. Development plan — Task breakup, work estimation and resource allocation plan

In my experience working with startups and companies, one counter-argument I hear the most is

“We are following agile methodology now, we want to adapt very quickly”.

I want to make it clear to all such people. Being agile doesn’t mean not having a plan up front. Jumping into developing a product without a plan is just like trying to build a car without a blueprint. Agile methodology actually means adjusting the initial thought out plan to changing circumstances.

It may take longer to start the process or the documentation process may be boring but the detailed planning is what brings clarity to product development.

So, next time you are starting with a new software project, start with a drawing board.