Building the product right and building the right product are two different things

Thanks to Gojko Adzic for his book Specification by Example for these few tips I am going to list down here on  software design.

These points felt so useful for those who want to design and develop software users will appreciate and love. So I though I could share them.

Go ahead now and read...Go on...

To build the right product effectively, software development practices have to provide the following:

• Assurance that all stakeholders and delivery team members understand what needs to be delivered in the same way.
• Precise specifications so delivery teams avoid wasteful rework caused by ambiguities and functional gaps.

• An objective means to measure when a piece of work is complete.
• Documentation to facilitate change, in terms of both software features and team structure.

Today, in the world of weekly software deliveries,
this doesn’t work. We need a solution that gives us a way to

• Avoid wasteful over-specifying; avoid spending time on details that will change before a piece of work is developed.

• Have reliable documentation that explains what the system does so we can change it easily.

• Efficiently check that a system does what the specifications say.

• Keep documentation relevant and reliable with minimal maintenance costs.

• Fit all this into short iterations and flow-based processes, so that the information on upcoming work is produced just-in-time.

Thank you!