Front page | perl.bootstrap |
Postings from August 2000
skud@netizen.com.au [skud@netizen.com.au] quoth: *> 6. Implementation, which breaks down into the following general areas *> of work: *> + Coding of the Perl 6 core *> + Coding of the standard library *> + Quality assurance and testing *> + Change management *> + Documentation One thing you might add to the implementation step is flow control as there will be groups who depend on another to finish their work before they can finish theirs. Making sure everyone is on the same page on deadlines, process, cross-communication and interdependency of tasks is key to keep bottlenecks from frustrating people who don't have a lot of time to waste and want to keep the ball rolling. A bottleneck abatement process is also something to consider. As much as I despise groupware, I find MS Project to be a fantastic tool to get 15 people all looking at the same visual picture of where their piece of the project fits in with all the others. Perhaps there is an Open Source equivalent that the working group chairs could all use and keep in sync with. Nice job :) e.Thread Previous | Thread Next