I have actually done a fair bit of work on the design, even to the point of having a UML model and having the class inheritance already worked out, and all the class shells having been created in the project. The issue is with explaining where I am and how I got to this point. So, in order to break the drought I started talking about the procrastination that is present in order to force the flow of ideas to continue.

Procrastination is one of my demons, both in initiating a project, and completing a project. The causes are usually to do with planning, scope, or being otherwise occupied. Scope is the simplest aspect to resolve in that features can be cut so as to reduce the required workload. Planning is where the majority of decisions regarding the direction of the project can be considered with regard to the desired scope of the project. A properly planned project should have adequate (and achievable) milestones, and a clear scope outlining desired functionality, and most importantly the undesired functionality. By identifying “features” that you do not want in the final project you can help to avoid feature creep.

The final issue regarding project procrastination is a hard one to resolve. These days things are hectic with work, family, friends, activities, study, and a lot more pressures bearing down on our limited workday. Planning plays some role in this as well, as by scheduling time in which to actually do project work removes some of the excuse of avoiding the project work.

So, having now written about my own procrastination, it is time now to start on my project. Thanks for reading.

Cheers, Chris.