Scrum guide
5711 mots
23 pages
SCRUMGUIDEBy Ken Schwaber, May, 2009
SCRUMGUIDE
By Ken Schwaber, May, 2009
INTRODUCTION TO SCRUM
Scrum has been used to develop complex products since the early 1990s. This paper describes how to use Scrum to build products. Scrum is not a process or a technique for building products; rather, it is a framework within which you can employ various processes and techniques. The role of Scrum is to surface the relative efficacy of your development practices so that you can improve upon them while providing a framework within which complex products can be developed.
SCRUM THEORY
Scrum, which is grounded in empirical process control theory, employs an iterative, incremental approach to optimize predictability and control risk. Three legs uphold every implementation of empirical process control.
THE FIRST LEG IS TRANSPARENCY
Transparency ensures that aspects of the process that affect the outcome must be visible to those managing the outcomes. Not only must these aspects be transparent, but also what is being seen must be known.That is, when someone inspecting a process believes that something is done; it must be equivalent to their definition of done.
THE SECOND LEG IS INSPECTION
The various aspects of the process must be inspected frequently enough so that unacceptable variances in the process can be detected. The frequency of inspection has to take into consideration that all processes are changed by the act of inspection. A conundrum occurs when the required frequency of inspection exceeds the tolerance to inspection of the process. Fortunately, this doesn’t seem to be true of software development. The other factor is the skill and diligence of the people inspecting the work results.
2
THE THIRD LEG IS ADAPTATION
If the inspector determines from the inspection that one or more aspects of the process are outside acceptable limits, and that the resulting product will be unacceptable, the inspector must adjust the process or the material