Scrum

User Stories (Def) a high-level description of a requirement (i.e. functionality) that is valuable to a user or product owner of the software product. User Role – who? Goal – what? functionality/feature Reason – why? value adding As a sales rep I want to view a list of customers so that I can pick one to contact.

Scrum Sprint Execution Product Backlog Sprint Increment An iterative and incremental agile SW development methodology. Frequent releases in short development cycles: 2 to 4-week sprints Sprint Execution Daily Scrum (“Stand-up”) Product Backlog Sprint Increment + Stakeholders Review (“Demo”) Retrospective Planning Task Board Burn Down Chart

Scrum Roles Product Owner Scrum Master Development Team client stakeholder who controls the Product Backlog Scrum Master a facilitator removes impediments, resolves issues Development Team 5-9 members Cross-functional skills “the developers” self-organizing teams complete control over organization & work processes They decide what goes in a Sprint

Scrum Meetings Sprint Planning Daily Scrum (“Stand-Up”) 8 hours - Creating the Sprint Backlog Part I: Product Owner presents the desired User Stories & the acceptance criteria for each story. Part II: Dev Team identifies tasks for each story; creates time estimates per task; finalizes the user stories they can commit to. Dev Team gets to say if there are details lacking in the user stories & cannot commit to certain stories Attended by: Product Owner, Dev Team, Scrum Master Story Points – effort estimation Fibonacci Sequence: 1, 2, 3, 5, 8, 13 T-Shirt Sizing: S, M, L, XL Daily Scrum (“Stand-Up”) 15 mins daily – Status update w/in dev team Yesterday, Today, Barriers Attended by: Development Team, Scrum Master Sprint Review (“Demo”) 4 hours - inspect & adapt the product; add new items to product backlog Attended by: Product Owner, Dev Team, Scrum Master PLUS: stakeholders Sprint Retrospective 3-hours - Process improvement lessons learned, successes & failure Attended by: Scrum Master, Dev Team

Fibonacci Sequence The sum of the 2 numbers to the left With Fibonacci, you will never see half of any number! It forces you to think! 0 1 1 2 3 5 8 13 21 34 User Story A 0 1 1 2 3 5 8 13 21 34 Assume: User Story B is about half the difficulty of User Story A. Is this user story a little more difficult than half (i.e. 5)?, or Is it a little less difficult than half (i.e. 3)?

Epic - a large Backlog item Scrum Meetings Backlog Refinement (“Grooming”) Refining the next items on the product backlog to prepare for the next sprint(s). It includes: Clarifying backlog items Reducing Epics into smaller items Determining dependencies Task can be done during a Sprint Planning Meeting but many prefer to do it separate; some do this as a separate meeting toward the end of a sprint. Epic - a large Backlog item

Scrum Artifacts Product Backlog Increment Task Board Sprint Backlog Product Owner Prioritized List of Product Backlog Items (PBIs) PBIs are written as user stories and will have: Acceptance Criteria Story Points/Effort Estimated – by dev team Increment Potentially shippable product Product Owner decides when to release Task Board For each item in the Sprint Backlog, list & classify all tasks: To Do, In Progress, Done Sprint Backlog Development Team List of PBIs committed to Includes the Tasks for each PBI Sprint Burndown Chart Shows amount of work remaining in one sprint

User Story To Do In Progress Done Task Board User Story To Do In Progress Done As a Sales Rep, I want to view a list of customers so that I can pick one to contact. As a Sales Rep, I need to maintain client data & locations so that we can properly determine their product needs based on their profile. Design the UIs Modify the Domain CD Modify the Use Case Diagram Test the UIs Create a sketch of the UIs Create a sketch of the UIs Modify the Domain CD Modify the Use Case Diagram Test the UIs Design the UIs

Burndown Chart

Story Map Useful when we have so many user stories and we need to understand how to progress through them.