Requirements Traceability Introduction

A high level introduction into agile requirements traceability, this first webcast demonstrates an example of agile requirements traceability and sets the stage for future technical webcasts that will take the user stories described to a deeper level of technical detail. We discuss an example user story and show how detailed requirements captured as test tables can be used to build executable specifications and aid the design process. Finally we wrap up by a brief example of how we would track the progress of multiple user stories across our scrum or kanban wall.

Category:

Science & Technology

Tags:

• Agile
• Requirements
• Test
• Lean
• Scrum
• Fit
• Test Tables
• Testing

[bluedna]

Thanks for posting, that very well described. Definitely left me wanting more. A few things that probably should have been mentioned were Epics and Product Backlog (in lieu of project management). Other than that, very informative video. Will you be posting more?

[mirwais69]

at the end of the day, don't confuse the people with so many ways to cut an apple.. cut the apple with the best way and the best way is already been done and exists.. learn it... don't invent confusion..build solutions.

[mirwais69]

Why is it referred to as a problem statement. Please.. Gee wiz, it is a NEED STATEMENT - The customer needs a service .. DOES not have a PROBLEM.. ok..now, User stories are the scenarios which describes how many ways an activity can be accomplished.. then you MUST establish and document the requirements - Then design, get approval & build it.. then the customer will test is against the REQUIREMENT that are documented.if all is verified by the customer, then it is accepted...

[cedricluma]

Helloo.. Nice one .. Where are the other videos ?..

Thanks for posting.