Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Managing Software Requirements the Agile Way

You're reading from   Managing Software Requirements the Agile Way Bridge the gap between software requirements and executable specifications to deliver successful projects

Arrow left icon
Product type Paperback
Published in Aug 2020
Publisher Packt
ISBN-13 9781800206465
Length 214 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Fred Heath Fred Heath
Author Profile Icon Fred Heath
Fred Heath
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Chapter 1: The Requirements Domain 2. Chapter 2: Impact Mapping and Behavior-Driven Development FREE CHAPTER 3. Chapter 3: Writing Fantastic Features with the Gherkin Language 4. Chapter 4: Crafting Features Using Principles and Patterns 5. Chapter 5: Discovering and Analyzing Requirements 6. Chapter 6: Organizing Requirements 7. Chapter 7: Feature-First Development 8. Chapter 8: Creating Automated Verification Code 9. Chapter 9: The Requirements Life Cycle 10. Chapter 10: Use Case: The Camford University Paper Publishing System 11. Other Books You May Enjoy

Applying the Agile requirements management workflow

Throughout this book, we've learned about different techniques, processes, and methods for dealing with various stages of the analysis and development life cycle. We can now put them all together in an integrated workflow that will start by capturing raw requirements from the stakeholders and end by delivering working code that verifiably delivers what our stakeholders require.

Our workflow consists of four distinct phases:

  1. Elicitation and Analysis
  2. Discovery and Modeling
  3. Executable Specification
  4. Development and Verification

These phases will be repeated time and time again throughout our project's life cycle, for each set of requirements that comes to our attention and through each development cycle or iteration (sprint). They will also be applied concurrently, where some of our team members will be eliciting requirements from the stakeholders, while some other team members will be creating...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at €18.99/month. Cancel anytime