On Mon, 2009-04-20 at 14:05 -0400, Scott Lawrence wrote: > I think that there has been difficulty with: > > * Keeping the list of 'desired' features for a release short > enough that the odds of all of them coming in on time are > reasonable (if there's a 20% chance of each item slipping, then > you only need 4 such before your odds of hitting the date are > down to 41% - and I've never met a programmer who consistently > met schedules 80% of the time). > > * Dedicating people to 'overlapped' development (that is, get some > people working on changes that will take a long time targeted > for release N+1 while others are doing release N).
It seems clear that we need some mechanism for overlapped development. As the number of workers increases, just synchronizing them to all have a stable point at the same time becomes impossible. If we can do overlapped development with some efficiency, then shortening the mandatory features list for the next release would suffice to shorten the development cycle. Dale _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
