Scrum for Your Lives - An Agile Overview

Learn the basics and how to put Scrum into practice in your company. This workshop runs through:
- Why Agile?
- Terms and roles
- How to create a backlog and user stories
- Estimating and prioritizing
- The Sprint - what goes into making a successful development sprint

Transcript

1. regan davis scrum for your lives an introduction to agile
2. regan davis product leader from chicago, il BACKGROUND Sr. Director of Product @ SpotHero EIR @ 1871 Advisor, Coach regandavis.com VP of Product @ Jellyvision VP of Product @ info.com
3. agile & scrum overview estimating workshop story mapping workshop live sprint play-through today’s agenda regandavis.com
4. why agile? the backlog estimating the sprint topics
5. regandavis.com everything is awesome
6. regandavis.com waterfall • Locked in up-front • Teams spend months designing, architecting, developing • Right before completion, pieces are put together and tested
7. regandavis.com agile manifesto Individuals and interactions Working software Customer collaboration Responding to change processes and tools comprehensive documentation contract negotiation following a plan -over- -over- -over- -over-
8. regandavis.com scrum Good for teams working toward milestones and deliverables Timeframe and effort based kanban Good for teams with small tasks and tight turnaround 
 (Ops, Analytics, e.g.) Issue count based *
9. regandavis.com “The goal is not to do as many tasks as possible. The goal is to have as great an impact by doing as few tasks as possible.
10. (credit: Lean Startup) regandavis.com
11. regandavis.com learn & iterate (credit: ”The Founder” movie clip) our goal is to
12. Josh Miller CEO, The Browser Company regandavis.com releasing weekly creating delightful experiences by
13. regandavis.com
14. regandavis.com the backlog
15. regandavis.com backlog smaller, broken down issues to work on fi rst large, generic ones further away an ordered list of everything that might be needed for the product
16. regandavis.com there can be only one
17. someone else will. regandavis.com if we don’t prioritize,
19. regandavis.com user stories description of a software feature from the perspective of an end user. As a ______, I want to ______ so that _____
20. regandavis.com stories require INVESTment • I • N • V • E • S • T ndependent egotiable ertical stimated mall ested
21. regandavis.com what’s in a user story? Summary (as a ___, I want to ___…) acceptance criteria mockups (usually)
22. regandavis.com As a customer, I want to add items to my shopping cart, so that I can easily keep track of what I want to buy. • The shopping cart icon is always visible on the screen. • Customers can add items to their cart by clicking on the “Add to Cart” button. • The item added to the cart should be displayed along with its price and quantity. • Customers can view their cart contents by clicking on the shopping cart icon. • The cart should update automatically when items are added or removed. Acceptance Critera
23. regandavis.com As a customer, I want to add items to my shopping cart, so that I can easily keep track of what I want to buy. As a customer, 
 I want to see the shopping cart icon on the screen, 
 so that I can easily fi nd it and access my cart. As a customer, 
 I want to add items on the site into my shopping cart, 
 so that I can fi nd them later As a customer, 
 I want to view my cart contents, 
 so that I can see what items I have added to my cart. As a customer, 
 I want the cart to update automatically when I add or remove items, 
 so that I can see the most up-to- date information.
24. regandavis.com As a customer, 
 I want to view my cart contents, 
 so that I can see what items I have added to my cart. • Customers can view their cart contents by clicking on the menu item named ‘Shopping Cart’ • The shopping cart loads a new page, with any previously added items for that customer. • Each item in the cart should be displayed along with its price and quantity. • The sub-total sums up the price of each item. • There is a ‘Check Out’ button to begin the payment process. Acceptance Criteria
25. backlog regandavis.com As a customer, 
 I want to see the shopping cart icon on the screen, 
 so that I can easily fi nd it and access my cart. As a customer, 
 I want to add items on the site into my shopping cart, 
 so that I can fi nd them later As a customer, 
 I want to view my cart contents, 
 so that I can see what items I have added to my cart. As a customer, 
 I want the cart to update automatically when I add or 

26. backlog regandavis.com Story Title Story Points Priority Add items to cart 5 1 View cart contents 3 2 Show cart icon 2 3 Auto-update cart 8 4
27. regandavis.com estimating
28. humans are terrible estimators regandavis.com
29. regandavis.com
30. regandavis.com
31. estimate effort regandavis.com instead of estimating hours, • no assumption of ‘perfect’ accuracy • fewer options, like simple numbers or t-shirt sizes • easier to compare to stuff you've done before
32. developers only regandavis.com • all developers should agree on the estimates • effort includes all the steps to reach "done" • Development • Local Testing • Code Review • Quality Assurance • User Acceptance Testing
33. regandavis.com story points 1, 2, 3, 5, 8, 13, 20 • rough fi bonnaci scale for estimating effort • numbers get wider apart the more effort something takes (to accept that we are less certain) • big stories get broken down into smaller stories
34. regandavis.com the sprint
35. regandavis.com sprint planning What can be delivered this sprint? Product Owner discusses goal and backlog items that would achieve it How will we get it done? Development team forecasts what it can do in the upcoming sprint a max 15-minute daily meeting Three questions to answer: • What did I do yesterday? • What will I do today? • Do I see any blockers? daily standup meeting to kick off a new sprint backlog refinement estimate stories ahead of sprint planning
36. regandavis.com development work
37. includes dev team, product owner, and stakeholders • demo the work that is done, answer questions • PO discusses current backlog, perhaps rough projections • entire group collaborates on most valuable to do next regandavis.com sprint review before next Sprint Planning Meant for team to provide self feedback and establish process improvements retrospective informal demo at end of each sprint
38. so many meetings! regandavis.com focus on talking with each other during development, not about the number of meetings you have. individuals & interactions -over- processes & tools
39. questions? AFTER THE BREAK regandavis.com estimating workshop story mapping workshop live sprint play-through
40. regandavis.com break time