helloc-pmt.weebly.com/uploads/4/0/1/7/4017805/015-project_update.pdf · 4.1 develop project charter...

ni hao

hello

bye

where are you?

Initiating Planning Executing Monitoring & Controlling Closing

Project Management Process Groups

Integration

Scope

Time

Cost

Quality

Human Resources

Communications

Risk

Procurement

Stakeholders

Kno

wle

dge

Are

as

Project

Management

The Planning Process Group

6.1 23 45 6

5. 1234

13.1

4.1 4.2

4.1 Develop Project Charter: authorizes project existence

4.2 Develop Project Management Plan: integrating plans

4.3 Direct and Manage Project Work: leading, performing, implementing

4.4 Monitor and Control Project Work: tracking, reviewing, reporting4.5 Perform Integrated Change Control: reviewing, approving, managing

4.6 Close Project or Phase: finalizing activities

Planning Process Group

Executing Process Group

Initiating Process Group

Closing Process Group

Monitoring & Controlling Process Group

Project Integration Management

66 ©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition

4 - PROJECT INTEGRATION MANAGEMENT

4.1 Develop Project Charter

Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. The key benefit of this process is a well-defined project start and project boundaries, creation of a formal record of the project, and a direct way for senior management to formally accept and commit to the project. The inputs, tools and techniques, and outputs for this process are shown in Figure 4-2. Figure 4-3 depicts the data flow diagram of the process.

Inputs Tools & Techniques Outputs

.1 Project statement of work

.2 Business case

.3 Agreements

.4 Enterprise environmental factors .5 Organizational process assets

.1 Expert judgment

.2 Facilitation techniques .1 Project charter

Figure 4-2. Develop Project Charter: Inputs, Tools and Techniques, and Outputs

Licensed To: Maureen MacDonald PMI MemberID: 2720945This copy is a PMI Member benefit, not for distribution, sale, or reproduction.

13.1 Identify Stakeholders: get ‘em in a register!

13.2 Plan Stakeholder Management: strategies to engage

13.3 Manage Stakeholder Engagement: needs & expectations

13.4 Control Stakeholder Engagement: monitoring relationships






Project Stakeholder Management

393©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition

13 - PROJECT STAKEHOLDER MANAGEMENT

13

13.1 Identify Stakeholders

Identify Stakeholders is the process of identifying the people, groups, or organizations that could impact or be impacted by a decision, activity, or outcome of the project, analyzing and documenting relevant information regarding their interests, involvement, interdependencies, influence, and potential impact on project success. The key benefit of this process is that it allows the project manager to identify the appropriate focus for each stakeholder or group of stakeholders. The inputs, tools and techniques, and outputs of this process are depicted in Figure 13-2. Figure 13-3 depicts the data flow diagram of the process.


.1 Project charter

.2 Procurement documents

.3 Enterprise environmental factors.4 Organizational process assets

.1 Stakeholder analysis

.2 Expert judgment

.3 Meetings

.1 Stakeholder register

Figure 13-2. Identify Stakeholders: Inputs, Tools & Techniques, and Outputs

Project Stakeholder Management

13.1Identify

Stakeholders

13.2Plan

StakeholderManagement

Procurementocuments

P

register

register

O

s

10.1Plan

CommunicationsManagement

12.1Plan

ProcurementManagement

12.1Plan


4.1Develop Project

Charter

5.2Collect

Requirements

8.1Plan QualityManagement

11.1Plan Risk

Management

11.2IdentifyRisks

Enterprise/Organization

Figure 13-3. Identify Stakeholders Data Flow Diagram




Project purpose or justification,

Measurable project objectives and related success criteria,

High-level requirements,

Assumptions and constraints,

High-level project description and boundaries,

High-level risks,

Summary milestone schedule,

Summary budget,

Stakeholder list,

Project approval requirements (i.e., what constitutes project success, who decides the project is successful, and who signs off on the project),

Assigned project manager, responsibility, and authority level, and

Name and authority of the sponsor or other person(s) authorizing the project charter.

4.2 Develop Project Management Plan

Develop Project Management Plan is the process of defining, preparing, and coordinating all subsidiary plans and integrating them into a comprehensive project management plan. The key benefit of this process is a central document that defines the basis of all project work. The inputs, tools and techniques, and outputs for this process are depicted in Figure 4-4. Figure 4-5 depicts the data flow diagram of the process.


.1 Project charter

.2 Outputs from other processes.3 Enterprise environmental factors.4 Organizational process assets

.1 Expert judgment

.2 Facilitation techniques .1 Project management plan

Figure 4-4. Develop Project Management Plan: Inputs, Tools and Techniques, and Outputs


4.1 Develop Project Charter: authorizes project existence

4.2 Develop Project Management Plan: integrating plans

4.3 Direct and Manage Project Work: leading, performing, implementing

4.4 Monitor and Control Project Work: tracking, reviewing, reporting4.5 Perform Integrated Change Control: reviewing, approving, managing

4.6 Close Project or Phase: finalizing activities






Project Integration Management(PMBOK Chapter 4)



4.1 Develop Project Charter

Develop Project Charter is the process of developing a document that formally authorizes the existence of a project and provides the project manager with the authority to apply organizational resources to project activities. The key benefit of this process is a well-defined project start and project boundaries, creation of a formal record of the project, and a direct way for senior management to formally accept and commit to the project. The inputs, tools and techniques, and outputs for this process are shown in Figure 4-2. Figure 4-3 depicts the data flow diagram of the process.


.1 Project statement of work

.2 Business case

.3 Agreements

.4 Enterprise environmental factors .5 Organizational process assets

.1 Expert judgment

.2 Facilitation techniques .1 Project charter

Figure 4-2. Develop Project Charter: Inputs, Tools and Techniques, and Outputs


5.1 Plan Scope Management: defining the scope5.2 Collect Requirements: stakeholder needs5.3 Define Scope: describe scope5.4 Create WBS: scope breakdown






Project Scope Management

5.5 Validate Scope: accepting deliverables5.6 Control Scope: monitor scope


5 - PROJECT SCOPE MANAGEMENT

5

5.1 Plan Scope Management

Plan Scope Management is the process of creating a scope management plan that documents how the project scope will be defined, validated, and controlled. The key benefit of this process is that it provides guidance and direction on how scope will be managed throughout the project. The inputs, tools and techniques, and outputs of this process are depicted in Figure 5-2. Figure 5-3 depicts the data flow diagram of the process.


.1 Project management plan

.2 Project charter


.1 Expert judgment

.2 Meetings.1 Scope management plan.2 Requirements management plan

Figure 5-2. Plan Scope Management: Inputs, Tools & Techniques, and Outputs

5.1Plan Scope

Management

5.2Collect

Requirements

5.3DefineScope

5.4CreateWBS

Project Scope ManagementEnterprise/Organization

4.1Develop Project

Charter

4.2Develop ProjectManagement

Plan

P

Project

R

O

Figure 5-3. Plan Scope Management Data Flow Diagram




5


.1 Scope management plan

.2 Requirements management plan.3 Stakeholder management plan.4 Project charter.5 Stakeholder register

.1 Interviews .2 Focus groups .3 Facilitated workshops .4 Group creativity techniques .5 Group decision-making techniques .6 Questionnaires and surveys .7 Observations .8 Prototypes .9 Benchmarking .10 Context diagrams .11 Document analysis

.1 Requirements documentation.2 Requirements traceability matrix

Figure 5-4. Collect Requirements: Inputs, Tools & Techniques, and Outputs

C g


5.2Collect

Requirements

5.1Plan Scope

Management

5.3DefineScope

5.4CreateWBS

5.5ValidateScope

5.6ControlScope

rR

n

R

Rx

13.1Identify

Stakeholders

13.2Plan

StakeholderManagement

8.1Plan QualityManagement

12.1Plan


4.1 Develop Project

Charter

Figure 5-5. Collect Requirements Data Flow Diagram




5.3 Define Scope

Define Scope is the process of developing a detailed description of the project and product. The key benefit of this process is that it describes the product, service, or result boundaries by defining which of the requirements collected will be included in and excluded from the project scope. The inputs, tools and techniques, and outputs of this process are depicted in Figure 5-7. Figure 5-8 depicts the data flow diagram of the process.



.2 Project charter

.3 Requirements documentation.4 Organizational process assets

.1 Expert judgment

.2 Product analysis

.3 Alternatives generation

.4 Facilitated workshops

.1 Project scope statement

.2 Project documents updates

Figure 5-7. Define Scope: Inputs, Tools & Techniques, and Outputs


5.3DefineScope

5.1Plan Scope

Management

5.2Collect

Requirements

5.4CreateWBS

Organizational

Projectcharter

Requirementsocumentation

Scopemanagementplan

Pscopestatement

Ps

4.1Develop Project

Charter

6.3SequenceActivities

6.5Estimate

Activity Durations

6.6DevelopSchedule

ProjectDocuments


Figure 5-8. Define Scope Data Flow Diagram

42367_ManualPMI5_book-R1.indb 120 3/11/13 4:26 PM




5

5.3.3.2 Project Documents Updates

Project documents that may be updated include, but are not limited to:

Stakeholder register,

Requirements documentation, and

Requirements traceability matrix.

5.4 Create WBS

Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components. The key benefit of this process is that it provides a structured vision of what has to be delivered. The inputs, tools and techniques, and outputs of this process are depicted in Figure 5-9. Figure 5-10 depicts the data flow diagram of the process.



.2 Project scope statement

.3 Requirements documentation.4 Enterprise environmental factors.5 Organizational process assets

.1 Decomposition

.2 Expert judgment .1 Scope baseline.2 Project documents updates

Figure 5-9. Create WBS: Inputs, Tools & Techniques, and Outputs


6.1 Plan Schedule Management - the process for planning

6.2 Define Activities - decompose the WBS into activities

6.3 Sequence Activities - predecessors & successors

6.4 Estimate Activity Resources - who is doing the work?

6.5 Estimate Activity Durations - how long will it take?

6.6 Develop Schedule - put the activities into software

Project Time Management


6 - PROJECT TIME MANAGEMENT

6

Rules of performance measurement. Earned value management (EVM) rules or other physical measurement rules of performance measurement are set. For example, the schedule management plan may specify:

○ Rules for establishing percent complete,

○ Control accounts at which management of progress and schedule will be measured,

○ Earned value measurement techniques (e.g., baselines, fixed-formula, percent complete, etc.) to be employed (for more specific information, refer to the Practice Standard for Earned Value Management) [9],

○ Schedule performance measurements such as schedule variance (SV) and schedule performance index (SPI) used to assess the magnitude of variation to the original schedule baseline.

Reporting formats. The formats and frequency for the various schedule reports are defined.

Process descriptions. Descriptions of each of the schedule management processes are documented.

6.2 Define Activities

Define Activities is the process of identifying and documenting the specific actions to be performed to produce the project deliverables. The key benefit of this process is to break down work packages into activities that provide a basis for estimating, scheduling, executing, monitoring, and controlling the project work. The inputs, tools and techniques, and outputs of this process are depicted in Figure 6-5. Figure 6-6 depicts the data flow diagram of the process.


.1 Schedule management plan.2 Scope baseline.3 Enterprise environmental factors.4 Organizational process assets

.1 Decomposition

.2 Rolling wave planning

.3 Expert judgment

.1 Activity list

.2 Activity attributes

.3 Milestone list

Figure 6-5. Define Activities: Inputs, Tools & Techniques, and Outputs




6

6.1 Plan Schedule Management

Plan Schedule Management is the process of establishing the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule. The key benefit of this process is that it provides guidance and direction on how the project schedule will be managed throughout the project. The inputs, tools and techniques, and outputs of this process are depicted in Figure 6-3. Figure 6-4 depicts the data flow diagram of the process.


.1 Project management plan

.2 Project charter


.1 Expert judgment

.2 Analytical techniques

.3 Meetings

.1 Schedule management plan

Figure 6-3. Plan Schedule Management: Inputs, Tools & Techniques, and Outputs

C g


6.1Plan ScheduleManagement

6.2Define

Activities

6.4Estimate Activity

Resources

6.3SequenceActivities


Durations

6.6DevelopSchedule

O4.2Develop ProjectManagement

Plan

11.2IdentifyRisks

11.4Perform

QuantitativeRisk Analysis

4.1 Develop Project

Charter


Figure 6-4. Plan Schedule Management Data Flow Diagram







6.7 Control Schedule - monitor the project progress153©2013 Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Fifth Edition


6

6.2.3.2 Activity Attributes

Activities, distinct from milestones, have durations, during which the work of that activity is performed, and may have resources and costs associated with that work. Activity attributes extend the description of the activity by identifying the multiple components associated with each activity. The components for each activity evolve over time. During the initial stages of the project, they include the activity identifier (ID), WBS ID, and activity label or name, and when completed, may include activity codes, activity description, predecessor activities, successor activities, logical relationships, leads and lags (Section 6.3.2.3), resource requirements, imposed dates, constraints, and assumptions. Activity attributes can be used to identify the person responsible for executing the work, geographic area, or place where the work has to be performed, the project calendar the activity is assigned to, and activity type such as level of effort (often abbreviated as LOE), discrete effort, and apportioned effort. Activity attributes are used for schedule development and for selecting, ordering, and sorting the planned schedule activities in various ways within reports. The number of attributes varies by application area.

6.2.3.3 Milestone List

A milestone is a significant point or event in a project. A milestone list is a list identifying all project milestones and indicates whether the milestone is mandatory, such as those required by contract, or optional, such as those based upon historical information. Milestones are similar to regular schedule activities, with the same structure and attributes, but they have zero duration because milestones represent a moment in time.

6.3 Sequence Activities

Sequence Activities is the process of identifying and documenting relationships among the project activities. The key benefit of this process is that it defines the logical sequence of work to obtain the greatest efficiency given all project constraints. The inputs, tools and techniques, and outputs of this process are depicted in Figure 6-7. Figure 6-8 depicts the data flow diagram of the process.


.1 Schedule management plan.2 Activity list.3 Activity attributes.4 Milestone list.5 Project scope statement.6 Enterprise environmental factors.7 Organizational process assets

.1 Precedence diagramming method (PDM).2 Dependency determination.3 Leads and lags

.1 Project schedule network diagrams.2 Project documents updates

Figure 6-7. Sequence Activities: Inputs, Tools & Techniques, and Outputs




6


.1 Schedule management plan.2 Activity list.3 Activity attributes.4 Resource calendars.5 Risk register.6 Activity cost estimates.7 Enterprise environmental factors.8 Organizational process assets

.1 Expert judgment

.2 Alternative analysis

.3 Published estimating data

.4 Bottom-up estimating

.5 Project management software

.1 Activity resource requirements.2 Resource breakdown structure.3 Project documents updates

Figure 6-12. Estimate Activity Resources: Inputs, Tools & Techniques, and Outputs


6.4EstimateActivity

Resources

6.2Define

Activities


6.6DevelopSchedule

6.5 Estimate Activity

Durations

A

A

P

A

ProjectDocuments

RA

O

12.2Conduct

Procurements

9.2Acquire

Project Team

11.2IdentifyRisks

7.2Estimate

Costs


12.1Plan


9.1Plan HumanResource

Management

Figure 6-13. Estimate Activity Resources Data Flow Diagram





.1 Schedule management plan .2 Activity list .3 Activity attributes .4 Activity resource requirements .5 Resource calendars .6 Project scope statement .7 Risk register .8 Resource breakdown structure .9 Enterprise environmental factors.10 Organizational process assets

.1 Expert judgment

.2 Analogous estimating

.3 Parametric estimating

.4 Three-point estimating

.5 Group decision-making techniques.6 Reserve analysis

.1 Activity duration estimates.2 Project documents updates

Figure 6-14. Estimate Activity Durations: Inputs, Tools & Techniques, and Outputs


6.5EstimateActivity

Durations


6.2Define

Activities


Resources

6.6DevelopSchedule

A

A

P

A

Activity

ProjectDocuments

O

12.2Conduct

Procurement

9.2Acquire

Project Team

11.2IdentifyRisks

5.3DefineScope


11.2IdentifyRisks

Figure 6-15. Estimate Activity Durations Data Flow Diagram

42367_ManualPMI5_book-R1.indb 166 3/11/13 4:26 PM


-- Project Planning --1) Project Statement of Work2) Project Charter3) Stakeholder Register

-- Project Scope Management --1) Requirements Traceability Matrix2) Project Scope Statement3) Scope Baseline (WBS + WBS Dictionary)

-- Project Time Management --1) Activity list2) Activity attributes3) Milestone list4) Project schedule network diagram5) Activity resource requirements6) Resource breakdown structure7) Activity duration estimate8) Schedule baseline9) Project schedule10) Schedule data11) Project calendars

To Do:

210

@ 5hr/day =

1575

++

++

==

1260

29 days145 hours

Time:

To Do, Today: One-page progress report

See the website for a link to this example

Upload your report to your website by the end of the class today.

Rita Mulcahy’s Pmp Exam Prep Copyright ©2013 RMC Publications, Inc.

Question


Answer


Question


Answer


Question


Answer


Question


Answer


Question


Answer


Question


Answer


Question


Answer


Question


Answer


Question


Answer

tzai jien

hello

bye