Practical Software Requirements
Writing requirements as a product manager has always been a black art to me. It’s not impossible but it normally involves a lot of fudging and reading it always make me feel that there’s something missing. I often end up putting specifications inside the requirements document. How do I make it complete without ending up writing the specifications itself?
Kovitz’s Practical Software Requirements provides a clear and concise guide to writing requirements by looking at the problem of developing software. By examining how we frame a problem and its domains, the book explains how the reader can extract elements of the requirements and specifications documents and present them in a concise manner.
Throughout the book, he proposes how its content can be written and provides clear examples. His approach is direct and concise, and he teaches the reader how to write without any hint of legalese that permeate traditional corporate requirements documents. His examples are practical and he addresses common mistakes that writers make.
I’ve thoroughly enjoyed reading this book, and it has been an invaluable tool in helping me write better requirements and specifications at work.