1 / 20

As an agilist , I want to write great user stories so that...

Learn how to create great user stories that accurately capture project requirements while promoting shared understanding and collaboration. Explore the role of user stories in agile development and discover strategies for effective decomposition. Avoid common user story anti-patterns and gain insights into acceptance criteria and examples.

spursell
Download Presentation

As an agilist , I want to write great user stories so that...

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. As an agilist, I want to write great user stories so that... Ryan Dorrell @ryan_dorrell 08.27.2013 Tampa Bay Agile Meetup

  2. Bio • CTO, co-founder, AgileThought (since 2004) • Started professional career developing using 16-bit VB4 on Win 3.1 at Arthur Andersen in Sarasota, FL • Since then: • OnSphere in Raleigh, NC (VB6, .NET, Java) • PricewaterhouseCoopers in Tampa, FL (Java) • Co-founded AgileThought in 2004 with David Romine, John Wagner • At AgileThought: • Development, technical leadership, plus helping teams and organizations adopt agile and ALM practices and processes • @ryan_dorrell • @agilethought

  3. User Stories Think about requirements differently A promise for a future conversation Specifying in writing doesn’t work well

  4. http://www.cakewrecks.com/

  5. http://www.cakewrecks.com/

  6. User Stories Think about requirements differently A promise for a future conversation Shared documents aren’t shared understanding Specifying in writing doesn’t work well

  7. User Story Cadence As a <role>, I want to <action>, so that <value>

  8. Are user stories enough? Conversation Confirmation Card As a <role>, I want to <action>, so that <value> As a <role>, I want to <action>, so that <value> Item 2ITe Item Item Item

  9. What about use cases? …is as a gazelle is to a gazebo. A user story is to a use case…

  10. Live by INVEST VALUABLE NEGOTIABLE INDEPENDENT TESTABLE ESTIMABLE SMALL

  11. User story anti-patterns Actually just a task Too technical Too large Describes implementation UI-focused Not user-focused

  12. Decomposition strategies By Workflow Steps By User Interface Model By Operation Split out spikes By Data Entry Method By Persona

  13. Examples As a user, I want to view my dashboard page As a product owner, I want the password to have complexity requirements As a customer svc rep, I want to manage a customer’s account As a developer, I want to refactor the database connection code

  14. Acceptance Criteria PO expectations on what will be delivered Can include: Functionality, look/feel, non-functional expectations Given… When…. Then… Automation tool support exists

  15. Acceptance Criteria Examples • Given an Existing Promo Code, • When it saved, Then the following rules are applied:

  16. Acceptance Criteria Examples As a mobile app user I want to accept the EULA just once when I log into the mobile app so that I’m legally in agreement with the company. Given when a user logins for the first time When they have never accepted the EULA before Then prompt to read the EULA and click Accept or Decline If user clicks Decline Then logout the user and return to login page If user clicks Accept continue on Also check for the version # of the EULA - if later, get text for latest version and display with accept/decline Since more than 1 user can use a device, track if the EULA has been seen by each user on each device

  17. Acceptance Criteria Examples Group by individual drugs.  Sort the ones with problems to the top, then alphabetical order by the "written as" field.  Display the "filled as" field also below the "written as" field.  Tapping the drug name should take them to the prescription details screen.  Select/tap to drop-down the different sections. Lo-fi mockup: [Text block at top indicating what to do] <!> Drug1     <downarrow> Filled as: Drug1a   Duplicate     Drug 2     Filled as: Drug2a     Drug 4     Filled as: Drug4a <!> Drug 2 <downarrow> Filled as: Drug2a   Duplicate     Drug 1 <!>  Drug 4 <downarrow> Duplicate Drug 1 As a mobile app user I want to view my current medications so that I can be informed of duplicate therapy conflicts.

  18. Parting words Groom often and with vigor. Work to split stories to the smallest consumable portion. Think Asteroids. Don’t get hung up on making a story absolutely perfect. Focus on the conversation.

  19. Thank you!

More Related