Teemu Suoranta

10%
Flag icon
For some years I have been successfully using the following rule of thumb for scheduling a software task: 1/3 planning 1/6 coding 1/4 component test and early system test 1/4 system test, all components in hand.
The Mythical Man-Month: Essays on Software Engineering
Rate this book
Clear rating