Group items tagged

The Agile Extension to the BABOK® Guide

The importance of business analysis practices

How business analysis is performed in agile lifecycles

Agile Software Development21+4£45,000-10114 (8.23 %)

Scrum35+10£47,500-6778 (5.51 %)

Big-View (Product)

Pre-View (Release)

Now-View (Iteration)

As a … I want… so that…” is a new-fangled user story format. The original XP user story format had no rules, so you could simply highlight any phrase in a use case and call it a user story. Personally, I feel sorry for anyone who has to write “As a… I want… so that…” for 200 user stories. Kind of like being kept after school and having to write “I will not write silly user stories in class” 100 times

A use case pretty much by definition contains multiple stories. A use case is a collection of scenarios related to the primary actor’s goal – some scenarios show the actor interacting with the system and the system interacting with other systems so that they succeed with the goal, some show failure. That’s all in the nature of a use case. see Structuring use cases with goals (discussion: Re: Structuring use cases with goals) from 1995. A use case written for this will occupy between half a page for a shortish one to 2 pages for a long one. A user story is a nickname for a single scenario – it contains neither the information content of the scenario nor failure or alternate paths. A user story typically occupies 1/2 to one sentence no matter its size.

(p.s. Agile was supposed to reduce bureaucracy and overhead, not add to it. :) Alistair

re-focuses on the essentials and offers a slimmed down, leaner way of working, for software teams seeking the benefits of iterative, incremental development at an enterprise level

Author: Ivar Jacobson, Ian Spence, Kurt Bittner

Based on several years of work with many of our customers around the world, we have revamped use cases to provide a scalable approach to managing requirements for agile projects and programs.