Scheduling relieves stress. However it is difficult to do accurately predict how much time tasks will take. They must be decomposed and thought about before the actual amount of work can be determined.
Some helpful tips:
- Decompose tasks into sufficiently small tasks such that you can determine the length of each task
- Give yourself extra time for mistakes and unforeseen costs, I’d say somewhere between 25-50% of what you’ve already allocated.
- Give yourself time to learn and evaluate the best way to do something. This is the intellectual of task of examining other people’s work and thinking about interface design, software use cases and requirements, and software architecture as well as various technologies. This depends on how well you know the technologies you’re working with, but it always seems there are things you don’t know about that could help you write better programs. Exploration is key here.
- Communication about the software itself is a large cost that is mostly fixed.
0 Responses to “Software Development Scheduling”