Book Image

Managing Software Requirements the Agile Way

By : Fred Heath
Book Image

Managing Software Requirements the Agile Way

By: Fred Heath

Overview of this book

Difficulty in accurately capturing and managing requirements is the most common cause of software project failure. Learning how to analyze and model requirements and produce specifications that are connected to working code is the single most fundamental step that you can take toward project success. This book focuses on a delineated and structured methodology that will help you analyze requirements and write comprehensive, verifiable specifications. You'll start by learning about the different entities in the requirements domain and how to discover them based on customer input. You’ll then explore tried-and-tested methods such as impact mapping and behavior-driven development (BDD), along with new techniques such as D3 and feature-first development. This book takes you through the process of modeling customer requirements as impact maps and writing them as executable specifications. You’ll also understand how to organize and prioritize project tasks using Agile frameworks, such as Kanban and Scrum, and verify specifications against the delivered code. Finally, you'll see how to start implementing the requirements management methodology in a real-life scenario. By the end of this book, you'll be able to model and manage requirements to create executable specifications that will help you deliver successful software projects.
Table of Contents (12 chapters)

Summary

In this chapter, we introduced the requirements domain, explored requirements and specifications, and defined some of the main entities in the requirements domain, namely stakeholders and goals. We discussed the relationship between these entities and outlined this book's approach for bridging the gap between requirements and specifications. Being able to create valid and verifiable specifications that accurately reflect the requirements is crucial to our system's success. Understanding the requirements domain allows us to analyze and model our requirements, which is the first step towards creating a specification.

In the next chapter, we will finish our exploration of the requirements domain by talking about two more domain entities, capabilities, and features.