1 / 11

Agile Story Authoring

Agile Story Authoring. Nigel Mossman Standard Data systems Limited. What is a Story?. A task that can be performed in an Agile Project Describes a user requirement or feature Written in “business language” Clear statement of what the user needs Discrete functionality Can be tested

aiden
Download Presentation

Agile Story Authoring

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Story Authoring Nigel Mossman Standard Data systems Limited

  2. What is a Story? • A task that can be performed in an Agile Project • Describes a user requirement or feature • Written in “business language” • Clear statement of what the user needs • Discrete functionality • Can be tested • The planning game may decompose the story

  3. How Do I Write A Story? • As a <type of user>, I want <some goal> [so that <some reason>]. Example: As an order clerk, I want to search for a customer account so that I can determine start processing an order.

  4. Qualifiers • As a set of bullet points, note additional supporting features • Continuing the example: • Search by name (partial match) • Search by account number • Return no more than 20 matching accounts • List returned in under 10 seconds

  5. Qualifiers • Help the discussion with the developers • Identify test criteria • How will the developers know they’ve done what you asked for • Help you to think about story granularity

  6. Supporting Artefacts • Include supporting artefacts • Example documents • Screenshots • References to trade journals or books

  7. System Problems • Sometimes, an agile project might be fixing bugs in a system • Amend the story format: • As an order clerk, I would like the system not to crash when searching for customers with over 20 characters in their name. • It’s OK to describe solutions • Identify examples of when the problem occurs Developers cannot fix problems they cannot recreate

  8. Large Functions/Modules • Write a functional overview • Several paragraphs written in business language • Describing the features of the new function/module • Use story boards • When complete • Decompose into stories • Identify qualifiers for each story • May need 2-3 parses to complete

  9. Types of Story • Business Story • Regular story to add features to an application • Technical Story • Developer story which does not implement any business features but does resolve some essential technical problem.

  10. Spikes • Spike • Used when the solution is not obvious, there are several options or risk • Does not usually deliver any completed work • Does deliver sufficient to produce an estimate on how to deliver a story • Can be used for both business and technical stories • Users can requests spikes

  11. The End Discussion, questions & answers

More Related