Home » Archives

Content tagged with: user stories

[22 Nov 2012 | Comments Off on Can Requirements and Agile Work Together | ]

This software testing podcast discusses why requirements are still needed in many projects, and how to work with both requirements and user stories to deliver on the promise of Agile.

[19 Oct 2012 | Comments Off on Lightweight User Story Mapping | ]

User story mapping might look like the heavy weight mapping of the past, but it is not. However, if you can’t map your stories back to business value, then why do they make or save the company money? Learn how to improve your business analysis with Agile story mapping.

[5 Sep 2012 | Comments Off on Splitting Features and Epics into Playable User Stories | ]

There’s a lot of the literature available on how to write and flesh out a user story – how to frame the story statement, what to include, how to write good acceptance criteria, etc. There is less written about how to carve out good, playable user stories from a complex feature or epic story in the first place. This workshop uses 3 case studies drawn from real projects to focus on this latter skill, demonstrating how close collaboration between analysts, customers, developers, testers, and UX designers can result in user …

[5 Jul 2012 | Comments Off on User Stories for Agile Requirements | ]

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. Mike Cohn explains how to identify and write good user stories. He describes the six attributes that good stories should exhibit and present thirteen guidelines for writing better stories. He explores how user role modeling can help when gathering a project’s initial stories.

[27 Jun 2012 | Comments Off on Identifying User Stories in Sprint Backlog | ]

A Sprint Backlog is typically associated with a Scrum project. The Scrum Sprint backlog identifies all of the user stories, the pieces of work, the business functionality, that will be delivered in at the end of the Sprint which has a 2 to 4 weeks duration.

[30 May 2012 | One Comment | ]

At the outset of an Agile project one of the first tasks at hand is to properly break down the requirements of the new application in to user stories. Discover 5 (or more) agile tools which will help you:
* Identify and rationalize requirements
* Quickly and effectively identify minimum application features at a macro level
* Organize user story cards

[22 May 2012 | Comments Off on User Stories Walking Exercise | ]

In this blog post, Dhaval Panchal proposes a technique that help slicing agile user stories. He uses it for stories ‘not-done’ at the end of sprint or team that have problems to split stories horizontally across components. The idea is linked to the experience of taking your dog to a park for a walk. The team will walk each end user functionality through the architectural component park. During this walk you estimate each user stories to see if it is feasible to develop them in one sprint, you can detect …

[25 Apr 2012 | Comments Off on Comprehensive User Stories | ]

A user story is a high-level requirement of a feature provided from the perspective of a stakeholder. A comprehensive user story has acceptance criteria that cover all possible functional scenarios or conditions needed to satisfy the user requirements. In development and testing terms, this means defining positive and negative scenarios. This article defines what differs between the normal user stories and the comprehensive user stories.

[18 Apr 2012 | Comments Off on User Stories and Use Cases | ]

What is the difference between user stories and use cases. This video shows the difference between them with examples, and also shows how they can be related.

[27 Mar 2012 | Comments Off on Complementing User Stories | ]

User stories are well established in agile software development processes, but they should not be seen as detailed requirements specifications. It is accepted that the end users do not know all the requirements at once. Therefore, user stories only give hints about the expectations of an end user. A computer supported strategy is proposed to get more details in a communications process. This strategy focuses on the agile development of information systems. Namely, it is proposed that additional information, not found in a user story, is extracted from natural language …