Monday, May 6, 2002
Joel has some really good ideas on how to make running a software development project schedule that actually is used:
- Use a spreadsheet, instead of complicated project management software
- Break the project down to features and tasks, very specifically. The design should be done before the schedule is written, which by the way should be done by the programmer.
- Estimate in hours; that's how specific your tasks should be.
- Don't forget about debugging, integration, and misc time that eats you up.
- Be sure to prioritize and complete the important features before the fun stuff.
And then, don't forget to eat dog food and try your new application, as a user. No admin privileges, no specially configured machine.
Knew this already, from my own experience: I'm a whole lot more productive when I can just hunker down and produce code, sans interruptions. But, this works only if
- I have a clean, organized work area
- The design is already done (actually design takes as much concentration as implementation)
- I have my schedule in order, so I'm not worrying about what I'm missing
- I don't happen to get many support requests (my other hat here at work)