Scrum MethodologyPresented by:Qasim MehmoodPortals & Collaboration Technical ManagerQmehmood@hotmail.com

Twitter: @Qamehmood

Presenter Introduction

Qasim MehmoodTechnical Practice Manager, CSM, Portals & CollaborationQmehmood@hotmail.com

• Over 16 years experience in technology.• Completed more than 30+ enterprise level

implementations in SharePoint.• Working Experience with Microsoft, Hitachi, T-Mobile.

as a Technical Program Manager.• Worked on Following Products:

• Microsoft MSN Live@Edu• XBOX and Zune digital Certificates Generation• MSDN Technet Newsletters

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

Scrum and AgileAgile 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

Problem - Why Scrum?

‣ Releases take too long ‣ Stabilization takes too long ‣ Changes are hard to make ‣ Quality is falling

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.

ReleasePlanning

DiscoverySession

Product Backlog

Planning Sprints

Retrospective

Sprint Backlog Production-Ready Features

Development Sprint Cycle

Sprint

SprintPlanning

DailyScrum

SprintReview

Scrum Methodology

Starting ScrumThe 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

Release planning

Scrum Methodology

Sprint Backlog

Product

BacklogVision

Sprints

Planning

Development

Unit Testing

Quality Assurance

Build

Deployment

Shipable Product

Sprint Mechanism

Sprint Planning

Daily Scrum

Sprint Review

Retrospective

Meeting

User storiesAcceptance criteriaBusiness rulesDevelopmentUnit TestingQuality AssuranceBuildDeployments

Value to customerCode is completeTesting is completeDocumentation is complete

Work

Work

Quick Process Overview

Scrum RolesProduct Owner

• Manages Product Backlog

• Makes decisions on Sprint Scope

• Provides details on features including acceptance criteria

• Decides on release date and content

• Accepts the deliverables

Scrum Master

• Responsible for facilitating process

• Manage communication between the Teams

• Produce project reporting to keep track of project performance

• Assists Product Owner in leveraging Scrum & managing the product backlog

The Team

• Architect and develop code as per the backlog items

• Perform Unit Testing

• Perform Quality Assurance

• Merge Code and ensure deploy-ability

Other stakeholders

• Customers• Vendors

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.

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.

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.

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

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.

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

Release Burndown

Sprint Burndown

Velocity Chart

Tools and Templates

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

Q&A

Thanks