Analysis in Agile: It’s More Than Just User Stories Kent Webinar Series 2015

©Kent McDonald Webinar Series 2015 Writing user stories… In order to share my experiences (and get into Agile2015 for free) As Sam the submitter I want to submit a session proposal In order to share my experiences (and get into Agile2015 for free) As Sam the submitter I want to submit a session proposal …is not the whole story!

©Kent McDonald Webinar Series 2015 What does analysis look like in Agile?

©Kent McDonald Webinar Series 2015 Describe what to build using models & stories How to determine what is just enough Analysis in Agile Use value to determine the right thing to build

©Kent McDonald Webinar Series 2015 Typical Description of What to Build This has its issues…

©Kent McDonald Webinar Series 2015 Exercise Do you have a complete solution?

©Kent McDonald Webinar Series 2015 Exercise Is the backlog more like a wish list?

©Kent McDonald Webinar Series 2015 Start with value, then identify stories

©Kent McDonald Webinar Series 2015 Use Goals & Objectives to define value Goal: Increase our ability to handle expected increase in claims Goal: Increase our ability to handle expected increase in claims Objective: Reduce paper claims from 1000 per week to 500 per week by 12/31 Objective: Reduce paper claims from 1000 per week to 500 per week by 12/31

©Kent McDonald Webinar Series 2015 Identify Assumptions Single doctor offices have internet access Majority of paper claims come from single doctor offices Single doctor offices do not have medical billing systems Staff at a single doctor’s office would submit claims via website

©Kent McDonald Webinar Series 2015 Identify stories to validate assumptions & meet objectives Majority of paper claims come from single doctor offices In order to identify the main sources of paper claims As Carol the Claims Mgr I need … In order to identify the main sources of paper claims As Carol the Claims Mgr I need … In order to determine whether single doctors offices would submit claims As Peter the Provider Relations Manager I need … In order to determine whether single doctors offices would submit claims As Peter the Provider Relations Manager I need … Staff at a single doctor’s office would submit claims via website

©Kent McDonald Webinar Series 2015 Impact Mapping © Gojko Adzic 2012http://impactmapping.org

©Kent McDonald Webinar Series 2015 Describe what to build using models & stories How to determine what is just enough Analysis in Agile Use value to determine the right thing to build

©Kent McDonald Webinar Series 2015 Understand the solution with models

©Kent McDonald Webinar Series 2015 Use models to identify stories In order to provide feedback to submitters As Reed I need to submit a review of a session In order to provide feedback to submitters As Reed I need to submit a review of a session As Reed I can add a review to a session So that I can provide feedback to Sam As Reed I can add a review to a session So that I can provide feedback to Sam As Sam I can view reviews on my session So that I can get feedback on my session As Sam I can view reviews on my session So that I can get feedback on my session As Reed I can edit my review So that I can react to changes Sam made to his submission As Reed I can edit my review So that I can react to changes Sam made to his submission

©Kent McDonald Webinar Series 2015 Use Models to Identify Stories

©Kent McDonald Webinar Series 2015 Stories represent changes needed In order to guide submitter track selection As Peter Program Chair I want to organize tracks into themes In order to guide submitter track selection As Peter Program Chair I want to organize tracks into themes

©Kent McDonald Webinar Series 2015 The delivery team sets me straight

©Kent McDonald Webinar Series 2015 And comes up with a better solution

©Kent McDonald Webinar Series 2015 Models describe stories As Reed I can add a review to a session So that I can provide feedback to Sam As Reed I can add a review to a session So that I can provide feedback to Sam

©Kent McDonald Webinar Series 2015 Acceptance Criteria describe stories One line summary and advice to presenter are required. One line summary limited to 95 characters. Choices for “This presentation should be included in the program” are agree, neutral, and disagree. As Reed I can add a review to a session So that I can provide feedback to Sam As Reed I can add a review to a session So that I can provide feedback to Sam

©Kent McDonald Webinar Series 2015 Examples describe stories

©Kent McDonald Webinar Series 2015 How many stories can you find?

©Kent McDonald Webinar Series 2015 Describe what to build using models & stories How to determine what is just enough Analysis in Agile Use value to determine the right thing to build

©Kent McDonald Webinar Series 2015 Do only what you actually need to do For illustrative purposes only No models were harmed used building the submission system

©Kent McDonald Webinar Series 2015 Exercise Definition of Ready

©Kent McDonald Webinar Series 2015 Team discusses and agrees

©Kent McDonald Webinar Series 2015 Possible things to include Interaction Diagrams Prototypes Wireframes Sample Data Testable examples Acceptance Criteria State Diagrams Small Story UX Test Approvals Dependency identified Stakeholder identified Definition of Ready Use case

©Kent McDonald Webinar Series 2015 Exercise Analyze when you need to, not before

©Kent McDonald Webinar Series 2015 Visualize Discovery and Delivery Iteration Planning Discovery Board Delivery Board

©Kent McDonald Webinar Series 2015 Discovery Board Defn of Ready Story Feature Include:  Story  Acceptance Criteria Include:  Story  Acceptance Criteria Story Include:  Story  Acceptance Criteria  Size Include:  Story  Acceptance Criteria  Size Include:  Story  Acceptance Criteria  Size  Mockup  Dependencies  Stakeholder list  Examples Include:  Story  Acceptance Criteria  Size  Mockup  Dependencies  Stakeholder list  Examples

©Kent McDonald Webinar Series 2015 What did you find when I go to work this afternoon, I’m going to try… #baot #valuemgmt

©Kent McDonald Webinar Series Hemant Elhence

©Kent McDonald Webinar Series 2015 Synerzip in a Nutshell Software product development partner for small/mid-sized technology companies –Exclusive focus on small/mid-sized technology companies, typically venture-backed companies in growth phase –By definition, all Synerzip work is the IP of its respective clients –Deep experience in full SDLC – design, dev, QA/testing, deployment Dedicated team of high caliber software professionals for each client –Seamlessly extends client’s local team, offering full transparency –Stable teams with very low turn-over –NOT just “staff augmentation”, but provide full mgmt support Actually reduces risk of development/delivery –Experienced team - uses appropriate level of engineering discipline –Practices Agile development – responsive, yet disciplined Reduces cost – dual-shore team, 50% cost advantage Offers long term flexibility – allows (facilitates) taking offshore team captive – aka “BOT” option

©Kent McDonald Webinar Series 2015 Our Clients

©Kent McDonald Webinar Series 2015 Next Webinar Technical Track: Lean With MEAN Complimentary Webinar: Wednesday, May 20, 11:00am CST Presented by: Mayuresh Pradke Technology Enthusiast & Entrepreneur Synerzip

©Kent McDonald Webinar Series 2015 Call for a Free Consultation! Hemant Elhence linkedin.com/company/synerzip facebook.com/Synerzip

©Kent McDonald Webinar Series 2015 Questions?

©Kent McDonald Webinar Series 2015 If you remember nothing else… 1. Use value to determine the right thing to build 2.Use models, acceptance criteria & examples to describe the solution 3.Collaborate to figure out what is just enough

©Kent McDonald Webinar Series 2015 Stay in Touch Kent Slides available from: