2. Quattro Pro teamWe were prodded into setting up the first Scrum meetingafter reading James Copliens paper on Borlandsdevelopment of Quattro Pro for Windows . TheQuattro team delivered one million lines of C++ code in31 months, with a four person staff growing to eightpeople later in the project. This was about a thousandlines of deliverable code per person per week, probablythe most productive project ever documented. The teamattained this level of productivity by intensive interactionin daily meetings with project management, productmanagement, developers, documenters, and qualityassurance staff.
3. Quatro Pro teamOne of the motivating factors in creating Scrum wasthe Borland Quattro Pro project documented indetail by James Coplien when he was at ATT BellLabs . Each developer on this project generated1000 lines of production C++ code every week forthree years. In comparison, productivity on therecent Microsoft Vista project was 1000 lines ofcode per developer per year. The Borland QuattroProject was 52 times as productive as the MicrosoftVista project measured by lines of code.
4. Quattro Pro teamOne of the most widely regarded case studies ofa successful roll out and productivity assessmentfor a software project, was Borland Quattro Prothat was using Scrum before scrum become ahousehold name. Apparently, the Borland teamwas able to produce 1000 lines of C++ code perweek with a less than 3% defect rate.