Developing good habits and a plan
The aspiration for this week is developing the plan. Given the choice of writing about a project and getting on with the grunt work, I very much prefer the latter. In my ideal world I’d have a subordinate who’d handle that for expressing the plan.
Projects imply size and therefore large chunks of time. Accountants will say time is money, so it is a sure bet that such a commitment of time will require somebody somewhere to give the OK. One of the purposes of the group project in Part II would have been to provide exposure to the whole idea of this planning which involves expressing facts, developing a potential fiction and being aware of potential failures. These would be the development of a skills assessment, a gantt chart and a risk analysis respectively.
The issue at present is the exact requirements and therefore the exact tasks and the exact skills required for such tasks until the research phase is complete, therefore it pays to be somewhat vague and produce something which behaves as a basis for future work.
First, there is the skill assessment. Although this may reflect personal opinion to a certain extend, an honest person will produce something which is close to the truth and can be considered fact. Second, there is the gantt chart. Given this is likely to be modified heavily before the end of the project, it is assumed to be a fiction of sorts. In manufacturing, this would be quite poor, but this is software development. Finally, there is a risk analysis which aims to handle potential failures. This is difficult to get right in the mathematical sense, since this would require either a time machine or a functioning crystal ball. Clearly there not many of these about since how many people had Volcanoes in Iceland on a risk assessment written before April?