Introduction Work With Scrum At Last

Scrum Agile Development

Development Team

Rhoitman
Nepways Pvt. Ltd. Kathmandu, Nepal

2012, March 18

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Scrum?

What? Why? Where? Who?

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition 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.

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition 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 difcult to master

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Basically

Scrum not a method Not about Software Where change must be replied

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition 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 Taylors application of Scientic Method to manufacturing (1911)

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Lean Principle

Reduce waste! How? Dont let mistakes propagate into the process Find problems early Dont build something of no value Minimize on-hand inventory [JIT]

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

(Kaizen) Philosophy

Aim to improve Learn by doing Try not to guess

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

(Muda),

(Mura),

(Muri)

Concept of Taiichi Ohno Executive Vice President, Toyota The Three Ms of inefciency
(Muda): waste (Mura): inconsistencies (Muri): unharmonizing strain, disruptions in ow

Characteristics of Kaizen management philosophy Communication (Kanban) solves and problem due isolation (Andon)

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Chronology

1986, Hirotaka Takeuchi & Ikujiro Nonaka 1991, DeGrace & Stahl termed SCRUM 1995, Ken Schwaber & Jeff Sutherland co-presented Scrum at the OOPSLA* conference * Object-Oriented Programming, Systems, Languages & Applications

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Components of Scrum

Team ScrumMaster Product Owner Development Team*

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Scrum Master

Protect the team Motivate the team Severs the team Manage the process Think out of box

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition 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

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition 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"

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Denition How it started Things in Scrum

Components of Scrum. . .

Events Sprint Meeting Review Artifacts Product Backlog Sprint Backlog Burn down chart

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Work Flow

24 h

30 days

Product Backlog

Sprint Backlog

Sprint

Working increment

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Product Backlog

Prioritized list What it has List of functionality, technology, issues Emergent, ordered, estimated

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Sprint Planning

Sprint Goal Workable Output Features Prioritizing Who Plans? Who are there? How do they Plan?

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started 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 youd be involved, Id be committed.

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Daily Scrum

3 Questions What did you do (get done) yesterday? What will you do today? What impediments stand in your way?

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Daily Update

Sprint Backlog Burndown Chart

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark 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 gure out what to do next.

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Sprint Retrospective
Scrum is focuses in (Kaizen).

Whats done? Inspect & Adapt regarding the product. Inspect & Adapt regarding the process. Point Potential improvement. Decide? Whats working? Whats not working? Whats changes to try?

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Starting the Next Sprint

Updating Releases Backlog Burndown Chart

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark 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

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Team Velocity

Def n . Velocity is points completed per Sprint. Measures: The capability of group.

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Denition 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

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Using Tools

Version Management Automated build Automated testing QA Environments

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Getting Started Benchmark Finally

Abnormal Termination

All Developers gather. They lie on the oor, on their backs, forming a circle with their feet (pointing up) in the center, touching one anothers 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), the Developers can get up and go back to something.

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Who has been Using Scrum? FAQ

Who has been Using Scrum?

Rhoitman

Scrum Agile Development

Introduction Work With Scrum At Last

Who has been Using Scrum? FAQ

FAQ

Team Size should be 5 to 7 Sprint Duration normally 1 to 4 weeks Sprint Cant be extended Incomplete 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

Rhoitman

Scrum Agile Development

Appendix

For Further Reading

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.

Rhoitman

Scrum Agile Development