{ 项目名称 }

项目立项报告

版本历史

目录

项目立项报告... 1

1.     项目概述... 6

1.1.      项目定义及价值（收入增长、成本节约、客户满意度提高）... 6

1.2.      项目开发背景... 6

1.3.      项目主要功能和特色... 6

1.4.      项目范围... 6

2.     市场概述... 6

2.1.      客户需求... 6

2.2.      竞争对手... 7

2.3.      市场规模与发展趋势... 7

3.     项目发展目标... 7

4.     项目技术方案... 7

4.1.      项目体系结构... 7

4.2.      关键技术... 7

5.     项目优缺点分析... 7

6.     项目的风险分析和应对措施... 8

7.     Make-or-Buy决策... 8

8.     项目计划... 8

8.1.      项目团队... 8

8.2.      软件硬件资源估计... 8

8.3.      成本估计... 9

8.4.      进度表... 9

9.     市场营销计划... 9

9.1.      项目赢利模式和销售目标... 9

9.2.      促销和渗透方式... 10

9.3.      销售方式和渠道... 10

10.       成本效益分析... 10

11.       总结... 10

12.       评审意见：... 11

 

1.   项目概述

1.1. 项目定义及价值（收入增长、成本节约、客户满意度提高）

提示：用简练的语言说明本项目“是什么”，“什么用途”。根据经验，概念罗嗦含糊的项目很难被用户接受。所以项目定义一定要简练且清晰。

1.2. 项目开发背景

提示：从内因、外因两方面阐述项目开发背景，重点说明“为什么”要开发本项目。

（1）因方面着重考虑：开发方的短期、长期发展战略；开发方的当前实力。

（2）外因方面着重考虑：市场需求及发展趋势；技术状况及发展趋势。

（3）如果是合同项目，请说明项目的来源。

1.3. 项目主要功能和特色

提示：

（1）给出项目的主要功能列表（Feature Lists）。

（2）说明本项目的特色。

1.4. 项目范围

提示：

（1）说明本项目“适用的领域”和“不适用的领域”。

（2）说明本项目“应当包含的内容”和“不包含的内容”。

2.   市场概述

2.1. 客户需求

提示：

（1）阐述本项目面向的消费群体（客户）的特征

（2）说明客户对项目的功能性需求和非功能性需求

（3）说明本项目如何满足客户的需求，以及给客户带来什么好处。

2.2. 竞争对手

2.3. 市场规模与发展趋势

提示：

（1）分析市场发展历史与发展趋势，说明本项目处于市场的什么发展阶段。

（2）本项目和同类项目的价格分析

（3）统计当前市场的总额、竞争对手所占的份额，分析本项目能占多少份额。

注意：引用数据应当写明数据来源，最好有直观的图表。

3.   项目发展目标

提示：说明本项目的短期目标和长期目标，绘制项目的Roadmap。目标必须清晰并且可以度量。

4.   项目技术方案

4.1. 项目体系结构

提示：

（1）绘制项目的体系结构

（2）阐述设计原理

（3）如果有多种体系结构，需比较优缺点。

4.2. 关键技术

提示：阐述本项目的关键技术，评价技术实现的难易程度

5.   项目优缺点分析

提示：综合考虑本项目的功能、质量、价格、品牌等因素，分析优缺点。

6.   项目的风险分析和应对措施

7.   Make-or-Buy决策

提示：

             确定哪些项目部件应当采购、外包开发或者自主研发，说明理由。

（2）分析相应的风险。

8.   项目计划

8.1. 项目团队

提示：说明项目团队的角色、知识技能要求、建议人选、人数、工作时间，如下表所示。

8.2. 软件硬件资源估计

提示：

（1）估计项目所需的软件和硬件资源，说明主要配置。

（2）说明以何种方式获得，如“已经存在”、“可以借用”或“需要购买”等。

（3）资源的级别为“关键”、“普通”两种，如果关键资源不能及时到位，可能危害项目。

8.3. 成本估计

提示：估计项目的“人力资源成本”、“软硬件资源成本”、“商务活动成本”等等。

8.4. 进度表

提示：绘制项目开发的进度表（建议用Gantt图）

9.   市场营销计划

9.1. 项目赢利模式和销售目标

提示：

（1）给出项目的赢利模式和价格结构

（2）给出短期和长期销售目标

9.2. 促销和渗透方式

提示：常见的促销和渗透方式有

²  出版书籍，树立权威。

²  建立网站，用户可以下载项目试用版和一些资料。

²  在各大学BBS或专业性的论坛网站上宣传。

²  到一些专业性报纸、杂志、网站上上做广告。

²  将项目试用版和资料赠送给老客户和潜在客户。

²  参加专业性的会展、研讨会，宣传项目。

²  通过朋友联系潜在客户，推销项目。

²  与政府、行业协会合作推广。

9.3. 销售方式和渠道

提示：常见的销售方式和渠道有

²  直销。本公司有关人员和客户直接联系，销售项目。

²  代理商或办事处。除公司所在地以为，在其他 IT 发达的大城市寻找代理商。当公司业务在该地区达一定规模后，设立办事处。

²  个人销售。个人推销本公司的项目，促成交易者，给予销售提成。

²  联盟。与其他相关公司合作或联盟，实现优势互补，争取更多的客户。

10.          成本效益分析

提示：

（1）总成本是项目开发、营销、维护的成本之和；

（2）效益包括“可量化的经济效益”和“不可量化的好处”。

11.          总结

提示：给出清晰的结论，便于上级领导决策。

12.          评审意见：

1、分管高管意见

2、总经理评审意见

第二篇：项目立项报告模板

Project Charter Template

---

---

Components

1. Executive Summary

Write a few paragraphs describing at a high level the key elements of the project that are detailed throughout the charter.

2. Strategic Alignment

1.      Specific Strategic Initiatives
Answer the questions: What university initiatives does this project support? What are the expected outcomes or benefits (impact on processes, systems, people, organizations)?

2.      Project Stakeholders
Who are the customers and sponsors?

3. Project Definition

1.      Mission
State the purpose of the project.

2.      Objectives
Clearly state 1-2 project objectives that are concise, verifiable, feasible, and measurable.

3.      Scope/Major Deliverables
The project deliverables define the products/services that are produced by the project and clearly state what is not produced by the project. Deliverables not included may be those constructed in a later project phase, or those to be constructed by another project.

Be as clear as possible in defining the project deliverables. Clear and obtainable deliverables set the direction of the project and eliminate confusion about what work is performed and what products/services are delivered.

4.      Quality Specifications
Describe the product or service performance criteria from a customer perspective.

5.      Assumptions
Project assumptions clarify gray areas in the project scope. Any known assumptions that have been made regarding the project that may influence this agreement should be noted.

Note: Assumptions are made to fill knowledge gaps; they may later prove to be incorrect and can have a significant impact on the project. List only those assumptions that have a reasonable chance of occurring.

6.      Constraints
List any known constraints imposed by the environment or by management. Typical constraints may include fixed budget; limited resources; imposed interim and/or end dates; predetermined software systems and packages; and other predetermined solutions.

7.      Human Resource Requirements
Define the project team's organizations, roles and responsibility requirements. Provide a description of major participants including the various internal and external organizations.

8.  If necessary, identify training requirements and begin to develop the Project Team Training Plan to be finalized after detailed planning. Training includes:

§  Technical training relevant to the project domain (e.g. IT development, procurement, logistics, systems training, etc.)

§  Team Training (e.g. team building, team effectiveness, team performance, consensus decision making, etc.)

§  Project Management (e.g. project management concepts)

§  Procedures/user manuals, training liaison, etc. needed for/by business users.

9.      Material/Equipment Procurement
Include information regarding the lease or procurement of required equipment and materials.

10.  Milestones
Define the milestone schedule of the project, integrating three key elements: deliverables, due date or duration, critical dependencies.

11.  Preliminary Budget/Cost Estimate
This estimate is prepared at a gross level for the project charter. Estimates are typically prepared for:

§  the duration of the project

§  the human resource requirements in terns of numbers and types of skills required on the team

§  the cost of performing the work defined in the project charter

§  the material and equipment resources in terms of quantity and duration.

Decisions to proceed with the project could be based on this information. Therefore, it is important to ensure that it is as accurate and realistic as possible. The objective here is to gain approval of the Project Charter as quickly as possible without developing project details.

As the project traverses through the stages outlined in the methodology, more information will be known and unpredictability will be reduced. Therefore, at the end of each stage and after detailed planning for the next phase, the cost/benefit analysis is updated and the information communicated as needed.

Good estimates require:

§  time and focus

§  historical information or previous experience

§  multiple, consistent estimating methods

§  knowledge of the work

Costs are divided into three types:

9.      Capital Items: associated with the procurement of assets that are capitalizable such as hardware and software

10.  Expense Items: associated with operating expenses, material, travel, training, supplies, books, copying, printing, etc.

11.  Labor: associated with the total time team members work on a project based on an hourly rate for each skill set or the actual salary of the team members

12.  Major Overall Risks
Identify and assess known project risks.

13.  Information Requirements
Describe the system of communications and the project performance documentation that will be provided to the various stakeholders.

4. Related Products and Deliverables

Document known project dependencies with other groups within or outside of the organization.

5. Approvals

Use this section to capture approval signatures from project stakeholders.

6. Attachments

Include in this section copies of pertinent documents such as:

o    Business Case or Plan that initiated the project

o    University guidelines or policies applicable to this project