This video is a high level introduction into agile requirements traceability. It demonstrates an example of agile requirements traceability. 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.
Writing an effective user story for a Scrum product backlog is easy … if you understand how.
INVEST is an acronym that you can use to remind the important attributes of great user stories: Independent, Negotiable, Valuable, Estimable, Small, and Testable.
The technique of expressing requirements as user stories is one of the most broadly applicable techniques introduced by the agile processes. User stories are an effective approach on all time constrained projects and are a great way to begin introducing a bit of agility to your projects. In this session, we will look at how to identify and write good user stories. The class will describe the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. We will explore how user role modeling can help when gathering a project’s initial stories. Because requirements touch all job functions on a development project, this tutorial will be equally suited for analysts, customers, testers, programmers, managers, or anyone involved in a software development project. By the end of this tutorial, you will leave knowing the six attributes of a good story, learn a good format for writing most user stories, learn practical techniques for gathering user stories, know how much work to do up–front and how much to do just–in–time.
Eric Evans advocates on gradual blending of modeling and design into iterative development based on a correct and deep understanding of the domain, avoiding both “analysis paralysis” and the “easiest solution” for a user story, in an attempt to create a solution that expresses the domain and is flexible enough to support future variations of the model.
A small video on to share ideas on how business analysts should participate in the Agile development process.
Related article: Agile Requirements
How does a team make sure they don’t lose sight of “non-functional requirements”? Are user stories of any use to make infrastructure more visible in the product backlog? This video presents how teams attempted to resolve these concerns. Discover patterns and anti-patterns of non-functional requirements in an agile world.
This video demonstrates an example of agile requirements traceability. 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.
Jeff Patton describes the different ways Agile teams deal with users and then digs in deep into story mapping – a technique that is more information rich than a simple backlog.
We’re agile, so we don’t have to estimate and have no deadlines, right? Wrong! This session will consist of an overview of the concept of agile estimation and the notion of re-estimation. We’ll learn about user stories, story points, team velocity, how to apply them all to estimation and iterative re-estimation. The lab will consist of an estimation project and doing a round or two of “planning poker”.keep looking »