This document provides an overview of Scrum and its key concepts. It introduces Scrum as an Agile methodology used to manage product development. The document outlines the Scrum process including sprints, daily stand-ups, sprint planning and reviews. It describes Scrum roles like Product Owner and Scrum Master and artifacts like the product and sprint backlogs. Charts are presented to track work like burndowns and velocity. The document aims to explain how Scrum can help teams adapt to change and deliver working software frequently.

1. Presented by:
Qasim Mehmood
Portals & Collaboration Technical Manager
Qmehmood@hotmail.com
Twitter: @Qamehmood

2. Presenter Introduction
Qasim Mehmood

3. Agenda
 Agile and Scrum
 Business Problem
 Scrum Process
 Scrum Team
 Artifacts
 Product Backlog
 Sprint Backlog

4. Scrum and Agile
Agile is the ability to create and response to change.
Scrum is the most popular of the Agile methods.
• Absorb Change
• New Requirements
• Deliver software periodically

5. Problem - Why Scrum?
‣ Releases take too long
‣ Stabilization takes too long
‣ Changes are hard to make
‣ Quality is falling

6. How does Scrum help to solve it?
• Traditional development methodologies rely
on documents to record and pass on
knowledge from one specialist to the next.
• Feedback cycles are too long or even
nonexistent.
• Scrum Provides Platform for people to work
together effectively
• Makes visible every problem.

7. Scrum Methodology
Planning Sprints
Discovery Development Sprint Cycle
Session
Sprint
Release
Planning Sprint Daily Sprint
Planning Scrum Review
Retrospective
Product Backlog
Sprint Backlog Production-Ready Features

8. Starting Scrum
The best thing you can do is hire an experienced coach. you need a Scrum
team. Product Owner, Scrum Master and team members.
Then follow this sequence of steps:
• 1. Train the Scrum Team
• 2. Establish the vision
• 3. Write user stories to form the product backlog
• 4. Order the backlog items by business value
• 5. Size the backlog items
• 6. Re-order the backlog, as necessary, by additional factors
• 7. Create the initial release plan
• 8. Plan the first sprint
• 9. Start sprinting

9. Scrum Methodology
Release planning
Product Sprint
Vision
Backlog Backlog
Planning
Deployment Development
Sprints
Build Unit Testing
Shipable Quality
Assurance
Product

10. Sprint Mechanism
User stories
Acceptance criteria
Sprint Business rules
Planning Development
Work Unit Testing
Quality Assurance
Build
Retrospec Deployments
Work Daily
tive
Scrum
Meeting
Sprint
Review Value to customer
Code is complete
Testing is complete
Documentation is
complete

11. Quick Process Overview

12. Scrum Roles
Product Owner Scrum Master The Team Other stakeholders
• Manages Product • Responsible for • Architect and • Customers
Backlog facilitating process develop code as per • Vendors
the backlog items
• Makes decisions on • Manage
Sprint Scope communication
between the Teams • Perform Unit Testing
• Provides details on
features including • Produce project • Perform Quality
acceptance criteria reporting to keep Assurance
track of project
• Decides on release performance • Merge Code and
date and content ensure deploy-
• Assists Product
ability
• Accepts the Owner in leveraging
deliverables Scrum & managing
the product backlog

13. Meetings
• Release Planning: the product owner, Scrum team
meet to plan and schedule the releases for sprints
• Sprint planning: the team meets with the product
owner to choose a set of work to deliver during a sprint
• Daily scrum: the team meets each day to share
struggles and progress
• Sprint reviews: the team demonstrates to the product
owner what’s completed during the sprint
• Sprint retrospectives: the team looks for ways to
improve the product and the process.

14. Sprint Planning Meeting
• It is a negotiation between the team and the
product owner about what the team will do
during the next sprint.
• The product owner and all team members agree
on a set of sprint goals, which is used to
determine which product backlog items to
commit from the uncommitted backlog to the
sprint.
• This portion of the sprint planning meeting is
time-boxed to four hours.

15. Daily Scrum
• The meeting starts precisely on time
• All are welcome, but normally only the core roles speak
• The meeting length is set (time boxed) to 15 minutes
• The meeting should happen at the same location and same time
every day
• During the meeting, each team member answers three questions:
– What have you done since yesterday?
– What are you planning to do today?
– Any impediments/stumbling blocks?
• It is the role of the Scrum Master to facilitate resolution of these
impediments, although the resolution should occur outside the
Daily Scrum itself to keep it under 15 minutes.

16. Sprint Review Meeting
• At the end of each sprint a sprint review meeting
is held.
• Scrum team shows what they have accomplished
during the sprint. Typically this takes the form of
a demo of the new features
• Participants in the sprint review typically include
the Product Owner, the Scrum team and the
customers
• Progress is assessed against the sprint goal
determined during the Sprint planning meeting

17. Sprint Retrospective Meeting
• The team and Scrum Master meet to discuss
what went well and what to improve in the
next sprint. The product owner does not
attend this meeting.
• The sprint retrospective should be time-boxed
to three hours.

18. Artifacts
• Product backlog: prioritized list of desired project
outcomes/features
• Sprint backlog: set of work from the product backlog
that the team agrees to complete in a sprint, broken
into tasks
• Impediment backlog: List of issues that are preventing
the team from progressing or improving
• Burndown charts: at-a-glance look at the work
remaining (can have two charts: one for the sprint and
one for the overall project)
• Velocity chart: To track the performance of each sprint

19. Release Burndown

20. Sprint Burndown

21. Velocity Chart

22. Tools and Templates
• TFS (Team Foundation System)
• Online Tool (http://www.rallydev.com)
• Product Backlog
• Sprint Backlog
• Status Reports

23. Q&A

24. Thanks