2015-Guo Hui-project overall management + project scope management

Project overall management content, input, output, tools.

2. Project Start-Up (co-book Ring Group of Regulations)

   Input: Contract, project work instruction, environmental and organizational factors, organizational process assets

   Output: Project Charter

   Tools: Project management methodology, project management information system, expert judgment

4. Formulation of the project Scope Specification (Preliminary) (Zhang Group first book)

   Input: Project charter, job description, environmental and organizational factors, organizational process assets

   Output: Project scope Specification (Preliminary)

   Tools: Project management methodology, project management information system, expert judgment

6. Develop project management plan (Zhang, pipe piping and variable control)

   Input: Project charter, project Scope Specification (preliminary), environmental and organizational factors, organizational process assets, other process outputs,

   Job performance information, forecasting

   Output: Project management plan, configuration management System, change control system.

   Tools: Project management methodology, project management information system, expert judgment

8. To guide and manage the execution of the project (corrective and corrective changes, changes in the pre-change and the lack of effect)

   Input: Project management plan, approved corrective action, approved preventative action, approved change request, approved bug fix, confirmed defect fix.

   Outputs: deliverables, request changes, corrective actions implemented, preventive actions implemented, changes implemented, bug fixes implemented, job performance data.

   Tools: Project management methodology, project management Information System

10. Supervise and control the project (Work efficiency and validity report, output correction of pre-change and lack of report)

    Input: Project management plan, job performance information, performance report.

    Output: Deliverable, request for change, 1. Recommended corrective action, 2. Recommended precautions, 3. Recommended bug fixes, project reports.

    Tools: Project management methodology, project management Information System, earned value analysis, expert judgment

12. Overall change control (item tube, please change the performance report, the batch rectification of the lack of delivery)

    Input: Project management plan, application changes, deliverables, job performance information.

    Output: Project management plan (batch), receipt or refusal of change request, approved corrective action, approved preventive measures have been

    Approved bug fixes, deliverables (batches).

    Tools: Project management methodology, project management information system, expert judgment

14. Closure of the project (the collection of the items in the management group, and the production of the garments into a group)

    Input: Project management plan, contract document, organizational process assets

    Output: Management closure method, contract closure method, final product service transfer, organizational process assets (more).

    Tools: Project management methodology, project management information system, expert judgment

Contents of the Project Charter

1. Requirements based on the needs and expectations of the project stakeholders.

2. The business requirements or product requirements that the project must meet.

3. The purpose of the project or the reason for project establishment.

4. Delegated permission levels for project managers and project managers.

5. Overview of Milestone progress plans.

6. The impact of the project stakeholders.

7. Functional organizations and their participation.

8. Organizational, environmental and external assumptions.

9. Organizational, environmental and external constraints.

10. Demonstrate the project's business plan, including ROI.

11. Summary budget.

The control flow of the change. (Moaning and refusing to turn chase)

1. Accept the change request.

2. The overall impact analysis of the change.

3. Receive or reject changes.

4. Execute the change.

5. Tracking and auditing of change results.
   

Project scope management content, input, output, tools.

1. Develop project scope management plan (Xiang group Zhang book, output only Van Yu)

   Input: Project management plan, environmental and organizational factors, organizational process assets, project Charter, project Scope specification (Preliminary)

   Output: Project scope management Plan

   Tools: Expert judgment, templates, forms and standards

2. Scope definition (item tube Change Group Zhang book, output detail book and document)

   Input: Project scope management plan, approved change request, organizational Process assets, project Charter, project Scope specification (Preliminary)

   Output: Project scope specification (detailed), updated project documentation.

   Tools: Expert judgment, product analysis, identification of a number of alternative options.

3. Create a work breakdown structure (item tube Group production and detailed book, Item tube Datum sub-dictionary)

   Input: Project management plan, organizational process assets, project scope specification (detailed)

   Output: Project management plan (more), scope datum, WBS and WBS dictionary.

   Tools: Decomposition, work breakdown structure template, work package format in work breakdown structure, rolling wave plan

4. Scope Confirmation (item tube Fan Shu intersection, completion Change sub-dictionary)

   Input: Project management plan, 1. Project scope specification, 2.WBS and WBS dictionary, deliverable.

   Output: Acceptable project deliverables and work, change requisitions, WBS and WBS dictionaries (more).

   Tools: Checking

5. Scope control (item tube Ergonomics change, change effect group item tube)

   Input: Project management plan, job performance information, performance report, approved change request.

   Output: Change request, job performance, organizational process assets (more), Project management plan (more).

   Tools: Deviation analysis, re-planning, change control system and change Control Committee, configuration management System.

Whether the project scope completes the measurement standard

1. Project Management Plan

2. Project Scope specification

3. WBS and WBS Dictionaries

The main contents of the project scope specification (the perimeter of the boundary of the object of the month leave)

1. Project objectives

2. Product Range Description

3. Project Deliverables

4. Project boundaries

5. Product acceptance Criteria

6. Project constraint conditions

7. Assumptions of the project

What activities are included in the work breakdown of the project

1. Identify and analyze project deliverables and work related to them

2. Structuring and organizing a WBS

3. Grading high-level WBS into a detailed unit of work with low levels

4. Assigning code to work units of a WBS

5. Confirm the extent of the work breakdown is necessary and sufficient

A method for decomposing WBS structures.

1. Project life cycle as the first tier.

2. Project important deliverables as the first tier.

3. Project subproject as the first tier.

Principle of decomposition work structure

Keep project integrity, subordinate upper layer free from cross.

The same level of the same nature, differentiated responsibility and content.

Plan to control the profit management, the bottom job than the tube check.

Including management and subcontracting, the underlying work is the package.

1. Maintain project integrity at all levels to avoid missing the necessary components.

2. Each unit of work is subordinate to an upper unit and avoids cross-dependent.

3. Units of work at the same level should be of the same nature.

4. The unit of work should be able to separate different responsible persons and different work contents.

5. Easy to plan and control the project management needs.

6. The lowest level of work should be comparable, manageable, and quantifiable.

7. Includes management and subcontracting work.

8. The underlying unit of work is a work package.

Range Benchmark

1. Project Scope specification

2. WBS and WBS Dictionaries

Reasons for the change to occur

1. Changes in the external environment of the project

2. The scope plan is not well-developed, error or omission.

3. New technologies, new tools, and solutions

4. The project implementation organization itself has changed

5. The customer's requirements for the project, product or service are changed.

   
   

2015-Guo Hui-project overall management + project scope management