Agile Scrum Overview

of 16/16
Agile Scrum Jason Dean, CSM
  • date post

  • Category


  • view

  • download


Embed Size (px)


This is an overview of the Scrum process describing events, roles, and flow.

Transcript of Agile Scrum Overview

  • 1.Agile Scrum Jason Dean,

2. Agile Scrum What is Agile? Agile Manifesto Ethos of Agile Agile Scrum Context Scrum in a Nutshell Roles and Responsibilities Details Epics, Stories, and COS Meetings Shippable Measurement 3. Agile Manifesto Individuals andoverProcesses Interactions and Tools Working overComprehensiveSoftwareDocumentation CustomeroverContract Collaboration Negotiation RespondingoverFollowing to Changea Plan 4. Agile Development Framework Dev Approaches Practices Extreme Iterative Development Programming (XP) Test Driven ScrumDevelopment Dynamic Systems Refactoring Development Pair Programming Method (DSDM) Continuous Integration Lean User Stories Automated Testing 5. Scrum in a Nutshell Discovery SessionsDefectsStrategy Sprintdone Backlog Sprint Planning Product BacklogPotentially 1. User StoryReview (Demo) Shippablegoal 2. User Story Software 3. User Story Retrospective 4. User Story 5. User Story feedback 6. Roles and Responsibilities Defines features and release dates Product Responsible for ROI Prioritizes features by business value Owner Accepts or rejects work Ensures team is functioning and productive Removes barriers (impediments) Scrum Shields team from external interference Master Ensures the process is followed Facilitates planning, not a traditional PM Cross functional, 7 +/- 2 membersTeam Self directed Organizes itself and tasks Member Commits to Sprint and Demos to Product Owner 7. Chickens and Pigs 8. Epics, Stories, and COS Release group of functionality goingProduct Backlogout to the customer1. User Story2. User Story Epic large block of functionality3. User Story User Story bite sized piece of 4. User Story5. User Story functionality As a I want so that. As a user I want to be able to print my list of items so I canuse it as a shopping list at the store. Conditions of Satisfaction (Acceptance Criteria) Details that determine the definition of Done Theme Epics or stories that are grouped together 9. Startup and Daily Meetings Sprint Sprint PlanningProduct BacklogBacklog Review User Stories 1. User Story2. User Story Tasking and some task 3. User Story4. User Storyassignments 5. User Story Deployment considerations Daily Scrum stand up, only pigs talk, not status What did you do yesterday? What are you going to do today? What is impeding your progress? 10. Wrapup Meetings Sprint Review Demonstrate functionality to Customers/Stakeholders Retrospective (Post Mortem) What did we do well? What should we do again? What opportunities do we have to improve? 11. Sprinting No changes during a sprint No one can add or remove work but the team If necessary Team can work with Product Owner to trade insertion with something else Recommitment and Tasking Abnormal Termination If cant meet the Sprint Goal If business needs change 12. Potentially Shippable Each sprint ends with a Potentially Shippable product increment May not push out to the user, but can Done, Done, Done (testing, integration, deployment, etc) May not be cohesive i.e. Print preview but no print May take more than one Sprint to release 13. Measurement Sprint Burndown 25201510Actual 50Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 14. What did we talk about? Agile Scrum ethos, context, and overview Roles and Responsibilities Details (Stories, Meetings) [email protected] 15. References Ken Schwaber - Mike Cohn - Martin Fowler Rugby Video -