Ebooka przeczytasz w aplikacjach Legimi na:
Odsłuch ebooka (TTS) dostępny w abonamencie „ebooki+audiobooki bez limitu” w aplikacji Legimi na:
Part 0: Introduction
Part 1: THE PROBLEM--Traditional planning doesn’t work
Part 2: THE SOLUTION--Scrum : A better way to plan
Part 3: WHY SCRUM WORKS --The advantages of planning the Scrum way
Table of Contents
Scrum is a new and improved way to do projects. It is designed to be evolutionary and adaptive rather than top-down and prescriptive.
The convent ional way of doing product development is broken. The “Waterfall Method” – break a large project down into step-by-step chunks and schedule them on a Gantt chart – doesn’t work. Almost without fail, waterfall method projects fall behind schedule, go over budget and run the risk of generating products nobody wants or will pay for when completed.
Scrum was developed in 1993 as a new and improved way to do projects. It is designed to be evolutionary and adaptive rather than top- down and prescriptive. Scrum was initially used with great success in the software industry but has now been used successfully in almost every industry across the board.
Scrum draws on the advantages of the Toyota Production System and the OODA loop used in combat aviation. Scrum organizes around small teams – the most effective way to work – who prioritize what needs to be done and then run one- to two-week sprints to gain momentum and make everyone accountable. These teams stay organized by holding brief daily stand- up meetings where everyone can share tips, get help on challenges which crop up and be accountable.
“I first created Scrum, with Ken Schwaber, twenty years ago, as a faster, more reliable, more effective way to create software in the tech industry. Scrum is a radical change from the prescriptive, top-down project management methodologies of the past, Scrum, instead, is akin to evolutionary, adaptive, and self-correcting systems. We’ve used Scrum to build everything from affordable 100-miles-per-gallon cars to bringing the FBI database systems into the twenty-first century. I firmly believe Scrum can help to revolutionize how business works in virtually every industry.” — Jeff Sutherland
Top-down planning where the boss specifies what should be done and when (using color-coded charts) plain doesn’t work. All you end up with is an illusion of planning which fools noone. You should understand planning is useful but blindly following plans is stupid.
The conventional way to plan a project usually goes something like this:
■ Instructions on what needs to be done and how it is to be done flows from the top of the organization to the bottom in a waterfall-style cascade.
■ Some planners spend months specifying what needs to be done and who will do it.
■ The planners produce magnificent looking color-coded Gantt charts showing who will do what and when.
The only problem is what looks perfectly logical in those plans and charts invariably gets very messy when those detailed plans meet reality. Consequently, almost every project planned the conventional ways ends up being late and over budget. Furthermore, since you wait until the end to unveil to your end-user, chances are also pretty good what you end up developing will be something nobody wants or is prepared to pay for.