Hans Samios' Personal Lean-Agile Knowledge Base

... absolutely #noabsolutes ...

User Tools

Site Tools

Trace: • what_are_the_steps_to_establish_a_development_manager • how_do_we_use_story_point_estimates_to_forecast • why_do_we_assign_business_values_to_pi_objectives • what_is_the_mapping_between_features_and_pi_objectives
how_do_we_split_user_stories

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
how_do_we_split_user_stories [2020/06/04 07:43] – [Need To Know More?] Changed Need to Want hanshow_do_we_split_user_stories [2021/04/28 11:35] (current) – Changed terminology to reflect more modern language hans
Line 13: Line 13:
 In other words, resist dividing the story up along "technical" boundaries as this will result in iterations of development with nothing complete (and valuable) to the end user. In other words, resist dividing the story up along "technical" boundaries as this will result in iterations of development with nothing complete (and valuable) to the end user.
  
-The question is then "how to I split a story if I don't use architectural boundaries?" One basic approach is to take the "Conditions of Satisfaction" for a User Story and use that to split the story up. So for example if the user story was "As a customer I want to pay with a credit card so I can get the item on sale", the "Conditions of Satisfaction" might be "Accept Visa; Accept MasterCard; Accept American Express" and so on. If it was determined that the Story is too big to fit in a Sprint, then you could split the Story as "As a customer I want to pay with a Visa card so I can get the item on sale" with its own Conditions of Satisfaction, and so on. Keep going until you have high priority items in the Product Backlog that are right-sized for a Sprint.+The question is then "how to I split a story if I don't use architectural boundaries?" One basic approach is to take the "Acceptance Criteria (or Conditions of Satisfaction)" for a User Story and use that to split the story up. So for example if the user story was "As a customer I want to pay with a credit card so I can get the item on sale", the "Acceptance Criteria (or Conditions of Satisfaction)" might be "Accept Visa; Accept MasterCard; Accept American Express" and so on. If it was determined that the Story is too big to fit in a Sprint, then you could split the Story as "As a customer I want to pay with a Visa card so I can get the item on sale" with its own Acceptance Criteria (or Conditions of Satisfaction), and so on. Keep going until you have high priority items in the Product Backlog that are right-sized for a Sprint.
  
 This type of thinking leads to the following general possibilities (using a different example): This type of thinking leads to the following general possibilities (using a different example):
/home/hpsamios/hanssamios.com/dokuwiki/data/attic/how_do_we_split_user_stories.1591281787.txt.gz · Last modified: 2020/06/04 07:43 by hans