Agile Pies
Published in

Agile Pies

Ways to split big User Story into smaller ones

Viewpoits for user story splitting/slicing and decomposing
  1. dividing the story into subtasks by type of work — for example, write requirements, design a solution, create a design layout, write code, etc. — or by architectural layers;
  2. dividing a large story into smaller, independent stories that fit in one sprint.

Why is it necessary that the story fit in 1 sprint?

  • Following the Scrum principle of incrementality. Of course, not a blind following — there are many advantages to working with increments, 15 of them are listed here.
  • Simple idea — work with the risk of not being on time.
  • And you can also decompose even during the sprint, when you realize that you will not have time to complete the task in the current statement.

And now 2x2 types of decomposition and splitting in more detail

  1. Decomposition by stages of the product creation process
  2. Decomposition by architecture layers, platforms, components
  3. Splitting by business process roles and steps
  4. Splitting by the level of detail with which you implement different parts of the feature

Decomposition by stages of software development process

Decomposition by stages of the product creation process

Decomposition by architecture layers, platforms, components

Decomposition by architecture layers, platforms, components

Splitting by business process roles and steps

Splitting by business process roles and steps

Splitting by the level of detail with which you implement different parts of the feature

Splitting by the level of detail with which you implement different parts of the feature

All together

--

--

Ideas and Howtos on Team management, projects and Agile, written simple and useful

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store