Your SlideShare is downloading. ×
6. Requirements Management, Macadamian - Sona Sahakyan
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

6. Requirements Management, Macadamian - Sona Sahakyan

156
views

Published on

Published in: Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
156
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 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