Project Life Cycle
I like to start most projects by negotiating a requirements list. This document defines (in plain English) the problems being solved and the ideal solution. The employer and I collaboratively write this document, via meetings, e-mails, or phone calls.
Once an initial requirements document is written, I can sit down and define the tasks necessary to fulfill the goals set forth. This also involves wrapping a timeline with estimates around the project.
Upon approval of the timeline, I can start work. In the ideal world, neither of these documents would change; because this is the real world, it is likely both will. Fulfilling a client’s expectations is the primary goal, so any re-factoring of the timeline or requirements document is almost never a problem.
When the solution is completed I install it for testing. Sometimes new work is discovered which needs to be added to the project, and sometimes there are bugs that need to be fixed. It is important to work closely together during this phase.
This is the Project Life Cycle I have found to work in the past for my clients and myself. However, I am always willing to change things if they make sense for the project. The most important factor towards success is establishing a close working relationship and free flow of information between the client and I.
|
