1. Copyright © 2015-2016 Curt Hill Scrum Software Development Paradigms What is a Scrum?

2. Introduction An agile development process A process framework to manage software development It is a management technique –XP is characterized as an engineering technique –The Scrum and XP are somewhat compatible Copyright © 2015-2016 Curt Hill

3. Scrum Teams Scrum teams are defined with: –Roles –Events –Artifacts –Rules What is scrum named after? Copyright © 2015-2016 Curt Hill

4. Original Scrum Copyright © 2015-2016 Curt Hill

5. Scrum Team Three distinct roles: –Product Owner –Development Team –Scrum Master Teams are self-organizing Should have all the skills needed to accomplish their goal Products are produced incrementally Each increment should produce a workable product Copyright © 2015-2016 Curt Hill

6. Terminology Product Backlog –Prioritized list of the features needed in the product Sprint –A time period that sees the production of a new or improved workable product –Implements a Sprint Goal determined by a Sprint meeting –Typically less than a month Sprint Backlog –Those features intended to be implemented in this sprint Copyright © 2015-2016 Curt Hill

7. Product Owner Creates and manages the Product Backlog –The only one to do so Sole interface with the business –Should be a business expert, not necessarily a development expert Makes sure the Development team understands the items in the backlog Copyright © 2015-2016 Curt Hill

8. Development Team Do the work of development Organize and manage their own work –Self organizing Cross functional –All the skills necessary must be present in the team No: –Sub-teams –Titles –No ranking in importance Copyright © 2015-2016 Curt Hill

9. Scrum Master Interface between the team and nearly everyone else Insulates the team from outside pressures Assists the Product Owner in managing the Backlog and facilitating events Assists the team in a coaching and mentoring fashion Not a project manager Copyright © 2015-2016 Curt Hill

10. Events The Sprint Sprint Planning –A meeting that determines what can be delivered and this will be done Daily Scrum –A short meeting to synchronize activities Sprint Review –Final meeting in the Sprint to determine what has and has not been done Copyright © 2015-2016 Curt Hill

11. Process The team moves the highest priority items from the product backlot creating the sprint backlog –Number determined by time estimates –This is the sprint planning event The sprint begins –Continues for a fixed amount of days –There is a daily scrun to inform of status The sprint review concludes and determines what is done Copyright © 2015-2016 Curt Hill

12. Task Board Copyright © 2015-2016 Curt Hill

13. Process Again The sprint review determines the contents of the demo –Things must be done to be demoed The demo is a functional product –The product owner may choose to release this or not Copyright © 2015-2016 Curt Hill

14. Finally One of the more popular agile methodologies today Like many agile schemes it is incremental or evolutionary Copyright © 2015-2016 Curt Hill