As an agilist, I want to write great user stories so that... Ryan 08.27.2013 Tampa Bay Agile Meetup.

Slides:



Advertisements
Similar presentations
Introducing User Stories
Advertisements

Applying Agile Methodologies to Traditional Publishing Kristen McLean Bookigee, Inc. February 12 th, 2011.
Behavior Driven Test Development
Focus on Your Content, Not on Ingesting Your Content Terry Brady Applications Programmer Analyst Georgetown University Library
Creating Page Layouts using SharePoint Designer or Visual Studio Becky Bertram MCSD, MCAD MCTS WSS Development MCTS MOSS Development
Iteration Planning.
Acceptance Testing.
02 | Define an Effective End-to-End Software Development Lifecycle Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant,
User Stories Testing 2, October 21.
TDT 4242 Inah Omoronyia and Tor Stålhane Agile requirements through user stories and scenarios TDT 4242 Institutt for datateknikk og informasjonsvitenskap.
Practical User Stories Brett Maytom Senior Consultant, Readify VIC.NET - 10 May 2011.
Writing Good User Stories Bob Schommer, CSP, PMP Senior Project Manager Skyline Technologies, Inc.
©2011 Improving Enterprises, Inc. Breaking down the Epic User Story.
Renato Pinto López TUM18 - UPM. Sprint Planning Meeting ATTENDED BY PRODUCT OWNER (PO), SCRUM MASTER AND SCRUM TEAM PO DESCRIBES THE HIGHEST PRIORITY.
Steve Collins Richland County IT Manager Agile.  Have Fun  Learn About Agile  Tell Some Stories.
May 4, 2015 Writing Stories 7 September, 2006 Kane Mar.
Non-Coding Activities a Development Team Needs a.k.a ”I don’t code, am I no longer useful?” Maaret Pyhäjärvi| | Twitter: maaretp Test Granlund.
Agile development By Sam Chamberlain. First a bit of history..
05 | Define End Value for the Software Iteration Steven Borg | Co-founder & Strategist, Northwest Cadence Anthony Borton | ALM Consultant, Enhance ALM.
CS350/550 Software Engineering Lecture 1. Class Work The main part of the class is a practical software engineering project, in teams of 3-5 people There.
An Agile View of Process
Living Requirements using Behavior Driven Development
Test Driven Development using Visual Studio Team System Ariel Gur-Arieh VP R&D – MCD Software Solutions
January 17, Dojo. Copyright © 2015 Open Source ERP Users Group All Rights Reserved. 2 Table of Contents 1.Setting Up OpenERP 2.Starting Your.
Processes, Tools, & Best Practices. My Background Lexmark Software Development for 15 years (‘93 – ‘08) – Multi-tier Java application servers – Window.
Agile Acceptance Testing Software development by example Gojko Adzic
Copyright BSPIN Agile Practices Benchmarking Case Study by Mazataz – Tesco.
Scrum’s Product Owner Role Jeff Patton Agile Product Design
Software Testing Life Cycle
Steve Fastabend Agile Coach Redpoint Technilogies
R ELEASE P LANNING. H ELPFUL R ESOURCES Planning Extreme Programming, Kent Beck and Martin Fowler Extreme Programming Installed, Ron Jeffries, Ann Anderson.
Beyond the wall of issues - Focus to drive velocity Mathew Aniyan Program Manager, Microsoft.
5. Planning.
4/23/ :45 PM © 2007 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered.
Agile User Stories. What is a User Story? User stories are short, simple description of a feature told from the perspective of the person who desires.
CSE Senior Design I Building a Plan Instructor: Mike O’Dell Several of the slides in this module are a modification and amplification of slides prepared.
Chapter 3 Agile Software Development (1/2) Yonsei University 2 nd Semester, 2015 Sanghyun Park.
TEST-1 6. Testing & Refactoring. TEST-2 How we create classes? We think about what a class must do We focus on its implementation We write fields We write.
Tejasvi Kumar Developer Technology Specialist | Microsoft India
With a hint of HP Quality Center Agile development and functional testing: friend or foe? Tom Vercauteren, June 26th, 2009.
User Stories 1-3 sentences in everyday language “Connextra” format:
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
AGILE XP AND SCRUM © University of LiverpoolCOMP 319slide 1.
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
Nigel Mossman Standard Data systems Limited.  A task that can be performed in an Agile Project  Describes a user requirement or feature  Written in.
Jim Remsik Agile Story Carding prepared
CS223: Software Engineering Lecture 18: The XP. Recap Introduction to Agile Methodology Customer centric approach Issues of Agile methodology Where to.
Introduction to Software Engineering Muhammad Nasir Agile Software Development(2)
User Stories- 2 Advanced Software Engineering Dr Nuha El-Khalili.
Introduction to Agile. Introduction Who is this guy?
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Project Workflow.
Chapter 5 Agile Development Moonzoo Kim KAIST
Penn State Project Management Conference
Software & Software Engineering Pertemuan-4 Dosen :Kundang K Juman
(Professional Business Analyst Training organisation)
Project Workflow.
Dr. Rob Hasker SE 3800 Note 3 Ch. 4, 5.
September 20, 2017 Agile Techniques Workshop Susan Futey
Real Metrics for Real Decisions
Requirements and User Stories
Pega 9/14/2018 8:48 AM Definition of Done = ready for PO acceptance
Decomposition.
Teams Want a Quick Game to Learn How to Deliver Value Faster
User Stories Applied, Mike Cohn Chapter 2: Writing Stories
Making small stories.
User Stories Applied, Mike Cohn Chapter 2: Writing Stories
Agile Development – a new way of software development?
Story Writing.
How To Improve UX Performance In Agile
Presentation transcript:

As an agilist, I want to write great user stories so that... Ryan Tampa Bay Agile Meetup

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 Bio

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

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

User Story Cadence As a, I want to, so that

Are user stories enough? Card ConversationConfirmation As a, I want to, so that 1.Item 2.2ITe 3.Item 4.Item 5.Item

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

Live by INVEST INDEPENDENTNEGOTIABLE ESTIMABLESMALL VALUABLE TESTABLE

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

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

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

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

Acceptance Criteria Examples RefFieldRules 1Promo Code The promo code, itself cannot be altered during the time between the Promo Start Date and Promo End Date. 2Promo Code Allow the start date of the promo to be modified if the current date is <the start date (i.e. if the promo code is not yet active, the start date can be changed) 3Promo Code All promo codes can only be used once and cannot be reused for another promotion. 4Promo CodeThe Total Limit of a promo code for a particular promotion can be modified if the Current Date <End Date. Given an Existing Promo Code, When it saved, Then the following rules are applied:

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

Acceptance Criteria Examples As a mobile app user I want to view my current medications so that I can be informed of duplicate therapy conflicts. 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 Filled as: Drug1a Duplicate Drug 2 Filled as: Drug2a Drug 4 Filled as: Drug4a Drug 2 Filled as: Drug2a Duplicate Drug 1 Drug 4 Duplicate Drug 1

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

Thank you!