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

Planning the way forward

The second meeting with the stakeholders is arguably more important than the first. This is where, after having done our initial analysis, we present our requirements model and seek stakeholders' feedback and approval. This is also the meeting that kick-starts system development. We should now have enough features to have created a small, but perfectly-formed, system backlog (a list of all the features on our requirements model). Our objectives for the second meeting are as follows:

  1. Explain the requirements model and get it approved by the stakeholders.
  2. Present a first draft of our specification document, as detailed in Chapter 6, Organizing Requirements, in the Creating a specification document section.
  3. Identify and discuss any areas of concern or ambiguity, if any.
  4. Present and discuss potential risks, if any.
  5. Identify a point of contact from our client-side stakeholders. We need one person to represent our client-side stakeholders...
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