May 4, 2015 Writing Stories 7 September, 2006 Kane Mar.

Slides:



Advertisements
Similar presentations
Copyright © , Armstrong Process Group, Inc., and others All rights reserved Made available under EPL v1.01 Project Management Review Eclipse Process.
Advertisements

Armstrong Process Group, Inc. Copyright © , Armstrong Process Group, Inc., and others All rights reserved Armstrong Process.
Applying evo to a project An Agile and EVO Workshop Based on the article Measuring Agile Value in Overload 89, by Ryan Shriver, and used with his permission.
Iteration Planning.
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.
Copyright Robert W. Hasker. Imperative Requirements- based Development  System specification: series of “shalls”  The registration system.
Agenda −Scrum with TFS 2010 using MSF for Agile 5.0 −Planning the Project −How do you plan the project? −Project planning in TFS 2010 −Planning a Sprint.
MAY 11, 2011 WRITING USE CASES IN AN AGILE WORLD KARL O’BRIEN SENIOR SOLUTIONS ENGINEER BLUEPRINT SYSTEMS.
ITEC 370 Lecture 25 Lifecycles. Review Questions? F give prototype demonstration –Testing plan for your software Life cycles –Scrum (Roles, Meetings,
Agile Project Management with Scrum
Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.
Transitioning to XP or The Fanciful Opinions of Don Wells.
Writing User Stories. Product owners … … always have unlimited desires but limited resources … have requirements, which necessitate communication with.
Agile-SCRUM. Introduction to SCRUM Sanil Xavier What is Scrum?
Managing a Project Using an Agile Approach and the PMBOK® Guide
S R S S ystem R equirements S pecification Specifying the Specifications.
Getting well written requirements and user stories from your Business Analysts Keith Richards KRC (Agile’s unsung heroes!)
PopMedNet Software Development Life Cycle Chayim Herzig-Marx Harvard Pilgrim Health Care Institute Daniel Dee Lincoln Peak Partners.
© 2010 AT&T Intellectual Property. All rights reserved. AT&T and the AT&T logo are trademarks of AT&T Intellectual Property. Deeper Dive Into: User Stories.
Use Cases 2 ENGR ♯10 Peter Andreae
What is Scrum Process? Where is it used? How is it better?
E-Learning Material Web Application Design 2. Web Application Design Use cases Guidelines Exceptions Interaction Sequence diagrams Finding objects.
Rational Unified Process (Part 1) CS3300 Fall 2015.
© BJSS Limited Going Agile UK TMF - April 2011 Mark Crowther, Test Consultant.
1 REQUIREMENT ENGINEERING Chapter 7. 2 REQUIREMENT ENGINEERING Definition Establishing what the customer requires from a software system. OR It helps.
Steve Fastabend Agile Coach Redpoint Technilogies
Requirements Engineering How do we keep straight what we are supposed to be building?
1 Chapter 5 Practice: A Generic View Software Engineering: A Practitioner’s Approach, 6th edition by Roger S. Pressman.
Notes from Pauls Session. Contract always a problem, either shackles you or too woolly Test management of agile project – no one felt it was comfortable.
CS 3610: Software Engineering – Spring 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class.
R ELEASE P LANNING. H ELPFUL R ESOURCES Planning Extreme Programming, Kent Beck and Martin Fowler Extreme Programming Installed, Ron Jeffries, Ann Anderson.
Mobile Aps: Agile Mentoring Review
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.
Agile Concepts - II “Agile” Estimating & Planning Nupul Kukreja 5 th November, 2014.
Software Engineering Saeed Akhtar The University of Lahore Lecture 6 Originally shared for: mashhoood.webs.com.
Acceptance criteria vs. Functional requirements by Anna Dąbrowska.
44222: Information Systems Development Documenting a Solution Ian Perry Room:C41C Extension:7287
© ThoughtWorks, 2007 Getting Agile or How I learned to stop worrying and love the index cards CIPS Business Analysis SIG Event JOHN JOHNSTON ThoughtWorks.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting May 19, Acceptance Criteria Defining Success one Story.
Agile: Lessons Learned (a retrospective) Tony
Chapter 7 The Practices: dX. 2 Outline Iterative Development Iterative Development Planning Planning Organizing the Iterations into Management Phases.
Initiation and Planning for Success Sridhar Seshagiri Rao, PMP Innova Solutions Inc. Santa Clara, CA. April 9 th 2004.
BA Team: Product Ownership, Analysis, and Solution Design BA Bi-Weekly Mini-meeting March 3, Gathering Requirements On an Agile Project…
Agile User Story. Agile – User Story us·er stor·y uzər st ɔ ri noun A user story is a tool used in Agile software development to capture a description.
Copyright Robert W. Hasker. Requirements-based Development  System specification: series of “shalls”  The registration system shall support.
1 What is the Software Life Cycle? The stages of developing a software application Requirements Analysis High-level Design Plan Low-level Design Implementation.
Cultivating Agile Requirements
BEHAVIOR DRIVEN TEST DEVELOPMENT Specification by Example All Rights Reserved - Sound Agile Consulting.
Jim Remsik Agile Story Carding prepared
Project Management Enabling Quality Marien de Wilde, PMP April 2007.
User Stories- 2 Advanced Software Engineering Dr Nuha El-Khalili.
Introduction to Agile. Introduction Who is this guy?
CSE Senior Design II Scrum Review/Discussion Instructor: Mike O’Dell.
Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Informed Traveler Program and Applications Agile / Scrum Overview Jerry Inberg.
Planning 2: Estimation Mechanics Emerson Murphy-Hill Creative Commons Attribution 4.0 License. Material Produced by NCSU Software Engineering Faculty.
User Stories > Big and Small
SYSTEM ANALYSIS AND DESIGN
Mike Cohn - Agile Estimating and Planning
System Requirements Specification
Decomposition.
Definition of Ready.
Analysis and Understanding
CSCE 741 Software Process Lecture 04 Availability
Adapting Agile in Pharmaceutical Industries
Story Writing.
Presentation transcript:

May 4, 2015 Writing Stories 7 September, 2006 Kane Mar

May 4, 2015 The problem with Users … … is that they always want something! Requirements is a problem of communication between those who have a problem and those who can provide the solution to that problem.

May 4, 2015 Negotiation over Contracts “Since users don’t know how to solve their problems, we need to stop asking … and to involve them instead” - Mike Cohn

May 4, 2015 Agenda Writing User Stories Decomposing Epics Writing Acceptance Criteria

May 4, 2015 What is a Story? “Promise for a future conversation” - Ron Jeffries

May 4, 2015 What is a Story not? Stories are not: –“mini” Use Cases –a complete specification –a contract –intended to be interpreted without a Product Owner

May 4, 2015 A Story template. “As a I want So that ” Example: As a Account Holder, I want to be able to withdraw funds from my checking account, So that I can buy some bling.

May 4, 2015 What is an Epic? Are usually compound Stories, that can be broken down into several smaller, more focused stories May encompass enough work for several Sprints (iterations)

May 4, 2015 Some guidelines to writing good User Stories Testable. Tangible acceptance tests can be written against any delivered software The scope of the User Story is manage-able enough for the team to provide an Estimate Independent and do not rely on other Stories Sized appropriately. Have a level of effort which the team can comfortably achieve in the duration of a single iteration

May 4, 2015 Agenda Writing User Stories Decomposing Epics Writing Acceptance Criteria

May 4, 2015 Some places to consider breaking Epics At C.R.U.D boundaries At system boundaries where two systems interface At Happy-Path / Exception-Path boundaries

May 4, 2015 At CRUD boundaries: This solution is commonly used in environments that interact with a database Example: As an account holder, I want to be open a checking account … As an account holder, I want to deposit a cheque into my checking account … As an account holder, I want to view the updated balance in my checking account …

May 4, 2015 At system boundaries: This solution is commonly used in environments where there are a large number of legacy systems And can be used: –When there is a clear separation between two systems –Where the interface between the two systems is well understood A word of caution: beware of creating dependencies between two different projects

May 4, 2015 At Happy-Path / Exception-Path boundaries: Commonly used when transitioning from Use Cases The happy-path scenario may still need to be decomposed Breaking down Use Cases can be a lot of work … it may be simpler to just start using User Stories

May 4, 2015 Agenda Writing User Stories Decomposing Epics Writing Acceptance Criteria

May 4, 2015 What are Acceptance Criteria? Product Owner expectations on what will be delivered Acceptance Criteria can include: –Functionality that the system will perform –Interface look and feel –Necessary documentation (eg. SOX compliance documentation)

May 4, 2015 Some guidelines to writing good Acceptance Criteria Be explicit –“The system will display the date.” … –In what format? Is “2006, April 1 st” acceptable? Provide examples for clarity –“The system date will be displayed in the format 1/4/06” List any assumptions that the team may not be fully aware of

May 4, 2015 Some guidelines to writing good Acceptance Criteria Include what you’d expect the system to do … –“The checking account balance will be updated with the amount entered by the user.” … and where ambiguous, what the system is not expected to do –“Reconciliation with the amount of funds deposited is not expected at this time.”

May 4, 2015 References “Users Stories Applied”, Mike Cohen “Agile Estimating and Planning”, Mike Cohen