From Classical Requirements To User Stories
From Classical Requirements and Use Cases to a Backlog of User Stories
Target audience: Product Owners, Business Analysts, and anyone else interested in the topic
In most cases circa 2008, agile teams are formed in the midst of traditional IT organizations. It's rare that an entire organization undertakes a radical transformation from top to bottom all at once.
Agile teams are geared to work from a backlog of user stories. In most IT organizations, they are handed a set of specifications or requirements in a different form. It can be challenging to convert those requirements into a form that is actionable by an agile team without
(a) losing useful information that was gathered previously, or
(b) slipping back into a BDUF approach by working directly from the formal requirements documents.
This session aims to address the issue by presenting tips for transforming
(a) a requirements document in "classical" form, such as "the system shall this, the system shall that" and
(b) requirements in the form of RUP-style Use Cases into a backlog of user stories.
We are visualizing two workshop segments: One to deal with the "classical" style of requirements specification, and the other to deal with Use Cases.
The basic outline
Presentation segment giving tips for converting "classical" requirements specifications into an actionable backlog. Workshop in which participants practice converting the classical requirements into a backlog of user stories. Presentation segment giving tips for converting a set of Use Cases into an actionable backlog. Workshop in which participants practice converting the Use Cases into a backlog of user stories.