Jim Remsik Agile Story Carding prepared

Slides:



Advertisements
Similar presentations
Introducing User Stories
Advertisements

Finding the Main Idea How to Read Smarter.
Iteration Planning.
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.
 What if we can NEVER specify a requirement precisely enough that there won’t be this kind of ambiguity?  Maybe the problem is that we’re just afraid.
User Stories in an Agile Environment Mike McLaughlin, PMP, CSM, CSP Project Management Institute Kansas City Mid America Chapter March 19, 2012.
May 4, 2015 Writing Stories 7 September, 2006 Kane Mar.
Stoimen Stoimenov QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Five Finger Rule Sometimes it is difficult to know if a book is going to be too easy or too hard by just looking at it. The Five Finger Rule is one way.
Intro to Scrum. What is Scrum? An answer to traditional “fixed cost / strict requirements” contracts which had very high rates of failure Recognizes the.
Notes on how to read a paper Reading is more than just passing your eyes over the words in consecutive order. Reading is understanding.
Writing User Stories. Product owners … … always have unlimited desires but limited resources … have requirements, which necessitate communication with.
Stoimen Stoimenov QA Engineer QA Engineer SitefinityLeads,SitefinityTeam6 Telerik QA Academy Telerik QA Academy.
Getting well written requirements and user stories from your Business Analysts Keith Richards KRC (Agile’s unsung heroes!)
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
Mrs. Wills.  What does a good study space look like?  What does “time management” actually mean?  How can this help me?  What time is my “PLT” or.
Roles Managers Technical Team Leaders Programmers Customers Database Administrators Instructors.
Agile Acceptance Testing Software development by example Gojko Adzic
© 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.
Copyright Robert W. Hasker. Story Review  Elements of a Scrum story:  The three C’s:  Sprintable stories:  Mechanisms for obtaining stories:
R ELEASE P LANNING. H ELPFUL R ESOURCES Planning Extreme Programming, Kent Beck and Martin Fowler Extreme Programming Installed, Ron Jeffries, Ann Anderson.
Release and Iteration Planning September 13, 2008.
Classical vs. Agile Requirements Development Svetlin Nakov Telerik Software Academy academy.telerik.com Senior Technical Trainer
Mobile Aps: Agile Mentoring Review
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.
Requirements Analysis via Use Cases SE-2030 Dr. Rob Hasker 1 Based on slides written by Dr. Mark L. Hornick Used with permission.
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.
Adjectives Adjectives ending in ‘-ed’ describe a feeling, e.g. bored Adjectives ending in ‘-ing’ describe people or things, e.g. boring.
How We Promoted Safe Driving and Utilized the Media To Do It.
Investigator Eyes See the Big Picture LAFS.K.RI.3.7: With prompting and support, describe the relationship between illustrations and the text in which.
User Stories 1-3 sentences in everyday language “Connextra” format:
We even iterate on the requirements Gathering Requirements 1.
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.
Peace Operations Tool Kit User Story Report Edwin Padilla & Mamadou Balde Senior Seminar Fall 2015 November 17 th, 2015 Dickinson College.
1 What is the Software Life Cycle? The stages of developing a software application Requirements Analysis High-level Design Plan Low-level Design Implementation.
Planning Extreme programming
#CASEindiana { Social Media Social Media for Customer Service CASE Indiana 2014 Fall Conference Marian University, Indianapolis.
Agile Requirements Introducing User Stories. Key Principles for Agile Requirements Active user involvement is imperative Agile teams must be empowered.
WHY USER STORIES? Traditional Requirements Gathering: – Complex / time-consuming – Perfecting – Reluctant to change – once written – “heavy”
Reader’s I want to talk to you about my friend who is a lawyer. He was working on this case for weeks and he had to find proof that the defendant was.
Prepared by Amira Selim 31 st October 2009 Revised by Dahlia Biazid Requirements Analysis.
User Stories- 2 Advanced Software Engineering Dr Nuha El-Khalili.
By Manish Shrotriya CSE MS 4 Point Agile Manifesto 1.Individuals and interactions over processes and tools 2.Working software over comprehensive.
Matching Exercise Creating User Stories Planning Poker Risk/Value Quadrant Mapping Advanced Burndown Interpretatio n Interactive.
Testing under the Agile Method CSCI 521 Software Project Management based on the book Testing Extreme Programming by Lisa Crispin and Tip House.
It seems 2017 year is best to redesign your website. So many business, startup business lunching new website with attractive design by using the latest.
User Stories 1.
Penn State Project Management Conference
User Stories > Big and Small
COMP8040 – Cloud Application Frameworks Agile Project Management
Scrum.
Dr. Rob Hasker SE 3800 Note 3 Ch. 4, 5.
Software Requirements
September 20, 2017 Agile Techniques Workshop Susan Futey
Requirements and User Stories
Taking an Iteration Down to Code
Decomposition.
Summarizing Our Models to Date
User Stories Applied, Mike Cohn Chapter 2: Writing Stories
CSCE 741 Software Process Lecture 04 Availability
Prepared by Stephen M. Thebaut, Ph.D. University of Florida
User Stories Applied, Mike Cohn Chapter 2: Writing Stories
Use Case Modeling Part of the unified modeling language (U M L)
Agile Development – a new way of software development?
Scrum in Action.
Story Writing.
SWE 3313 Requirements.
Presentation transcript:

Jim Remsik Agile Story Carding prepared

Jim Remsik Who am I? twitter: jremsikjr Jim Remsik Big Tiger

Jim Remsik Who am I? gmail: jremsikjr Jim Remsik Big Tiger

Jim Remsik Who am I? flickr: jremsikjr Jim Remsik Big Tiger

Jim Remsik +

Jim Remsik Jacksonville Ruby Ecosystem

What is this talk about?

Jim Remsik 민첩한 ?

Jim Remsik Agile?

Jim Remsik

Jim Remsik Story Cards

Jim Remsik Story Cards are a placeholder for Conversation

Jim Remsik Story Cards capture conversations between the customer and developer

Jim Remsik Story Cards include tests that indicate successful completion of the task

Jim Remsik Story Cards are written in such a way that the customer values them

Jim Remsik

Jim Remsik An example User reads a book before falling asleep

Jim Remsik Story Template As I want So that

Jim Remsik Story Template In order to As I want

Jim Remsik Story Template In order to read a book at night As I want

Jim Remsik Story Template In order to wind down from the day As I want

Jim Remsik Story Template In order to wind down from the day As person in bed trying to read I want

Jim Remsik Story Template In order to wind down from the day As person in bed trying to read I want a light source I can control that illuminates my book

Jim Remsik Acceptance Criteria Detail the conversations between developer and customer Describe assumptions the customer may hold Are to be written by the customer and augmented by criteria added by the developer Are captured before solution is executed

Jim Remsik In order to wind down from the day As person in bed trying to read I want a light source I can control that illuminates my book Acceptance Criteria * Control does not require me to get out of bed * Light source is safe to leave on overnight * Light source is not so bright that keeps my wife up * Light source is bright enough that I don’t have to strain my eyes to see the text

Jim Remsik Acceptance Criteria What happens when I click on a link? User goes to the linked page An AJAX for is displayed User’s hard drive is formatted

Jim Remsik We have a story card, now what?

Jim Remsik Estimating Relative effort, not time Assign points or skittles or hot dogs 0, 1, 2, 4, 8

Jim Remsik Prioritization Customers can Negotiate relative priority based on Estimates of Independent, Small, Testable Stories and how much they Value the story

Jim Remsik I.N.V.E.S.T.

Jim Remsik Independent

Jim Remsik Negotiable

Jim Remsik Valuable (To the purchaser)

Jim Remsik Estimatable

Jim Remsik Common Reasons for un-estimatable stories include: Lack of domain knowledge Lack of technical knowledge The story is just too big

Jim Remsik Small

Jim Remsik The smaller the better, right? Stories can be broken down Stories can be combined

Jim Remsik Testable (Strive to automate)

Jim Remsik I.N.V.E.S.T.

Jim Remsik Pivotal Tracker