1_scrum

8/2/2019 1_scrum

http://slidepdf.com/reader/full/1scrum 1/36

Introduction

Work With Scrum

At Last

Scrum Agile DevelopmentDevelopment Team

Rhoitman

Nepways Pvt. Ltd.Kathmandu, Nepal

2012, March 18

Rhoitman Scrum Agile Development

http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

Scrum?

What?

Why?

Where?

Who?


http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

What Wikipedia says?

Scrum is an iterative and incremental

methodology for software projects and product or application

development. It is also one of the variants of agile software

development methodologies.


http://find/

http://goback/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

What ScrumMaster Says?

A framework within which people can address complex

adaptive problems, while productively and creatively

delivering products of the highest possible value.

Scrum is:

Lightweight

Simple to understand

Extremely difficult to master


http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

Basically

Scrum not a methodNot about Software

Where change must be replied


I d i D fi i i

http://find/

http://goback/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

Lean Moment

Originally, Kiichiro Toyoda, Toyoda Loom

Popularized in Toyota car manufacturing(especially the Prius line)

Also draws on Taylor’s application of Scientific Method to

manufacturing (1911)


I t d ti D fi iti

http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

Lean Principle

Reduce waste! How?

Don’t let mistakes propagate into the processFind problems early

Don’t build something of no value

Minimize on-hand inventory [JIT]


Introduction Definition

http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

(Kaizen) Philosophy

Aim to improveLearn by doing

Try not to guess



http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

(Muda),(Mura),(Muri)

Concept of Taiichi Ohno

Executive Vice President, Toyota

The “Three Ms” of inefficiency

(Muda): waste

(Mura): inconsistencies(Muri): unharmonizing strain, disruptions in flow

Characteristics of Kaizen management philosophy

Communication (Kanban) solves and problem due isolation

(Andon)



http://find/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

Chronology

1986, Hirotaka Takeuchi & Ikujiro Nonaka

1991, DeGrace & Stahl termed SCRUM1995, Ken Schwaber & Jeff Sutherland co-presented

Scrum at the OOPSLA* conference

* Object-Oriented Programming, Systems, Languages &

Applications



http://find/

http://goback/

8/2/2019 1_scrum


Introduction

Work With Scrum

At Last

Definition

How it started

Things in Scrum

Components of Scrum

Team

ScrumMaster

Product Owner

Development Team*


http://find/

8/2/2019 1_scrum



http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

How it started

Things in Scrum

Scrum Master

Protect the team

Motivate the team

Severs the team

Manage the process

Think out of box



http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

How it started

Things in Scrum

Product Owner

Vision the Product

Speaks for all stakeholders i.e Customer

Set Requirements i.e Write Product Backlog



http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

How it started

Things in Scrum

Development Team

Estimate the Task Duration

Free do decide how to solve task

Cross-Functional Team

Includes necessary expertise

Self Organize

"No one tell them what to do"



http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

How it started

Things in Scrum

Components of Scrum. . .

Events

Sprint

Meeting

Review

Artifacts

Product Backlog

Sprint Backlog

Burn down chart


Introduction

W k Wi h S

Getting Started

B h k

http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

Benchmark

Finally

Work Flow

30 days

24 h

Working incrementSprint Backlog SprintProduct Backlog


Introduction

W k With S

Getting Started

B h k

http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

Benchmark

Finally

Product Backlog

Prioritized list

What it has

List of functionality, technology, issues

Emergent, ordered, estimated


Introduction

Work With Scrum

Getting Started

Benchmark

http://find/

http://goback/

8/2/2019 1_scrum


Work With Scrum

At Last

Benchmark

Finally

Sprint Planning

Sprint Goal

Workable OutputFeatures Prioritizing

Who Plans?

Who are there?

How do they Plan?


http://find/

http://goback/

8/2/2019 1_scrum


IntroductionWork With Scrum

Getting StartedBenchmark

http://find/

8/2/2019 1_scrum


Work With Scrum

At Last

Benchmark

Finally

Daily Scrum

Classic Story!

A Chicken and a Pig decided to go into resturant business.

The Pig asked the Chicken:

“What should we name it?”

The Chicken responded,

“How about, ’Ham and Eggs’?”

The Pig responded,

“No, thank-you: while you’d be involved, I’d becommitted.”




http://find/

8/2/2019 1_scrum


Work With Scrum

At Last

Benchmark

Finally

Daily Scrum

3 Questions

What did you do (get done) yesterday?

What will you do today?

What impediments stand in your way?




http://find/

8/2/2019 1_scrum


Work With Scrum

At Last

Benchmark

Finally

Daily Update

Sprint Backlog

Burndown Chart




http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Sprint Review

Inspect what was done during the Sprint.

Who will be there

Product Owner

Team Members

ScrumMaster

Others i.e customers, stakeholders, experts, executives

and Anyone interested

Discuss it, and figure out what to do next.




http://find/

8/2/2019 1_scrum


At Last Finally

Sprint Retrospective

Scrum is focuses in(Kaizen).

What’s done?

Inspect & Adapt regarding the product.

Inspect & Adapt regarding the process.Point Potential improvement.

Decide?

What’s working?What’s not working?

What’s changes to try?




http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Starting the Next Sprint

Updating

Releases

Backlog

Burndown Chart


http://find/

http://goback/

8/2/2019 1_scrum



A L


Fi ll

http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Burndown Chart

Its Management tool of Scrum

Why?

It is stupid to track time consumed doing a task!

Time records are a waste of time!

What it does?

Focus on achieving the end date

The focus is on delivery

Estimation Velocity



At L t


Fi ll

http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Team Velocity

Def n .

Velocity is points completed per Sprint.

Measures: The capability of group.



At Last


Finally

http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Definition of Done (DoD)

What “Done” means must be agreed by the Scrum Team

There must be no remaining work

Means its must be ready to ship



At Last


Finally

http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Using Tools

Version Management

Automated build

Automated testing

QA Environments


http://find/

http://goback/

8/2/2019 1_scrum



At Last


Finally

http://find/

http://goback/

8/2/2019 1_scrum


At Last Finally

Abnormal Termination

All Developers gather.

They lie on the floor, on their backs, forming a circle with

their feet (pointing up) in the center, touching one another’s

feet.

Upon command, they unloose their emotions about having

their hard work jerked around by unknown forces that view

chaos as better than productivity.

When it is all out (usually within 15 minutes), theDevelopers can get up and go back to something.



At Last

Who has been Using Scrum?

FAQ

http://find/

http://goback/

8/2/2019 1_scrum


At Last




At Last


FAQ

http://find/

http://goback/

8/2/2019 1_scrum


FAQ

Team Size should be 5 to 7

Sprint Duration normally 1 to 4 weeks

Sprint Can’t be extendedIncomplete Task moves on to next Sprint

Stand up meeting not meant for reporting

Product Owner can Terminate the Sprint

Product Owen is not a product manager


Appendix For Further Reading

http://find/

http://goback/

8/2/2019 1_scrum


For Further Reading I

Jeff Sutherland

Scrum Handbook.

Scrum Training Institute Press, 2010.

Hirotaka Takeuchiand and Ikujiro Nonaka

The New Product Management Game

Harvard Business Review, 1986.


http://find/

Documents

1_scrum