https://luminoussheep.net/mediawiki/index.php?action=history&feed=atom&title=Agile_User_Stories 2026-05-11T19:22:20Z Revision history for this page on the wiki MediaWiki 1.43.8 https://luminoussheep.net/mediawiki/index.php?title=Agile_User_Stories&diff=81&oldid=prev 2021-09-14T21:38:29Z

<p>Created page with &quot;&#039;&#039;&#039;Notes from the excellent book User Stories Applied [http://www.amazon.co.uk/User-Stories-Applied-Development-Signature/dp/0321205685/] ISBN 0321205685 &#039;&#039;&#039; =Writing User St...&quot;</p> <p><b>New page</b></p><div>&#039;&#039;&#039;Notes from the excellent book User Stories Applied [http://www.amazon.co.uk/User-Stories-Applied-Development-Signature/dp/0321205685/] ISBN 0321205685 &#039;&#039;&#039;<br /> <br /> =Writing User Stories=<br /> Good stories : INVEST<br /> *Independent<br /> *Negotiable<br /> *Valuable to users<br /> *Estimable<br /> *Small<br /> *Testable<br /> <br /> ==Dependencies==<br /> #Combine stories<br /> #Split in a different way<br /> #2 Estimates - one before and one after dependent story<br /> <br /> ==Negotiable==<br /> * Short description - details negotiable<br /> * Important details annotated<br /> ** include undecided info as a prompt to resume discussion<br /> * Avoid excessive detail - consider separate card - details become tests<br /> * User stories for all stakeholders<br /> ** Avoid developer stories - reword in user context with user value<br /> * Avoid user interface/assumptions/technology<br /> <br /> ==Estimation==<br /> Problems:<br /> * lack of domain knowledge<br /> ** discuss until general understanding reached<br /> * lack of technical knowledge<br /> ** run technical spike - time box - experiment to learn enough to be able to estimate<br /> * story too big<br /> <br /> ==Types of user stories==<br /> ===Epic===<br /> Big picture<br /> <br /> ===Story===<br /> * Description for planning - card<br /> * Conversations for gasthering detail - conversation<br /> * Tests determine when complete - confirmation<br /> Should be written in business language - domain<br /> <br /> ==Prioritisation==<br /> # How desirable to all users<br /> # How desirable to subset of users<br /> # Cohesiveness to other stories<br /> # Cost<br /> Adjust requested by developers<br /> # Technical risk<br /> # Complementary to other stories<br /> <br /> ==Acceptance tests==<br /> Tests documented as soon as possible<br /> <br /> =User Stories=<br /> * Emphasis the verbal<br /> * Comprehensible by the user + dev<br /> * sized for planning<br /> * supports iterative development<br /> * defers detail until it is required<br /> * something the user would do in a single sitting<br /> <br /> Stories are epics until prioritised<br /> * Differed stories<br /> * Iteratively refined</div>

Martin