AgileCamp Presents: Scrum

Good luck in your presentation!

• This slide deck has been shared by AgileCamp Kit under the Creative Commons Attribution 4.0 International License

• The views expressed in this slide deck are of the AgileCamp Kit team and do not necessarily reflect the views of their employer, Return Path.

• You may remove this slide for your presentation, but please attribute AgileCamp Kit in some way in your presentation.

Agile Manifesto

We are uncovering better ways of developing software by doing it and helping others do it.

Through this work we have come to value:

• Individuals and interactions over processes and tools• Working software over comprehensive documentation• Customer collaboration over contract negotiation• Responding to change over following a plan

That is, while there is value in the items on the right, we value the items on the left more.

Twelve Principles of Agile Software

Insert image of 12 principles

Principles of Agile Software

1) Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

2) Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

Principles of Agile Software

8) Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

10) Simplicity--the art of maximizing the amount of work not done--is essential.

12) At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior.

What is Scrum?

Insert image of rugby scrum

Scrum Framework

Agile Roles• Scrum Masters

• Product Owners

• Development Teams

• Stakeholders

Scrum MasterDuties include:

• Servant Leader• Monitoring & Tracking• Reporting & Communicating• Process Check Master• Quality Master• Resolve Impediments• Resolve Conflicts• Shield the Team• Performance Feedback

Product Owner (Product Manager)Duties Include:

• Facilitate Collaboration: colocation with team, backlog grooming and other meetings

• Understand the Market: create personas, seek feedback, conduct product discovery

• Features and UX: user stories, wireframes, and sketches, product canvas

• Value: understand business model including revenue sources, costs, and channels

• Ownership: responsible for vision and roadmap

Scrum Team

Insert image of Scrum team

Sprint Ceremonies

Sprint Planning - At the start of each sprint

Sprint Ceremonies

Daily Standup - 15 minutes each workday

Turning Mountains Into GravelBacklog Grooming Meeting- Review of product backlog

Epics Stories Tasks

Sprint CeremoniesSprint Review - Demo of completed stories

Sprint Ceremonies

Sprint Retrospective - Finding ways to improve

Backlogs

Artifacts - Product Backlog

Sprint BacklogStories (aka Cards) move from Product Backlog to the Sprint

Backlog.

Release Planning

Reporting - Burndown Chart

Reporting - Velocity Chart

Reporting - Cumulative Flow Chart

SummaryProduct Owners - Determine what to build in the next 30 days or less.

Development Teams - Build what is needed in 30 days or less, and then demonstrate what they have built. Based on this demonstration, the Product Owner determines what to build next.

Scrum Masters - They ensure this process happens as smoothly as possible, and continually help improve the process, the team and the product being created.

Questions?

Resources

Agile Alliance (http://www.agilealliance.org)● Certified Scrum Master (CSM)● Certified Scrum Product Owner) CSPO● Certified Scrum Developer (CSD)● Certified Scrum Professional (CSP)

Books:Agile Project Management For Dummies by Mark C. LaytonAgile Project Management for Beginners: Mastering the Basics with Scrum by Bryan MathisEssential Scrum: A Practical Guide to the Most Popular Agile Process by Kenneth S. Rubin

Thank You for attending AgileCamp!