From the course: Agile at Work: Planning with Agile User Stories

Unlock the full course today

Join today to access over 24,900 courses taught by industry experts.

Identified state

Identified state

From the course: Agile at Work: Planning with Agile User Stories

Start my 1-month free trial Buy for my team

Identified state

“

- The beginning point of a story lifecycle is identification. Let's start with a feature and break it down into stories. Features that a customer interacts with will typically have a series of steps or actions that the customer will move through to accomplish something. These steps in the workflow generally are stories. Here, we can see the work in a brainstorming session where the feature was decomposed into actions the customer may take. Each action, represented by a sticky note, becomes a user story. Most user stories are identified early in the project's timeline. Remember that this requires minimal time, as the depth of understanding of each story, through discussion and acceptance criteria, is done just before we implement a given story. If you want more details about what this looks like, please refer to the earlier video on identifying stories, where I shared an example of brainstorming with stakeholders and team members. Now that we have identified the majority of stories for…

Contents