| 
|
QuoteRef: cusuMA6_1997
topics >
all references >
ThesaHelp:
ACM references a-e
ThesaHelp:
references c-d
Topic:
management of large software projects
Topic:
incremental development
Topic:
software metrics
Topic:
specification is infeasible
Topic:
software management
Reference
Cusumano, M.A., Selby, R.W., "How Microsoft builds software", Communications of the ACM, 40, 6, pp. 53-61, June 1997. Google
54 ;;Quote: Microsoft uses synch-and-stabilize, daily build, and zero-defect; work in parallel but synch and debug daily with a shippable product; common language, continuous testing, milestone and release metrics
56 ;;Quote: during product development at Microsoft, the feature set may change 30% or more from the original specification
58 ;;Quote: software check in must happen by 2 or 5 p.m. so that a new build is ready the next day
58+;;Quote: most developers check in code two or more times per week
58 ;;Quote: if a developer breaks the build, it must be fixed immediately
ThesaHelp: ACM references a-e (259 items)
ThesaHelp: references c-d (337 items)
Topic: management of large software projects (63 items)
Topic: incremental development (74 items)
Topic: software metrics (32 items)
Topic: specification is infeasible (46 items)
Topic: software management (27 items)