©2011 Improving Enterprises, Inc. Breaking down the Epic User Story

©2011 Improving Enterprises, Inc. Dilbert on the User Story

©2011 Improving Enterprises, Inc. Why are Epics important? When do we break them down? Who does it? How do we do it?

©2011 Improving Enterprises, Inc. Why are Epics important?

©2011 Improving Enterprises, Inc. Business Case Financing Scope & Approach Contracts Initial Release Plan Assemble Team Sprint Planning 1 day Acceptance Defined Team commits Tasks created Product Owner establishes vision and prioritizes Product Backlog Sprint 1 to 4 weeks Team (BA, QA, Dev, etc.) creates and estimates Sprint Backlog (tasks) Potentially Shippable Daily Scrum < 15 minutes Burn down Review 1/2 day Sprint Retrospective 1/2 day Burn up velocity Scrum

©2011 Improving Enterprises, Inc. A list of goals, features, and items that a product must provide in order to meet a business need. The Product Owner creates and maintains this list, and from it all Sprints derive their work. User Stories are popular product backlog items. Product Backlog The essential planning tool

©2011 Improving Enterprises, Inc. Independent Negotiable Valuable Estimable Small Testable Independent Negotiable Valuable Estimable Small Testable Good Stories Are...

©2011 Improving Enterprises, Inc. The Epic User Story

©2011 Improving Enterprises, Inc. How much is there? Total: 180 Total features in P B/L features per interval of time (velocity) length of interval

©2011 Improving Enterprises, Inc. How much is there?

©2011 Improving Enterprises, Inc. Why are Epics important? I can forecast… I can start sooner…

©2011 Improving Enterprises, Inc. Why breakdown at all?

©2011 Improving Enterprises, Inc. Independent Negotiable Valuable Estimable Small Testable Independent Negotiable Valuable Estimable Small Testable Good Stories Are...

©2011 Improving Enterprises, Inc. Good to great!

©2011 Improving Enterprises, Inc. Independent Negotiable Valuable Estimable Small Testable Independent Negotiable Valuable Estimable Small Testable Sprint 1 to 4 weeks Fits nicely into one sprint…

©2011 Improving Enterprises, Inc. In today’s session… EpicSmall I wonder how…

©2011 Improving Enterprises, Inc. When do we do it?

©2011 Improving Enterprises, Inc. Timing – in between… Initial Product Backlog Product Backlog Grooming Sprint Planning Sprint Execution Grooming Session Breakdown Sprint Execution Next Sprint Planning Sizing

©2011 Improving Enterprises, Inc. Timing – as you go… Initial Product Backlog Product Backlog Grooming Sprint Planning Sprint Execution Next Sprint Planning Sprint Execution Breakdown & Sizing

©2011 Improving Enterprises, Inc. Who does it?

©2011 Improving Enterprises, Inc. Sponsor ScrumMasterProduct Owner Stakeholders Team Who breaks down the Epics?

©2011 Improving Enterprises, Inc. Sponsor ScrumMasterProduct Owner Stakeholders Team Who breaks down the Epics?

©2011 Improving Enterprises, Inc. How do we do it?

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 1.Workflow Steps 2.Business Rules 3.Major Effort 4.Simple / Complex 5.Variations in Data 6.Defer non-functionals 7.Operations (CRUD) 8.Spikes (research) Original List ©2009 Humanizing Work, LLC

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 1.Workflow Steps

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 2. Business Rules

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 3. Major Effort

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 4. Simple / Complex

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 5. Variations in data

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 6. Defer non-functionals

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 7. Operations (CRUD)

©2011 Improving Enterprises, Inc. Guidelines for breaking down EpicSmall 8. Spikes  (research)  Be careful with this one

©2011 Improving Enterprises, Inc. Here they are again EpicSmall 1.Workflow Steps 2.Business Rules 3.Major Effort 4.Simple / Complex 5.Variations in Data 6.Defer non-functionals 7.Operations (CRUD) 8.Spikes (research) Original List ©2009 Humanizing Work, LLC

©2011 Improving Enterprises, Inc. Why are Epics important? When do we break them down? Who does it? How do we do it?

©2011 Improving Enterprises, Inc. Break them down in between. All responsible, PO accountable. Eight guidelines. Break them down as we go. Epics help us forecast. Epics get us started sooner.

©2011 Improving Enterprises, Inc. Plans are nothing. Planning is everything. -Dwight D. Eisenhower

©2011 Improving Enterprises, Inc. All Done!

©2011 Improving Enterprises, Inc. Questions? Hemant Elhence

©2011 Improving Enterprises, Inc. Synerzip in a Nut-shell 1. 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 2. 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 3. Actually reduces risk of development/delivery Experienced team - uses appropriate level of engineering discipline Practices Agile development – responsive, yet disciplined 4. Reduces cost – dual-shore team, 50% cost advantage 5. Offers long term flexibility – allows (facilitates) taking offshore team captive – aka “BOT” option

©2011 Improving Enterprises, Inc. Our Clients

©2011 Improving Enterprises, Inc Call Us for a Free Consultation! Hemant Elhence Thanks!