Your SlideShare is downloading. ×
0
210204006 pwp hyperproductive teams ncimgroep r001  kasph
210204006 pwp hyperproductive teams ncimgroep r001  kasph
210204006 pwp hyperproductive teams ncimgroep r001  kasph
210204006 pwp hyperproductive teams ncimgroep r001  kasph
210204006 pwp hyperproductive teams ncimgroep r001  kasph
210204006 pwp hyperproductive teams ncimgroep r001  kasph
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

210204006 pwp hyperproductive teams ncimgroep r001 kasph

149

Published on

SCRUM example of the hyperproductive Borland QuattroPro team

SCRUM example of the hyperproductive Borland QuattroPro team

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
149
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. SCRUMHyper productive teams
  • 2. Quattro Pro teamWe were prodded into setting up the first Scrum meetingafter reading James Copliens paper on Borlandsdevelopment of Quattro Pro for Windows [2]. 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 [2]. 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.

×