Project Life Cycle

Getting Started: Important Terms

• Deliverables:
  Each step in the Project Life Cycle is completed with a deliverable, which is usually a document, product, or a program. Deliverables represent the important milestones in every project. NOTE: Simply giving an oral report is not sufficient. Not only do deliverables document your progress, but they demonstrate your organizational skills and your professionalism, and in some cases, the deliverable can actually serve as a contract. For example, if the Business System Design promises a system of a specified configuration and capability, you can add signature lines for you and your client. The signatures create a legal contract which not only obligates you to deliver, but protects you from scope creep.

• Scope Creep:
  Scope Creep is a term that describes small changes that tend to sneak into a project after the specification is approved that can add major cost and time overruns. First of all, it can be managed. Sometimes scope changes should be curtailed. Sometimes they should be allowed, but be sure to have all parties sign off all changes. The best technique is to include a clause in your Business System Design stipulating that any change to the specification, once accepted by the client, will result in a delay of the deliverable date and additional cost to the client. Try to specify a minimum delay and cost. Each time a change is requested by the client remind them of the agreement. But, for the sake of good customer relations, if a change is small enough and you can reasonably include it without major impact, waive the cost. Record all changes in addenda to the specifications!

• Concurrency:
  Just because the steps of the Project Life Cycle are laid out in a certain order, doesn't mean that they have to be performed in exactly that sequence. In fact, such a rigid attitude could be wasteful and expensive! Some tasks can and should be done concurrently. For example, the Quality Assurance team can prepare test scripts at the same time that the development team is creating the system. Since both teams are working from the same detailed spec, such an arrangement serves to see how closely the development team followed the specification. A multi-person development team can write different portions of the application simultaneously. Closely examine every project to find opportunities for concurrency. Some are listed in the swim lane diagram.

• Revision Control:
  Don't assume that Revision Control Systems (RCS) are just for software! These packages are designed to track revisions of any type, not just source code changes. Take advantage of them to store revisions to the specifications or any of the deliverable documents, contracts, etc. This way, if the specification changes, you never lose the original. Managing revisions effectively will avoid contract disputes that may arise at some point. Many good ones are available. Microsoft Sourcesafe is a great choice if you're using any of Microsoft's Visual programming languages. MKS RCS is more document-oriented, and PVCS is a market leader. In addition, many free or shareware RCS packages exist. You can find some programs at Shareware.com.

  ---

  | Home | About Us | Clients | Project Management Resources | Tools & Templates | Links |