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)

Chapter 10: Use Case: The Camford University Paper Publishing System

In previous chapters of this book, we learned how to manage requirements in order to provide a successful software delivery. In this, the final chapter, we will examine how our knowledge can be applied to a real-life use case. Camford University is obviously not real, but the nature of the requirements, interactions, and events described herein are all based on actual cases that I've encountered in my career in the course of various projects. In particular, we will learn about the following:

  • Understanding the Camford conundrum
  • Eliciting requirements
  • Analyzing requirements
  • Planning the way forward

This chapter intends to give some context to all the knowledge imparted in this book. You will get a taste of how to apply all the requirement elicitation and specification methods you've learned in this book to a new project. You will also learn how to conduct two important project milestones...