From the course: Agile Analysis (IIBA®-AAC) Cert Prep

Unlock this course with a free trial

Join today to access over 25,300 courses taught by industry experts.

Story decomposition

Story decomposition

- I'm sure you've heard before that your user stories or requirements might be too vague or perhaps too detailed, maybe both. You can address this by using a technique called Story Decomposition. It's a technique that uses analysis skills to break down and decompose user stories into smaller pieces, while still keeping the best practices of user stories in play. Lets talk about how Chris, our agile BA uses story decomposition. He first works with the team to understand which stories on the backlog are too big to be estimated or just need more depth. The most typical approach to story decomposition is called breath over depth, meaning that he first wants to make sure he understands the high level goals of the user, then the features, then the smaller stories, and then the acceptance criteria. Chris knows that decomposition happens progressively and over time as the team learns more. It can be wasteful to work on the details…

Contents