SCRUM example of the hyperproductive Borland QuattroPro team

1. SCRUM
Hyper productive teams

4. Quattro Pro team
We were prodded into setting up the first Scrum meeting
after reading James Coplien's paper on Borland's
development of Quattro Pro for Windows [2]. The
Quattro team delivered one million lines of C++ code in
31 months, with a four person staff growing to eight
people later in the project. This was about a thousand
lines of deliverable code per person per week, probably
the most productive project ever documented. The team
attained this level of productivity by intensive interaction
in daily meetings with project management, product
management, developers, documenters, and quality
assurance staff.

5. Quatro Pro team
One of the motivating factors in creating Scrum was
the Borland Quattro Pro project documented in
detail by James Coplien when he was at ATT Bell
Labs [2]. Each developer on this project generated
1000 lines of production C++ code every week for
three years. In comparison, productivity on the
recent Microsoft Vista project was 1000 lines of
code per developer per year. The Borland Quattro
Project was 52 times as productive as the Microsoft
Vista project measured by lines of code.

6. Quattro Pro team
One of the most widely regarded case studies of
a successful roll out and productivity assessment
for a software project, was Borland Quattro Pro
that was using Scrum before scrum become a
household name. Apparently, the Borland team
was able to produce 1000 lines of C++ code per
week with a less than 3% defect rate.