Using Story points is a technique used by Scrum team to evaluate the relative size of user stories. If this technique works fine for single teams, it might be more problematic when multiple teams are involved. In this article, Paul Raymond explains why user story normalization is needed in contexts where multiple Scrum teams cooperate on the same user stories.
Most agile software development team grapple with user stories as a technique for understanding what needs to be developed iteratively. This talk presents some techniques for uncovering useful user stories and how to slice them in a way to deliver value in small increments.
Non-functional requirements relate to qualities of the system that cut across user facing features, such as security, reliability, and performance. How does an Agile team take care of these non-functional requirements? This presentation discusses if user stories are of any use in this situation and how Scrum teams can applying Agile techniques to solve these concerns.
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.
The definition of “Done” (DoD), which means that a feature is ready for delivery, is a concept often discussed in Scrum. In this blog post, George Dinwiddie discusses the concept of “Ready” that apply to user stories that are ready to be developed.
User stories and their format defined by Mike Cohn “As a , I want so that .” are a classical way to record requirements in Scrum project. In his blog post, Alan Klement discusses a new format that he called “Job Stories” with the format “When … , I want to … , so I can … .”
User stories and their size are often the basis for planning a Sprint in Scrum. You can use a relative estimation and planning poker or a more classical approach to define the effort for each user stories. As such, they are also the basis for the metrics of progress and the velocity of the Scrum team.
Scrum Expert Copyright © 2009-2023 Martinig & Associates