Introduction to Scrum

Introduction to Scrum

Richie Rump@Jorriss

www.jorriss.net

Who is this dude?

What is Scrum

• It’s a framework to get things done.• Designed for complex projects.• Iterative process.• Shippable software, frequently.• Handles frequent changes.

Why Scrum?

• Embrace Change• Frequent Delivery of Software• Better Risk Management• Greater Team Involvement• Better Software Quality

Waterfall vs Agile

Source: http://www.mountaingoatsoftware.com/blog/agile-succeeds-three-times-more-often-than-waterfall

Scrum Values

• Individuals and interactions over processes and tools

• Completed functionality over comprehensive documentation

• Customer collaboration over contract negotiation

• Responding to change over following a plan

Scrum Roles

• Product Owner• Dev Team• Scrum Master

Scrum Ceremonies

• Sprint Planning• Daily Scrum (Standup)• Sprint Review• Sprint Retrospective

Scrum Artifacts

• Product Backlog• Sprint Backlog• Burndown Chart

Product Owner

• One person• Accountable for product• Owns Product Backlog• Responsible for ordering items in Product

Backlog• Responsible for clearly expressing

Product Backlog items.

Dev Team

• Professionals that “Do the work”.• Self-organizing – Selects what to work

and choses how to do it.• Cross-functional – the team has all of the

skills necessary to deliver an increment.• Do not contain sub-teams.• Accountability is shared

Scrum Master

• Ensures Scrum is understood and enacted.

• Facilitates events as needed.• Removes impediments and blockers.• Servant leader.• Serves the Product Owner, Dev Team and

the Organization.

Sprint

• Less than 30 days• Most are two weeks long• Has a goal• No changes are made that would affect

the goal• Scope may be clarified during the Sprint

Product Backlog

Sprint Planning

• What will be done this Sprint?• How will the chosen work get done?• Creates a Sprint Backlog and a Sprint Goal.• Forecast the work for the Sprint.• At the end we will have created shippable

software.• Define “done”.

Sprint Backlog

Daily Scrum

• Fifteen minute meeting• Held every day• What has been accomplished since the last

meeting? • What will be done before the next

meeting? • What obstacles are in the way? • Inspect and adapt the Sprint Backlog

Sprint Burndown

Sprint Review

• Time boxed; one hour per week of sprint.• Involves the Scrum Team and

stakeholders.• Demos the work done.• Records feedback and places in Product

Backlog

Sprint Retrospective

• Scrum team only; no outsiders.• Inspect how the sprint went with regards

to people, process and tools.• Creates a plan for implementing

improvements.

Scrum Process

Photo credit: http://sambit-daspatnaik.blogspot.com/2012/03/importance-of-project-management.html

Reference

• Scrum Guide : http://www.scrum.org/Scrum-Guides

• Scrum Primer: http://scrumfoundation.com/library

• Scrum Fundamentals on PluralSight.

Thank You!!

Richie Rump@Jorrisshttp://jorriss.nethttp://slideshare.net/jorriss http://dotnetmiami.com