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

Definition How it started Things in Scrum

Scrum?

What? Why? Where? Who?

Rhoitman

Scrum Agile Development

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.

Rhoitman

Scrum Agile Development

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 Rhoitman Scrum Agile Development .

Introduction Work With Scrum At Last Definition How it started Things in Scrum Basically Scrum not a method Not about Software Where change must be replied Rhoitman Scrum Agile Development .

Toyoda Loom Popularized in Toyota car manufacturing (especially the Prius line) Also draws on Taylor’s application of Scientific Method to manufacturing (1911) Rhoitman Scrum Agile Development .Introduction Work With Scrum At Last Definition How it started Things in Scrum Lean Moment Originally. Kiichiro Toyoda.

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 process Find problems early Don’t build something of no value Minimize on-hand inventory [JIT] Rhoitman Scrum Agile Development .

Introduction Work With Scrum At Last Definition How it started Things in Scrum (Kaizen) Philosophy Aim to improve Learn by doing Try not to guess Rhoitman Scrum Agile Development .

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) Rhoitman Scrum Agile Development .Introduction Work With Scrum At Last Definition How it started Things in Scrum (Muda). (Muri) Concept of Taiichi Ohno Executive Vice President. (Mura).

DeGrace & Stahl termed SCRUM 1995. Languages & Applications Rhoitman Scrum Agile Development . Systems. Ken Schwaber & Jeff Sutherland co-presented Scrum at the OOPSLA* conference * Object-Oriented Programming.Introduction Work With Scrum At Last Definition How it started Things in Scrum Chronology 1986. Hirotaka Takeuchi & Ikujiro Nonaka 1991.

Introduction Work With Scrum At Last Definition 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 Definition 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 .

e Customer Set Requirements i.Introduction Work With Scrum At Last Definition How it started Things in Scrum Product Owner Vision the Product Speaks for all stakeholders i.e Write Product Backlog Rhoitman Scrum Agile Development .

Introduction Work With Scrum At Last Definition 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 Definition 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. estimated Rhoitman Scrum Agile Development . ordered. issues Emergent. technology.

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 .

.

’Ham and Eggs’?” The Pig responded. thank-you: while you’d be involved. I’d be committed.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.” Rhoitman Scrum Agile Development . “How about. “No. The Pig asked the Chicken: “What should we name it?” The Chicken responded.

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 .

stakeholders. Who will be there Product Owner Team Members ScrumMaster Others i. experts. executives and Anyone interested Discuss it.e customers. Rhoitman Scrum Agile Development . and figure out what to do next.Introduction Work With Scrum At Last Getting Started Benchmark Finally Sprint Review Inspect what was done during the Sprint.

Point Potential improvement. Decide? What’s working? What’s not working? What’s changes to try? Rhoitman Scrum Agile Development . Inspect & Adapt regarding the process.Introduction Work With Scrum At Last Getting Started Benchmark Finally Sprint Retrospective Scrum is focuses in (Kaizen). What’s done? Inspect & Adapt regarding the product.

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 .

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 Team Velocity Def n .

Introduction Work With Scrum At Last Getting Started Benchmark 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 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 .

.

When it is all out (usually within 15 minutes). the Developers can get up and go back to something. Upon command. forming a circle with their feet (pointing up) in the center.Introduction Work With Scrum At Last Getting Started Benchmark Finally Abnormal Termination All Developers gather. on their backs. They lie on the floor. they unloose their emotions about having their hard work jerked around by unknown forces that view chaos as better than productivity. touching one another’s feet. 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 Can’t 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 .

Rhoitman Scrum Agile Development .Appendix For Further Reading For Further Reading I Jeff Sutherland Scrum Handbook. 2010. Hirotaka Takeuchiand and Ikujiro Nonaka The New Product Management Game Harvard Business Review. 1986. Scrum Training Institute Press.