This document discusses Agile requirements management. It provides an overview of key Agile concepts like the product backlog, backlog items, acceptance criteria, and how requirements work in Scrum. The product backlog is an ordered list of everything needed in the product and is the single source of requirements. Acceptance criteria define when a user story is complete. Requirements in Agile are dynamic, visible to all, and the single source of truth. The document also discusses managing the backlog over time through progressive refinement and decomposition.

1. Confidential 10/7/2013 1
AGILE TOUR YEREVAN
05, October, 2013
Agile Requirements Management
Sona Sahakyan
QA Engineer, PSM

2. Agenda
 Introduction
 Product Backlog
 Backlog Items
 Acceptance criteria
 How Requirements Work in Scrum
 Agile RDM
 Decomposition
 Summary
2

3. Introduction
 Myth about Agile
 Agile Manifesto
 Working software over comprehensive documentation
 Value question
 Lean thinking
 RDM(Agile requirements definition and management)
3

4. 4

5. Product Backlog
“The product backlog is an ordered list of everything that
might be needed in the product and is the single source of
requirements for any changes to be made to the product.
5

6. Backlog Items
6
Feature
Epic
User Story
Task
a distinct element of functionality which can provide capabilities to the business
big User Story
new functionality
both development and testing tasks
work to address a defect

7. Acceptance Criteria
7
“ Acceptance criteria define the parameters of a User Story and
determine when a story is completed and working as expected.

8. Benefits of acceptance criteria
 Focusing the team on how a feature will work from the
customer’s perspective
 Removing ambiguity from the requirements
 Forming the tests that will confirm that the feature is
working and complete
 Limiting the developers to adding only the functionality
that the US requires
Confidential 10/7/2013 8

9. Backlog Specifications
 Visible to everyone
 Single source of the truth
 Dynamic
9

10. How it works in Scrum
10

11. Agile RDM steps
11

12. Managing Backlog
 How does it change over time?
 Progressive Refinement
 How much detail?
12

13. Attributes of a good product backlog
 Detailed Appropriately
 Estimated
 Emergent
 Prioritized
13

14. Decomposition
14

15. Summary
 Agile or not do not skip RDM
 Good backlog as a way to build a software that matters
 Acceptance criteria and its’ benefits
 Ways of managing backlog and requirements
15

16. 16