Concise requirements give your team a useful, easy to read and easy to change understanding of what must be done. Great requirements exist to do three things:
What is the right level of detail for writing requirements? What about for writing specifications (functional, non-functional requirements, etc)? The answer is that there is no one answer. But there are guidelines, and reasons to write more detail, or less detail – for any given product or project, and any given team. The reason we write requirements is so that they can be read. Understanding the readers is the key to determining which details to include in the requirements.
These articles are written primarily for business analysts and product managers. Hopefully they are helping you with thinking, doing, and learning. Welcome aboard!
Latest Articles
Comments on all Articles