Computer Project Management

In a university environment, Computer Projects
  • may be written as a one-off yet end up being used for years
  • are unlikely to depend on many commercial libraries/programs
  • may only ever be used inhouse
  • may well result in freeware
  • may well be written by one person
  • may have cutting edge technology
  • may not have much of a GUI
This document attempts to adapt some standard Project Management procedures to this situation (viewed mostly from the programmer's perspective). Contributions and suggestions welcomed!
(click on the "next" or "->" links to go to the next page or bullet-point)

Updated 10/02/03 with help from James Matheson
Tim Love