Managing Software Requirements the Agile Way: Bridge the gap between software requirements and executable specifications to deliver successful projects

Managing Software Requirements the Agile Way: Bridge the gap between software requirements and executable specifications to deliver successful projects

English | 2020 | ISBN: 978-1800206465 | 214 Pages | PDF, EPUB | 26 MB


Learn how to deliver software that meets your clients’ needs with the help of a structured, end-to-end methodology for managing software requirements and building suitable systems
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.
What you will learn

  • Kick-start the requirements-gathering and analysis process in your first meeting with the client
  • Accurately define system behavior as features
  • Model and describe requirement entities using Impact Mapping and BDD
  • Create a feature-based product backlog and use it to drive software development
  • Write verification code to turn features into executable specifications
  • Deliver the right software and respond to change using either Scrum or Kanban
  • Choose appropriate software tools to provide transparency and traceability to your clients