Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Agile Scrum Overview

•
•
Jason Dean
Jason Dean

The document discusses Agile Scrum, including: - The Agile Manifesto principles of prioritizing individuals, interactions, working software, and responding to change over processes, tools, documentation, and following a plan. - Scrum roles like Product Owner, Scrum Master, and cross-functional team members. - Scrum ceremonies like sprint planning, daily stand-ups, sprint reviews, and retrospectives. - User stories, epics, and conditions of satisfaction to define work in the product backlog. - The goal of each sprint is to produce potentially shippable increments of functionality.

1 of 16
Download to read offline
Agile Scrum Jason Dean, CSM AgileScrumPro.org
Agile Scrum Overview
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
Agile Manifesto Individuals and over Processes Interactions and Tools Working over Comprehensive Software Documentation Customer over Contract Collaboration Negotiation Responding over Following to Change a Plan
Agile – Development Framework • Dev Approaches • Practices – Extreme – Iterative Development Programming (XP) – Test Driven – Scrum Development – Dynamic Systems – Refactoring Development – Pair Programming Method (DSDM) – Continuous Integration – Lean – User Stories – Automated Testing
Scrum in a Nutshell Discovery Sessions Defects Strategy Sprint done Backlog Sprint Planning Product Backlog Potentially 1. User Story Review (Demo) Shippable goal 2. User Story Software 3. User Story Retrospective 4. User Story 5. User Story feedback
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 members Team  Self directed  Organizes itself and tasks Member  Commits to Sprint and Demos to Product Owner
Chickens and Pigs
Epics, Stories, and COS • Release – group of functionality going Product Backlog out to the customer 1. User Story 2. User Story • Epic – large block of functionality 3. User Story • User Story – bite sized piece of 4. User Story 5. User Story functionality – As a <user type> I want <some functionality> so that <reason>. – As a user I want to be able to print my list of items so I can use 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
Startup and Daily Meetings Sprint • Sprint Planning Product Backlog Backlog – Review User Stories 1. User Story 2. User Story – Tasking and some task 3. User Story 4. User Story assignments 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?
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?
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 can’t meet the Sprint Goal – If business needs change
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
Measurement Sprint Burndown 25 20 15 10 Actual 5 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
What did we talk about? • Agile Scrum ethos, context, and overview • Roles and Responsibilities • Details (Stories, Meetings) • Measurement AgileScrumPro.org jason@jasonleedean.com
References • Ken Schwaber - ControlChaos.com • Mike Cohn - MountainGoatSoftware.com • Martin Fowler – MartinFowler.com • ScrumAlliance.com • ImplementingScrum.com • AgileManifesto.org • Rugby Video - http://www.youtube.com/watch?v=IEQyCcageGg

More Related Content

Agile Scrum Overview

  • 1. Agile Scrum Jason Dean, CSM AgileScrumPro.org
  • 3. 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
  • 4. Agile Manifesto Individuals and over Processes Interactions and Tools Working over Comprehensive Software Documentation Customer over Contract Collaboration Negotiation Responding over Following to Change a Plan
  • 5. Agile – Development Framework • Dev Approaches • Practices – Extreme – Iterative Development Programming (XP) – Test Driven – Scrum Development – Dynamic Systems – Refactoring Development – Pair Programming Method (DSDM) – Continuous Integration – Lean – User Stories – Automated Testing
  • 6. Scrum in a Nutshell Discovery Sessions Defects Strategy Sprint done Backlog Sprint Planning Product Backlog Potentially 1. User Story Review (Demo) Shippable goal 2. User Story Software 3. User Story Retrospective 4. User Story 5. User Story feedback
  • 7. 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 members Team  Self directed  Organizes itself and tasks Member  Commits to Sprint and Demos to Product Owner
  • 9. Epics, Stories, and COS • Release – group of functionality going Product Backlog out to the customer 1. User Story 2. User Story • Epic – large block of functionality 3. User Story • User Story – bite sized piece of 4. User Story 5. User Story functionality – As a <user type> I want <some functionality> so that <reason>. – As a user I want to be able to print my list of items so I can use 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
  • 10. Startup and Daily Meetings Sprint • Sprint Planning Product Backlog Backlog – Review User Stories 1. User Story 2. User Story – Tasking and some task 3. User Story 4. User Story assignments 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?
  • 11. 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?
  • 12. 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 can’t meet the Sprint Goal – If business needs change
  • 13. 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
  • 14. Measurement Sprint Burndown 25 20 15 10 Actual 5 0 Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10
  • 15. What did we talk about? • Agile Scrum ethos, context, and overview • Roles and Responsibilities • Details (Stories, Meetings) • Measurement AgileScrumPro.org jason@jasonleedean.com
  • 16. References • Ken Schwaber - ControlChaos.com • Mike Cohn - MountainGoatSoftware.com • Martin Fowler – MartinFowler.com • ScrumAlliance.com • ImplementingScrum.com • AgileManifesto.org • Rugby Video - http://www.youtube.com/watch?v=IEQyCcageGg