Lecture 4 Assignment

Web Project Management Home Page Lecture 4: Web Project Management Essentials 2

Alternative Assignment 1: Create a Documentation Plan identifying which, if any, templates you will use in your Web Project Process.

Alternative Assignment 2: If you currently have a set of templates that you would like feedback on them submit those instead. Indicate if there are any templates you lack but plan to start using.

One thought on “Lecture 4 Assignment

  1. Tonya Price Post author

    Hi Glenn and Barbara,
    Glenn’s assignment and feedback below. Barbara I haven’t received yours yet. I did clean out my spam folder late last week and I’m wondering if it might have gone to spam and Ijust missed it and accidently deleted it. If you have already sent my your Assignment 4 would you mind resending?

    Thanks,
    Tonya

    Glenn’s Assignment 4 Submission for Essentials 2 lecture is found at:
    Assignment Three – Essentials2

    Here is my feedback:
    Hi Glenn,

    You have a very complete plan here. Several of the documents you describe are often combined into one document, but the important thing is that you collect the information you need to manage the project. If you try a document and you find that the information is a burden to collect and does not help you improve communications or keep track of the project or manage the progress of the project, then there is no reason to use the document.

    Some documents are designed to educate and keep the client aware of the project status. You want to make sure the client 1) understands and agrees with all your assumptions 2) understands the process and the implication of change requests on the budget and deadline 3) is not surprised by anything that occurs during the project (this is why you create a risk management plan which outlines risks and backup plans) and you want to make sure the client knows what they need to do to maintain and use the web project effectively once the project is complete.

    One note about templates – these are the basis for documents that you will use during projects. I prefer to include information in the template that cover any contingency and then delete from the template information I don’t need for a project. This reduces the chance that I will forget some section that I wanted to include but overlooked. For example, if your client does not have a Content Management System and a CMS in not part of the project, then you wouldn’t need any sections about a CMS in your Project Brief or Project Specification however, you might still want the info in your template for those projects which would require a CMS or must deal with a CMS as part of the project. Figure out what works best for you. There are no right or wrong ways to do these things, just what works best for you.

    If you don’t want to use templates, then you might consider a checklist of everything you might want in your document to use as a reminder so you don’t accidentally forget to include information.

    There is a lot of confusing information about documents. Many go by different names although they contain the same information. For example, a Project Brief is also called a Creative Brief and a Proposal. The Project Specification is also called a Contract. The most important thing to remember is focus on the information you need to collect, retain and analyze rather than worrying about what the documents are called.

    Consider these templates as “dynamic” documents that are constantly being revised. Lessons Learned help us improve our documents, fine tuning what information is helpful to collect and share and what information is redundant or unimportant for managing the project.

    It is important 1) that the client reviews and approves your understanding of the project and assumptions you are making as create a project strategy and that 2) the client signs a document that states the approach, the process and the deliverables. Many firms avoid listing hourly rates, feeling it is better to quote a price for the project, with hourly rates restricted to any change work requests. Again, you know your business best so pick the approach most appropriate for your work, I just try to mention ideas that might be useful.

    In addition to the client, you want to make sure that the Web team also understands the process that is going to be followed.

    It is important to have the documents together so that if something happens and you are unavailable, someone else could step in as Web project manager and continue the project. That is why you might consider keeping your template set together in a large Project Specification document. Often this document is maintained throughout the project with meeting notes being added and lessons learned and the closing document included when the project is completed. This also makes it easier for you to go back and review the information on the project in the future should the client return and request additional phase 2 work be done on the initial project.

    Good job on this assignment. Let me know if you have any questions. The most important information to remember about templates and documents is to use them to gain better control over the project. Do not let the documents rule you. If you are spending so much time on the documents that you can’t get your work done, then your documents need to be simplified.

    Tonya

Leave a Reply