Basics of Scrum

By Sarath Revuri, PMP , CSM , PRINCE2 Practitioner

We will only be discussing basics about Scrum and activities involved.

What is Project? What is Project Management ? What is Agile Agile Examples What is Scrum? Cost of change in Scrum Scrum roles Scrum activities Process flow Project Backlog Burn down chart Sprint Backlog Need to remember Credits

Agenda

2
7/20/2012

A project is a temporary endeavor having a defined beginning and end undertaken to meet unique goals and objectives usually to bring about beneficial change or added value The temporary nature of projects stands in contrast to business as usual (or operations), which are repetitive, permanent or semi-permanent functional work to produce products or services.

What is project?

3
7/20/2012

 Project Management is application of knowledge, skills tools and techniques to project activities to meet the project requirements

What is project management?

4
7/20/2012

 Agile software development refers to a group of software development methodologies based on iterative development Deliver something useful to client; check what they value Build competitive teams Enable team decision making Use short time boxed iterations to quickly deliver features Focus on delivery activity not process compliance activities

What is Agile?

5
7/20/2012

 Extreme Programming (XP) is a software development methodology which is intended to improve software quality and responsiveness to changing customer requirements. As a type of agile software development, it advocates frequent "releases" in short development cycles (timeboxing), which is intended to improve productivity and introduce checkpoints where new customer requirements can be adopted. Extreme project management (XPM) refers to a method of managing very complex and very uncertain projects. It differs from traditional project management mainly in its open, elastic and undeterministic approach. The main focus of XPM is on the human side of project management (e.g. managing project stakeholders), rather than on intricate scheduling techniques and heavy formalism. Adaptive Software Development is a software development process that grew out of rapid application development work by Jim Highsmith and Sam Bayer. ASD embodies the principle that continuous adaptation of the process to the work at hand is the normal state of affairs. Scrum Projects are divided into 30-Day work intervals in which specific number of requirements for a prioritized list are implemented. Daily 15 Minutes Scrum Meetings maintain coordiantion

Agile Examples

6
7/20/2012

Scrum is a simple approach for managing complex projects.

Based on common sense Less documentation Release early, release often Avoid chaos Better level of communication Commitment oriented Agile in nature and practice

What is Scrum?

7
7/20/2012

Scrum is flexible enough to accommodate changes easily to requirements without much impact on budget.

Cost of change in Scrum

Scrum allows changes at any point But not in a release cycle Scrum expects changes would come up and stays prepared for them
Cost of change

Waterfall

Cost of change
Development Life Cycle

Scrum Development Life Cycle

8
7/20/2012

Scrum makes clear distinction between committed members and interested members of a team.

Product owner
Customer representative Prioritizes product requirements

Team
Develops product Responsible for failure or success Self managed and organized

Scrum Master
Teaches and implements Scrum Ensures Scrum is practiced properly Maintains documentation required

Scrum roles

9
7/20/2012

Scrum process is all about clarity, inspection and adaptation.

Sprint planning meeting

Before every Sprint Divided in two half for focusing on what to do and how to do

Sprint
Release cycle of 2 to 4 weeks No changes accepted while in Sprint

Daily Scrum
Daily meeting during Sprint for about 15 minutes Every member answers:
What they did since last meeting? What they plan to do till next meeting? What obstacles are there in their way?

Scrum activities

? ? ?
10
7/20/2012

Continued

Scrum process is all about clarity, inspection and adaptation.

Scrum review meeting

Is done after every Sprint To demonstrate that is being done And give feedback

Scrum retrospective meeting

Is done at end of every Sprint after review meeting To discuss experiences and problems faced to improve further The product owner is not required to attend this meeting

Scrum activities

11
7/20/2012

Scrum process flow is iterative and incremental in nature. It is a light weight process focused on better performance.

15 mins Daily Scrum Meeting Sprint

Sprint Backlog

Backlog tasks distributed by team

30 days

Product Backlog As prioritized by Product Owner

Potentially Shippable Product Increment

Process flow

12
7/20/2012

System requirements in order of priority. In a traditional way it is the project plan.

Same as Project plan Monitors entire project Prioritized to get faster ROI and better results Prepared and managed by product owner Requirements can be added at any point Sweet and simple, easy to manage

Product backlog

13
7/20/2012

System requirements in order of priority. In a traditional way it is the project plan.

Product backlog

14
7/20/2012

Indicator which tells progress of project and individuals very clearly. Similar to Gantt charts.

Helps in predicting problems Helps in performance appraisals Works like an overall tracker Useful for evaluating overall performance

Burndown Chart

15
7/20/2012

Indicator which tells progress of project and individuals very clearly. Similar to Gantt charts.

No work being done

Work done

Days in Sprint

Burndown Chart

16
7/20/2012

Indicator which tells progress of project and individuals very clearly. Similar to Gantt charts.

Work being done but not very fast

Work done

Days in Sprint

Burndown Chart

17
7/20/2012

Indicator which tells progress of project and individuals very clearly. Similar to Gantt charts.

Work being done but not very fast

Work done

Days in Sprint

Burndown Chart

18
7/20/2012

Indicator which tells progress of project and individuals very clearly. Similar to Gantt charts.

Individual Burndown chart

Work done

Days in Sprint

Burndown Chart

19
7/20/2012

Part of product backlog that can form a deliverable Similar to a release plan in traditional project management

Product requirement that will be covered in a sprint A real time picture of work in a sprint Avoids problems that may delay or fail a release Doesnt allow any additions Can only be modified by team

Sprint backlog

20
7/20/2012

Part of product backlog that can form a deliverable Similar to a release plan in traditional project management

Sprint backlog

21
7/20/2012

We are back to where we started. What is Scrum?

Few important facts to always remember about scrum

Is common sense Is not a solution to every problem Is an approach towards software development Is very fast and flexible Is commitment oriented Is based on clarity, inspection and adaptation Implementing scrum takes time (nothing such as big bang)

Need to remember

22
7/20/2012

 E-Mail: sarath@revuri.com Resources

http://www.theprojectmanagement.com http://sarath.revuri.com

Questions

23
7/20/2012