zoukankan      html  css  js  c++  java
  • Essential Documents to Manage Your Projects

    Speak to an experienced project manager, and they can give you a wealth of good advice on the do's and don'ts to successfully manage any project. All this advice, in a nutshell, would be about how to manage the people doing the work (that includes you too), to deliver their results on time and to a budget, while keeping the risk of failure to a minimum.

    It really doesn't sound that difficult to do, but for some reason, many people think that project management is a massive overhead to any project. I often hear phrases like "oh, don't waste your time planning the work, just do it!" or "why are you wasting your time writing the objectives, we all know what needs to be done!"

    So the number one shortcut to successfully manage any project is:

    "Understand the few essential brief documents you need to create and regularly review during the life of your project."

    Document 1 - The Project Charter

    For example, at the beginning of your project, you need to create a one-page document called the project charter. This document will make sure that you and your customer understand the general goals of the project. After all, if you don't know where you are going, how are you going to get there? Remember, you could also be your own customer!

    To get this information, have a meeting with your customer and ask the following 3 essential questions:

    • What are the objectives of your project?
    • What do you want to produce or deliver?
    • What is the business reason for doing this project?

    After the meeting write the answers to these questions in your project charter and email this back to your customer and ask them for their approval.

    You have now successfully completed the most important aspect of any project, and that is to understand and agree with your customer where you are going with this project.

    If you look at the time spent to achieve this important step in a project, you are looking at one or two meetings and about 30 minutes to write up the information, say 2 hours in total for a small project. Not a big overhead at all.

    Document 2 - The Plan

    You can now get on and create the second document call the plan. This will include a list of the work that needs to be done (also referred to as the scope of work), who will do it, the cost and time to do this work, and finally a simple review of what will go wrong, known as a risk assessment.

    Document 3 - The Progress Report

    On a regular basis, anything from weekly to monthly, you need to create a progress report and deliver this to your customer. They want to know what work was done, when, and how much was spent. They also want to know if you need their help to solve any problems. Your major challenge is just collecting this information so that you can create your regular progress report.

    A Final Thought

    I have described the absolute minimum information you need to manage any project, and the key to success is understanding the few essential brief documents you need to create with this information - the project charter, the plan and the progress report. I hope it leads you to success in your projects.

  • 相关阅读:
    理解 QEMU/KVM 和 Ceph(2):QEMU 的 RBD 块驱动(block driver)
    Neutron VxLAN + Linux Bridge 环境中的网络 MTU
    理解 QEMU/KVM 和 Ceph(1):QEMU-KVM 和 Ceph RBD 的 缓存机制总结
    [译] 企业级 OpenStack 的六大需求(第 3 部分):弹性架构、全球交付
    [译] 企业级 OpenStack 的六大需求(第 2 部分):开放架构和混合云兼容
    [译] 企业级 OpenStack 的六大需求(第 1 部分):API 高可用、管理和安全
    Javascript中的Array(数组) 、{}(映射) 与JSON解析
    HTML中显示特殊字符,如尖括号 “<”,">"等等
    Ubuntu 12.04 安装配置 Apache2
    Python中函数的参数传递与可变长参数
  • 原文地址:https://www.cnblogs.com/RR-ghost/p/4198244.html
Copyright © 2011-2022 走看看