Search icon CANCEL
Subscription
0
Cart icon
Cart
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
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

Product type Book
Published in Aug 2020
Publisher Packt
ISBN-13 9781800206465
Pages 214 pages
Edition 1st Edition
Languages
Concepts
Author (1):
Fred Heath Fred Heath
Profile icon Fred Heath
Toc

Table of Contents (12) Chapters close

Preface 1. Chapter 1: The Requirements Domain 2. Chapter 2: Impact Mapping and Behavior-Driven Development 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

Creating a product backlog

A product backlog is simply a list of all the Features that we, the system builders, need to implement in order to successfully deliver the system. In order to understand the role and significance of the backlog, we need to understand how the Software Development Life Cycle (SDLC) works.

The Agile SDLC

The SDLC consists of three major phases, as depicted in the following diagram:

Fig. 6.2 – SDLC

Fig. 6.2 – SDLC

These phases are as follows:

  • Requirements gathering and analysis
  • Development
  • Integration and verification

In Agile development, these three phases are not singular. They are repeated in continuous iterations, each iteration focusing on specific functionality or goals. Neither are they sequential; they can and do occur in parallel. Within the same iteration, a team member may be doing requirements gathering, while a second one writes code for a feature and a third team member verifies a different feature...

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 $15.99/month. Cancel anytime