Jeff e Ken trabalharam em conjunto para resumir o que haviam aprendido ao longo do tempo; eles criaram uma nova metodologia, que foi chamada de Scrum, descrita em um artigo de Schwaber, “Scrum and the perfect storm” (“Scrum e a tempestade perfeita”), disponível em www.controlchaos.com/my-articles.
Segue abaixo The Origins of Scrum(As Origens do Scrum), tenha uma ótima leitura.
The Scrum software development process described in this article arose from shared
concerns between Advanced Development Methods (ADM) and VMARK Software
(VMARK). ADM produces process automation software. VMARK produces objectoriented software development environments. Both companies were concerned over the
lack of breakthrough productivity being reported in object-oriented development projects.
Both ADM’s and VMARK’s products are built using OO, and breakthrough productivity
had been experienced in both companies.
We were particularly concerned that OO and component-based development were being
hindered by currently available development processes. We wanted to ensure that the
processes used by our organizations, and other ISV’s, were available to our customers and
the software development community.
After further analyzing how successful ISV’s build software, we found that our
development processes are very similar. We all use empirical processes. We all control
the empirical processes through quantitative measures. We refer to the results of these
processes as “the best possible software” or “good enough software.” We all were able to
relate stories of peers who used empirical processes without controls, and who were now
in the sin bin of failed ISV’s.
The ISV’s understood that building systems is an art guided by rules of thumb and tips
and techniques. A methodologist at one ISV said “…you can’t expect a processto tell you
everything to do. Writing software is a creative process, like painting or writing or
architecture… … [a process] supplies a framework that tells how to go about it and
identifies the places where creativity is needed. But you still have to supply the
Our first step in formalizing the ISV empirical development process into Scrum was
researching why the ISV empirical software development approach delivers breakthrough
productivity, and why the defined process advocated by the Software Engineering
Institute’s Capability Maturity Model (SEI’s CMM) doesn’t. After all, CMM promises
those most elusive of things-predictability, quality, repeatability, and improvability.