下载文档原格式
Project最简单的横线项目管理模板介绍本文档提供了一个最简单的横线项目管理模板，适用于小型项目和需求不复杂的项目。
该模板旨在帮助项目管理者规划、组织和监控项目，确保项目按时交付和达到预期目标。
项目概述在这个部分中，描述项目的目标和背景信息。
明确项目的目标是什么，项目是为了解决什么问题或实现什么结果。
目标在这里列出项目的主要目标和预期结果。
背景提供项目的背景信息，包括项目的动机和相关的外部因素。
项目计划这个部分将讨论项目的计划和主要阶段。
这里只提供一个简要的概述，不需要给出详细的计划和时间表。
阶段1: 规划描述项目的规划阶段，包括收集需求、定义项目范围和目标、制定项目计划和分配资源等。
阶段2: 执行描述项目的执行阶段，包括实施计划、管理团队和资源、监控项目进展等。
阶段3: 完成描述项目的完成阶段，包括审查项目成果、确认交付物和客户验收等。
项目团队在这个部分中，明确项目团队的角色和职责。
列出各个团队成员和他们的职责，以便项目进度和任务分配的可视化。
里程碑在这里列出项目的重要里程碑，并给出每个里程碑的预计完成日期。
里程碑有助于项目管理者和团队成员跟踪项目进展和评估项目的进展情况。
风险管理在这个部分中，描述项目可能面临的主要风险，并提供相应的应对措施。
风险1: [风险描述]描述风险1，并提供解决方案。
风险2: [风险描述]描述风险2，并提供解决方案。
项目监控和控制在这个部分中，说明如何监控和控制项目的进展。
监控描述项目管理者和团队成员如何监控项目的进展和达成目标。
控制说明项目管理者如何采取行动来纠正偏差和确保项目按计划进行。
项目评估在这个部分中，讨论如何评估项目的成功和项目交付后的持续价值。
评估标准提供项目成功的评估标准，根据这些标准衡量项目是否达到预期目标。
持续价值描述项目交付后的持续价值，并说明如何跟踪和评估持续价值的实现。
结论总结本文档的内容，并强调项目管理的重要性和这个横线项目管理模板的简单性。
PROJECT项目管理案例一、项目简介项目的主要工作是维修某主要道路下一段长约1公里的供水管道，市政局要求电力部门配合施工，同时铺设一条地下电缆，以增加该道路两侧的用电用户。
由于该项目是在现有道路上开挖，故市政局决定在回填后顺便铺设新的混凝土路面。
为此，专门成立了一个项目管理办公室，以管理、协调该项目。
项目内容包括：供水工程、电力工程和道路工程。
整个项目从2009年7月1日提交预算报批为开始，市政局希望将项目施工对公众造成的影响降至最低，故希望该项目能在2009年10月底竣工并恢复交通。
二、项目任务关系、固定成本及资源需求量项目各项任务逻辑关系及固定成本(设备费、材料费和管理费等)、资源需求量如表1。
预算报批需1周，对外公告需2周时间。
三、可用资源项目施工可用资源(仅考虑劳动力)及其费率如表2所示，项目实施期间的日常管理费用为每天50元。
四、项目管理要求（1）根据所给条件，确定项目是否可按上级要求如期完成?如果完不成，各种工人各需要增加多少?项目的总成本能否控制在50万元的预算内?（2）跟踪和控制项目的实施。
五、使用PROJECT进行该项目管理的具体步骤参考(1)输入项目基本信息；(2)输入任务名称、任务持续时间、建立任务间的逻辑关系；(3)检查网络逻辑关系；(4)输入资源数据、费用数据；(5)保存进度计划和基础数据；(6)检查工期和成本目标是否符合要求，不符合则进行调整和优化；(7)将最优计划设置为基准计划；(8)打印计划报告(网络图、横道图、资源负荷图)；(9)开始实施项目，并分别在7、8、9、10月底各进行一次跟踪和控制。
六、监控条件(1)第一轮进度监控信息：预算在2009年7月31日才获批准，即工序“预算报批”的实际完成时间是2009年7月31日。
分析由于“预算报批”工序延期对其它各项目的影响及对整个项目工期和成本的影响。
进行项目调整，设法使项目的竣工日期不变，如不可能，则设法优化出最短工期。
项目章程XXX股份有限公司XXXXXXXXX软件有限公司2021年4月23日文档控制更改记录审核分发目录1项目章程介绍 (7)1.1总览 (7)1.2项目目标 (7)1.2.1总体应用目标 (7)1.2.2具体应用目标 (7)2 实施策略 (7)2.1实施策略 (7)2.2实施策略的考虑 (8)3项目范围 (9)3.1功能范围 (9)3.2实体范围 (9)3.3技术范围 (9)4项目组织结构 (10)4.1项目组织结构图 (10)4.2职责 (10)5项目计划 (14)5.1项目阶段划分及关键任务 (15)5.2时间表 (15)5.3里程碑 (15)5.4项目计划执行和报告 (16)6项目文档管理 (17)6.1项目文档管理的重要性 (17)6.2项目文档体系 (17)6.3项目文档管理环境 (20)7项目沟通管理 (20)7.1项目决策流程 (20)7.2项目列会 (22)8项目风险管理 (22)8.1实施周期延期的风险 (22)8.2实施范围风险 (22)8.3人员的风险 (23)8.4管理变革的风险 (23)9项目变更管理 (24)9.1提出变更 (24)9.2接收方的响应 (25)9.3申请方的认可 (26)9.4变更实施 (26)9.5变更程序流程 (26)10知识转移 (26)11质量控制 (27)12验收标准 (27)12.1验收方式 (27)12.2验收标准(根据项目情况修改) (28)13文件签署 (29)文档目的本文档资料的目的是用来确定适合本项目的政策, 标准及程序。
文档资料也阐明了何时，何人如何使用这些政策, 标准及程序。
如未有特殊申明，本文档资料的内容适合于项目组中的所有人。
关键联系信息1项目章程介绍1.1总览XXX公司决定在实施XXXX管理系统（以下简称XXXX系统），并选择XX公司进行XX系统实施。
该项目章程作为双方同意的文件，将包括项目目标的定义，实施策略的制定和项目组成人员和责任的确认，以及项目工作的计划。
PROJECT项目管理案例一、项目简介项目的主要工作是维修某主要道路下一段长约1公里的供水管道，市政局要求电力部门配合施工，同时铺设一条地下电缆，以增加该道路两侧的用电用户。
由于该项目是在现有道路上开挖，故市政局决定在回填后顺便铺设新的混凝土路面。
为此，专门成立了一个项目管理办公室，以管理、协调该项目。
项目内容包括：供水工程、电力工程和道路工程。
整个项目从2013年7月1日提交预算报批为开始，市政局希望将项目施工对公众造成的影响降至最低，故希望该项目能在2013年10月底竣工并恢复交通。
二、项目任务关系、固定成本及资源需求量项目各项任务逻辑关系及固定成本(设备费、材料费和管理费等)、资源需求量如表1。
三、可用资源项目施工可用资源(仅考虑劳动力)及其费率如表2所示，项目实施期间的日常管理费用为每天50元。
四、项目管理要求（1）根据所给条件，确定项目是否可按上级要求如期完成?如果完不成，各种工人各需要增加多少?项目的总成本能否控制在50万元的预算内?（2）跟踪和控制项目的实施。
五、使用PROJECT进行该项目管理的具体步骤参考(1)输入项目基本信息；(2)输入任务名称、任务持续时间、建立任务间的逻辑关系；(3)检查网络逻辑关系；(4)输入资源数据、费用数据；(5)保存进度计划和基础数据；(6)检查工期和成本目标是否符合要求，不符合则进行调整和优化；(7)将最优计划设置为基准计划；(8)打印计划报告(网络图、横道图、资源负荷图)；(9)开始实施项目，并分别在7、8、9、10月底各进行一次跟踪和控制。
六、监控条件(1)第一轮进度监控信息：预算在2013年7月31日才获批准，即工序“预算报批”的实际完成时间是2013年7月31日。
分析由于“预算报批”工序延期对其它各项目的影响及对整个项目工期和成本的影响。
进行项目调整，设法使项目的竣工日期不变，如不可能，则设法优化出最短工期。
写出分析报告。
(2)第二轮监控信息：在8月底,工序“向社会公告”已经完成，工序“开走路上车辆”也已经完成，但是工序“开挖槽沟”还没有开始。
Xavor Corporation<Project Name>Project Management PlanVersion <x.x> [Note: The following template is provided for use in Xavor projects. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document.]Organization Level Template CMM – Xavor Corporation Document #:XVR.0002/PMPVer.:Title:1. Project Management PlanPage #:2 of 17 Revision History[For every revision of this document, provide the revision history that should include the date of revision, version number, description of the changes in the document, and author of the document for that particular version.]Date Version Description Author<dd/mm/yyyy> <x.x> <Details> <Name>Distribution List[State the persons/teams/groups to whom this document should be distributed whenever the document isrevised. Also state the name of their parent organization.]Document Recipient Organization<Role Name> <Organization Name>CMM – Xavor CorporationTitle:1. Project Management PlanPage #:3 of 17 Table of Contents1.Introduction 51.1Purpose 51.2Scope 51.3Definitions, Acronyms and Abbreviations 51.4References 51.5Overview 62.Project Overview 72.1Project Name, Code and Leader 72.2Project Purpose, Scope and Objectives 72.3Assumptions and Constraints 72.3.1Critical Assumptions and Constraints 72.3.2Non-Critical Assumptions and Constraints 72.4Project Milestones 72.5Project Deliverables 72.6Tailoring Guidelines 82.7Software Development Life Cycle 83.Project Organization 93.1Organizational Structure 93.2External Interfaces 113.3Roles and Responsibilities 113.3.1<Organizational Unit Name> 114.Management Process 124.1Work Breakdown Structure (WBS) 124.2Project Estimates 124.2.1Estimation Technique 124.2.2Size 124.2.3Effort 124.3Project Schedule 124.3.1Pre-Development Schedule 124.3.2Development Schedule 124.4Project Phases, Iterations and Releases 124.4.1Project Phases 124.4.2Project Iterations 124.4.3Releases 124.5Project Resourcing 134.5.1Staffing 134.5.2Resource Acquisition 134.5.3Training 134.6Project Budget 13CMM – Xavor CorporationTitle:1. Project Management Plan Page #: 4 of 174.7Project Monitoring and Control 134.7.1Schedule Control 134.7.2Budget Control 134.7.3Measurements 134.8Risk Management Plan 134.9Project Closure 135.Technical Process Plans 145.1User Experience Design 145.2Requirements Management 145.3Analysis and Design 145.4Development Plan 145.5Peer Review Plan 145.6Project Maintenance 145.7Test Plan 145.8Tools, Techniques and Standards 145.8.1Tools 145.8.2Techniques and Standards 155.9Infrastructure 165.10Facilities 165.11Security Plan 166.Supporting Process Plans 166.1Configuration Management Plan 166.2Documentation 166.3Software Quality Assurance Plan 166.4Intergroup Coordination 166.5Communication 166.6Problem Resolution 166.7Subcontractor Management 167.Additional plans 178.Appendices 17CMM – Xavor CorporationTitle:1. Project Management Plan Page #: 5 of 17Project Management Plan1. Introduction[The introduction of the Project Management Plan should provide an overview of the entire document. It should include the purpose, scope, definitions, acronyms, abbreviations, references and overview of this Project Management Plan.]1.1 Purpose[Specify the purpose of this Project Management Plan.]1.2 Scope[A brief description of the scope of this Project Management Plan; what Project(s) it is associated with,and anything else that is affected or influenced by this document.]1.3 Definitions, Acronyms and Abbreviations[This subsection should provide the definitions of all terms, acronyms, and abbreviations required tointerpret properly the Project Management Plan. This information may be provided by reference to the project Glossary.]1.4 References[This subsection should provide a complete list of all documents referenced elsewhere in the ProjectManagement Plan. Each document should be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document. For the Project Management Plan, the list of referenced artifacts may include:•Risk Management Plan•User Interfaces Guidelines•Configuration Management Plan•Software Quality Assurance Plan, etc.]Document Title Publishing Organization<Title> <Organization Name>CMM – Xavor CorporationTitle:1. Project Management Plan Page #: 6 of 171.5 Overview[This subsection should describe what the rest of the Project Management Plan contains and explain how the document is organized.]CMM – Xavor CorporationTitle:1. Project Management Plan Page #: 7 of 172. Project Overview2.1 Project Name, Code and Leader[Specify the project name, project code and project leader (project manager).]Project Name: <Project Name>Project Code: <xxx-xxx>Project Leader: <Name>2.2 Project Purpose, Scope and Objectives[A brief description of the purpose and objectives of this project, and a brief description of whatdeliverables the project is expected to deliver.]2.3 Assumptions and Constraints[A list of assumptions that this plan is based on, and any constraints (e.g. budget, staff, equipment,schedule, etc.) that apply to the project. Make a distinction between critical and non-critical factors.]2.3.1 Critical Assumptions and Constraints[State the critical assumptions and constraints affecting the project.]2.3.2 Non-Critical Assumptions and Constraints[State the non-critical assumptions and constraints affecting the project.]2.4 Project Milestones[Tabular list of major milestones to be achieved during the project, with target dates.]Milestone Target Achievement Date <Milestone Name> <dd/mm/yyyy>2.5 Project Deliverables[Tabular list of the artifacts to be created during the project, with target delivery dates.]Deliverables Target Delivery Date<Deliverable Name> <dd/mm/yyyy>CMM – Xavor CorporationTitle:1. Project Management Plan Page #: 8 of 172.6 Tailoring Guidelines[Specify the tailoring guidelines for the project.]2.7 Software Development Life Cycle[Specify the Software Development Life Cycle that is to be followed in the project.]CMM – Xavor CorporationTitle:1. Project Management Plan Page #: 9 of 173. Project Organization3.1 Organizational Structure[Describe the organizational structure of the project team, including management and other reviewauthorities. This should include identification of all project organizational units and a description of their function and responsibility. A diagram of the organizational structure should also be attached for further illustration.Examples of project organizational units are:•Project Implementation Committee•Project Steering Committee•Project Management Team•Architecture Group•User Experience Design Team•Requirements Team•Analysis and Design Team•Implementation Group•Development Team•Database Management Team•Testing Team•Infrastructure Team•Configuration Management Team•Software Quality Assurance Team, etc.]Organizational Unit Description<Organizational Unit Name> <Description>CMM – Xavor CorporationTitle :1.Project Management Plan Page #:10 of 17Project Team <Project Name>Version: <x.x>Date: <dd/mm/yyyy>Project ManagerProject ManagementTeamProject ArchitectureGroupProjectImplementationGroupUser ExperienceTeamRequirementsTeamSystem Analysis & Design Team System ArchitectureTeam Software DevelopmentTeamTesting TeamDatabase ManagementTeamInfrastructureTeamSoftware ConfigurationTeam Software Quality Assurance TeamCMM – Xavor CorporationTitle:1. Project Management Plan Page #:11 of 173.2 External Interfaces[Describe how the project interfaces with external groups. For each external group, identify the internal/external contact names.]External Organization External Role External RoleHolderResponsibility ofExternal Role HolderInternal ContactRole andPerson<Organization Name> <Role Name> <Role HolderName><Responsibility Details> <Role Name>,<Person Name>3.3 Roles and Responsibilities[Specify the roles, responsibilities and role holders within each organizational unit of the project.]3.3.1 <Organizational Unit Name>Role Responsibility Role Holder<Role Name> <Responsibility Detail> <Role Holder Name>CMM – Xavor CorporationTitle:1. Project Management Plan Page #:12 of 174. Management Process4.1 Work Breakdown Structure (WBS)[List the activities necessary for completing the project.]4.2 Project Estimates4.2.1 Estimation Technique[Specify the estimation method and the reason for its choice. Provide the estimated cost as well as thebasis for those estimates, and the points/circumstances in the project when re-estimation will occur.]4.2.2 Size[State the size of each activity as calculated according to the estimation technique. Units of size may be in LOC, FP, etc.]4.2.3 Effort[Specify the amount of effort required to perform each activity on the basis of the size estimation. Unitsmay be man-hours, man-days, etc.]4.3 Project Schedule[Diagrams/tables showing target dates for completion of iterations and phases, release points, demos, and other milestones. Critical path must be specified. Usually enclosed by reference to MS Project file.]4.3.1 Pre-Development Schedule[This schedule will cater for project planning, requirements, analysis and design activities.]4.3.2 Development Schedule[This schedule will cater coding, testing and deployment activities.]4.4 Project Phases, Iterations and Releases4.4.1 Project Phases[Identify phases and major milestones with their achievement criteria.]4.4.2 Project Iterations[Specify the number of iterations and list the objectives to be accomplished for each of the iterations.]4.4.3 Releases[Brief descriptions of each software release, whether demo, beta, etc.]CMM – Xavor CorporationTitle:1. Project Management Plan Page #:13 of 174.5 Project Resourcing4.5.1 Staffing[Identify here the numbers and type of staff required (including and special skills or experience), scheduled by project phase or iteration. State what resources are critical.]4.5.2 Resource Acquisition[Describe how you will approach finding and acquiring the staff needed for the project.]4.5.3 Training[List any special training project team members will require, with target dates for when this trainingshould be completed.]4.6 Project Budget[Allocation of costs against the WBS and the project phases.]4.7 Project Monitoring and Control4.7.1 Schedule Control[Describes the approach to be taken to monitor progress against the planned schedule and how to takecorrective action when required.]4.7.2 Budget Control[Describes the approach to be taken to monitor spending against the project budget and how to takecorrective action when required.]4.7.3 Measurements[Describe the types of measurements to be taken, their frequency, and responsible workers/entities for this purpose.]4.8 Risk Management Plan[Enclosed by reference]4.9 Project Closure[Describe the activities for the orderly completion of the project, including staff reassignment, archiving of project materials, post-mortem debriefings and reports etc.]CMM – Xavor CorporationTitle:1. Project Management Plan Page #:14 of 175. Technical Process Plans5.1 User Experience Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to befollowed.]5.2 Requirements[Describe the approach that will be adopted with details of processes, procedures, and guidelines to befollowed.]5.3 Analysis and Design[Describe the approach that will be adopted with details of processes, procedures, and guidelines to befollowed.]5.4 Development Plan[Enclosed by reference]5.5 Peer Review Plan[Specify the work products to be peer reviewed, type of peer review, their frequency, etc.]5.6 Maintenance[Describe details of any software maintenance for the warranty period of the project.]5.7 Test Plan[Enclosed by reference]5.8 Tools, Techniques and Standards5.8.1 Tools5.8.1.1 Project Management Tools[Specify the project management tools that are to be used in the project and the reasons for their selection.Examples of areas to be covered are project planning, project scheduling, project monitoring, statusreporting, measurements, etc. Examples of these tools are MS Project, etc.]5.8.1.2 Requirements Management Tools[Specify the requirements management tools that are to be used in the project and the reasons for theirselection. Examples of areas to be covered are requirements gathering, requirement issue resolution,requirement change management, measurements, etc. Examples of these tools are Rational Requisite Pro, EINS, etc.]5.8.1.3 System Analysis & Design Tools[Specify the system analysis and design tools that are to be used in the project and the reasons for theirCMM – Xavor CorporationTitle:1. Project Management Plan Page #:15 of 17selection. Examples of tools in this area are Visio, Rational Rose, Power Designer etc.]5.8.1.4 Languages[Specify the languages that are to be used for software development in the project and the reasons for their selection. Examples of languages are HTML, Java, etc.]5.8.1.5 User-Interface Development Tools[Specify the tools that are to be used for UI development in the project and the reasons for their selection.Examples of these tools can be Dreamweaver, Flash, etc.]5.8.1.6 Database Management System Software[Specify the database management system software that is to be used in the project and the reasons fortheir selection. Examples of these tools are Oracle, SQL Server, etc.]5.8.1.7 Third Party Software[Specify any third party software that is to be used in the project and the reasons for their selection.Examples are Inktomi, Infranet, etc.]5.8.1.8 Software Testing Tools[Specify the software testing tools that are to be used in the project and the reasons for their selection.Examples of these tools are WinRunner, LoadRunner, etc.]5.8.1.9 Defect and Change Management Tools[Specify the defect and change management tools that are to be used in the project and the reasons fortheir selection. Examples of these tools are ClearQuest, etc.]5.8.1.10 Configuration Management Tools[Specify the configuration management tools that are to be used in the project and the reasons for theirselection. Examples of these tools are ClearCase, etc.]5.8.1.11 Integrated Development Environment[Specify the operating systems (platforms), web servers, application servers, development servers that are to be used in the project and the reasons for their selection. Examples of these tools are Sun Solaris,iPlanet, JBuilder, WebSphere, etc.]5.8.2 Techniques and Standards[Lists the documented project technical standards etc by reference. Examples may be:User-Interface GuidelinesProgramming GuidelinesTest Guidelines, etc.]CMM – Xavor CorporationTitle:1. Project Management Plan Page #:16 of 175.9 Infrastructure[Specify hardware, network connectivity, bandwidth, etc., required in this project. Make a clear distinction about what factors are critical.]5.10 Facilities[Describe the facilities required for the execution of the project. This will cover physical workspace,buildings, etc.]5.11 Security Plan[List down the security consideration e.g. of security can be operating system, access controls tosite/product, physical security considerations.]6. Supporting Process Plans6.1 Configuration Management Plan[Enclosed by reference]6.2 Documentation[Specify the documents that will be produced in the project, what document templates will be used, and any other information pertaining to documentation.]6.3 Software Quality Assurance Plan[Enclosed by reference]6.4 Intergroup Coordination[Describe how different project groups will communicate with one another; specify dependencies, andcommitments.]6.5 Communication[Specify how various workers/units/entities, both within and outside the project team, will communicatewith each other.]6.6 Problem Resolution[Describe the approach for resolving issues in the project, escalation procedures, etc.]6.7 Subcontractor Management[If subcontractors are involved in the project give details of what kind of contractors are required forvarious tasks, the duration for which they are required and how they will be managed.]Organization Level Template CMM – Xavor Corporation Document #:XVR.0002/PMPVer.:Title:1. Project Management Plan Page #:17 of 177. Additional plans[Additional plans if required by contract or regulations.]8. Appendices[Attach any supplementary information.]。
工程计划 project 模板一、概述工程计划是项目管理的重要组成部分，它主要用于规划和安排项目的实施过程。
一个完善的工程计划可以帮助项目团队明确目标、合理分配资源、有效控制进度，从而确保项目顺利完成。
为了帮助项目管理者更好地制定和执行工程计划，下面将介绍一套常用的工程计划project 模板。
二、项目概况1. 项目名称：【填写项目名称】2. 项目背景：【简要描述项目的背景和必要性】3. 项目目标：【明确项目的主要目标和预期效果】4. 项目范围：【界定项目的边界，明确包含和不包含的内容】5. 项目时限：【规定项目的开始时间和结束时间】三、项目组织1. 项目发起人：【列出项目的发起人及其通联方式】2. 项目负责人：【指定项目的负责人，并说明其职责】3. 项目成员：【列出项目团队的成员及其分工】四、项目计划1. 项目启动阶段：- 制定项目章程- 确定项目范围- 编制项目计划2. 项目执行阶段：- 分配工作任务- 管理项目进度- 控制项目成本3. 项目收尾阶段：- 评估项目成果- 撰写项目总结报告 - 结束项目合同五、项目资源1. 人力资源：- 项目团队成员- 外包人员2. 物质资源：- 设备设施- 原材料3. 财务资源：- 项目预算- 资金来源六、项目风险1. 技术风险：【具体描述可能出现的技术问题及应对措施】2. 经济风险：【具体描述可能出现的资金问题及应对措施】3. 管理风险：【具体描述可能出现的管理问题及应对措施】七、项目交付1. 交付物标准：【确定项目交付物的标准和验收标准】2. 交付时间：【规定项目交付物的提交时间】3. 交付方式：【确定项目交付物的传递方式和地点】八、项目评估1. 绩效评估：【制定项目绩效评估指标，并进行评估】2. 风险评估：【对项目风险进行定期评估，并提出改进建议】3. 资源评估：【评估项目资源的利用情况，并提出优化建议】九、项目交流1. 内部交流：【规划好项目团队内部的交流机制和频率】2. 外部交流：【与项目相关外部单位或人员的交流计划】十、项目改进1. 问题反馈：【接受来自项目团队和相关方的问题反馈，并及时处理】2. 改进措施：【对已有问题提出改进措施，确保类似问题不再发生】十一、总结工程计划 project 模板是项目管理中的重要工具，它可以帮助项目管理者更好地规划和执行项目，保证项目的顺利进行和成功完成。
PROJECT项目管理案例一、项目概况项目的主要工作是维修某主要道路下一段长约1公里的供水管道，市政局要求电力部门配合施工，同时铺设一条地下电缆，以增加该道路两侧的用电用户。
由于该项目是在现有道路上开挖，故市政局决定在回填后顺便铺设新的混凝土路面。
为此，专门成立了一个项目管理办公室，以管理、协调该项目。
项目内容包括：供水工程、电力工程和道路工程。
整个项目从2010年7月1日提交预算报批为开始，到恢复交通为止。
项目预计建设工期为64天，工程总投资约557790元。
二、项目初始计划参照工程工艺关系、固定成本及所需资源表和项目可用资源(劳动力)数量及费率表，将项目各项任务逻辑关系及固定成本（设备费、材料费和管理费等)、资源需求量信息，输入project文档，得到该项目的实施计划表（表2.1）、甘特图（图2.1）。
表2.1：项目初始计划表由表2.1知，项目总工期为64个工作日，其开始时间为2010年7月1日，完成时间为2010年9月28日。
该项目计划满足市政局希望该项目能在2010年10月底竣工并恢复交通的要求。
图2.1：项目实施甘特图对图2.1分析知，找出该项目实施计划的关键线路：预算报批，对外公告，开走路上停留的车辆，开挖沟槽，维修水管，压力试验，复铺路面，恢复交通。
表2.2项目实施任务分配状况表2.3 资源工作表表2.4 资源使用状况2.1项目总成本的计算：1．固定成本：设备费、材料费和管理费等；2．可变成本：（1）原料费：包括修复路面使用的水泥，石子，沙，各种防水材料，模板等；（2）租赁费：租赁各种设备，包括挖土机，压路机，各种大型的运输车等；（3）施工流动津贴：包括各种由于外界或自身的原因而造成因施工地点的改变而增加的额外的费用；（4）人工费：包括付给监理人员，技工和壮工等的费用；在该项目中，固定成本已经给定，可变成本主要由人工费组成，因而要计算处所有的人工费，其主要包括技工、壮工和管理人员的费用。
