Skip to content

Commit

Permalink
Updated Story Splitting
Browse files Browse the repository at this point in the history
Added A Practical Guide to User Story Splitting for Agile Teams
  • Loading branch information
lorabv authored Jul 11, 2019
1 parent 7910ede commit ee483bd
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions Story-Splitting.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,6 +2,8 @@

- [10 Powerful Strategies for Breaking down User Stories in Scrum (with Cheatsheet)](https://medium.com/@chrisverwijs/10-powerful-strategies-for-breaking-down-user-stories-in-scrum-with-cheatsheet-2cd9aae7d0eb) - by Christiaan Verwijs. "In Scrum, a vertical break-down is more useful, in which user stories are broken down into smaller user stories (instead of technical tasks). If user stories are broken down vertically, they are broken down in such a way that smaller items still result in working, demonstrable, software. Functionality will not be split across technical layers or tasks, but across functional layers. So, if the user story is ‘As customer I can pay for my order, so I can get my products’, it can be broken down into smaller user stories like ‘As customer I can pay by wire transfer, so I can get my products’ or ‘As customer I can pay with credit card, so I can get my products’."

- [A Practical Guide to User Story Splitting for Agile Teams](https://techbeacon.com/app-dev-testing/practical-guide-user-story-splitting-agile-teams) - by Mark J. Balbes. "Many small stories add up to a releasable feature, but each story should be releasable by itself. This allows the product owner and the team to get quick feedback on the larger feature being built, with the expectation that this will steer the ultimate direction of the feature and maximize user value."

- [How to Split a User Story](http://agileforall.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf) (Flowchart) - by Agile For All. A flowchart showing different patterns split a user story.

- [INVEST in Good Stories, and SMART Tasks](http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/) - by Bill Wake. "As you discuss stories, write cards, and split stories, the INVEST acronym can help remind you of characteristics of good stories. When creating a task plan, applying the SMART acronym can improve your tasks." INVEST: Independent, Negotiable, Valuable, Estimable, Small, Testable; SMART: Specific, Measurable, Achievable, Relevant, Time-boxed
Expand Down

0 comments on commit ee483bd

Please sign in to comment.