Description
purpose of project integration management, what is project charter, project plan elements, project planning methodology, elements of project plan, gantt chart, PERT chart.
Project Integration Management
.
Project Integration Management
?
Purpose: Integration of Resources for coordinating all the work across a project to ensure the right choices and tradeoffs are made, customer needs are met, and the project is ultimately successful.
Project Integration Management
? Coordinate
Project Elements ? Project Plan Development ? Project Plan Execution ? Overall Change Control
Project Integration Management
Also described with following steps: ? Project Charter ? Preliminary Scope Statement ? Project Management Plan ? Project Execution Management, Monitoring, and Control ? Change Control ? Project Close-out
Coordinate Project Elements
?
Process required in integration management ensures that all the various elements of the project are properly coordinated to meet or exceed the stakeholders’ expectations.
? Primary
processes required to integrate the components of the project. ? All project management processes are integrative to some extend.
Project Charter
?
?
? ?
?
? ? ? ?
New Product Business Plan New Project Proposal Business Requirements Document Marketing Requirements Document Opportunity Screening Worksheet Setting Strategic Project Selection Criteria Strategic Project Prioritization Worksheet Project Selection and Controlling Project Starts Project Charter
Project Management Plan
?
? ? ? ?
?
Guide Project Execution Document Assumptions Document Decisions Facilitate Communication Define Management Reviews Baseline For Control
Project Plan Development
?
?
?
Project plan uses output of other planning processes Plan development is an iterative process. Project plan is only a result of the process.
Project Plan
?
? ? ?
?
? ? ? ? ?
Project Charter Management Approach Scope Statement/ Vision Statement Work Breakdown Structure (WBS) Cost Estimates Baselines For Schedules And Cost Major Milestones Key Or Required Staff Risk Management Plan Open Issues
Project Charter
The Project Charter is a high-level, short document created at project initiation to communicate the major parameters of the project the executives have approved to proceed. It summarizes briefly: ? business drivers and justification ? scope, schedule, cost targets ? high-level resource needs ? key roles assigned for the project (sponsor and project manager)
Preliminary Scope Management
Project Scope Definition: Vision Document ? Introduction to Software Release Trains ? Software Release Life Cycle Overview
?
? SDLC
for typical software projects
?
Project Planning Techniques Brief
? Agile
Technique Brief: Agile Planning ? Waterfall / Iterative/ V - Process
Project Vision
A brief document created by a team in the early days of a project. ? The project vision builds the case for doing a project, negotiates the overall scope and requirements at the highest customerfocused level, and obtains team alignment and captures agreement on the project definition.
?
Project Plan Elements
? ? ? ? ? ? ? ? ? ? ?
Project Definition - Overview (Scope), Requirements Objectives - Statement of Work, General Approach Specifications Budget/ Schedule Organization and Systems - Responsibility, Communication, Reporting, Decision Making Human Resources and Other Resources Logistics and Support Contracting & Procurement - - With Client, Subcontractor, Vendors Design, Development, Construction Testing and Evaluation Methods Potential Problems - Risks, Events
Project Plan Evolves From..
?
? ? ?
?
? ? ?
?
?
Executive Summary Program Plan Management Approach Acquisition Plan Implementation Plan (Schedules) Budget and Resources Plan Test (Validation and Verification) Plan Deployment Plan Acceptance Plan Deactivation / Closure Plan
Other Inputs
? ?
?
?
Historical information ? Estimation database, performance database Organizational policies ? Quality management – process improvement goals ? Personnel administration – performance reviews ? Financial controls – required expenditure reviews, accounting codes Constraints ? Factors that will limit the project team’s options. ? Predefined schedule or budget ? Contractual provisions Assumptions ? Factors, for the purpose of planning considered to be true. ? The date a key hardware will become available may be assumed ? Assumptions generally involve a degree of risk
Tools and Techniques
?
Project planning methodology
? Structured
approach to guide the project team during plan development. ? Can be as simple as forms and templates
?
Planning methodologies include
? Representation
techniques and notations ? Planning process ? Planning heuristics
A project Planning methodology
?
Scope the project
? Create
a draft project overview statement (POS) by means of a Joint Project Planning Session ? JPPP should involve the customer, the project manager and key members of the project team.
?
? ? ? ?
Problem / opportunity Project goal Project objectives Success criteria Assumptions, risks, obstacles
? ?
POS approval Create the project definition statement
Project Planning Methodology
Identify project activities ? Estimate activity duration, resource requirements and costs ? Construct and analyze the project network diagram ? Finalize the schedule based on resource availability
?
Tools and Techniques
?
Stakeholder skills and knowledge
? Who,
when and what ? Project planning team should determine the answers
?
Project management information system
?A
system to gather, integrate and disseminate outputs of project management processes
?
Thank You…
Outputs…
Project plan ? Formal, approved document to manage project execution. ? Project plan is expected to change overtime as more information becomes available. ? Project schedule lists planned dates for performing activities and meeting milestones identified in the project plan. ? Performance measurement baseline change only in response to an approved scope change.
Project Plan Includes
?
Project plan includes:
? ? ? ? ? ? ? ? ? ? ? ?
Project charter Project management approach Scope statement (deliverables and objectives) Work breakdown structure as a baseline scope document Cost estimates, schedules, start dates and responsibility assignment appropriate with the WBS Performance measurement baselines for schedule, cost and scope. Major milestones and their target dates Key or required staff Risk management plan: Key risks and planned responses for each Subsidiary management plans: Scope, schedule, cost, quality, staffing, communications, procurement. Open issues and pending decisions Other project planning outputs as necessary
Outputs… samples
Risk Management Matrix (Example)
Initial Risk Impact Risk Description Management Strategy Prototype User Interface Early Involve Real Users (Prototype) Set Up Project Review Meetings and Newsletter Residual Risk
H
H
Human Interaction and Interfaces Extensive and Unknown
M/L
M
H
Project Communications
L
H
L
Any High Risk
ELIMINATE
NONE
H
H/M
Any High Risk
NO MATTER WHAT STRATEGY
H
PERT Chart
Theme 7 Thu 6/2/94 2d Fri 6/3/94 Date 8 Mon 6/6/94 3d Wed 6/8/94 Site 9 Thu 6/9/94 1w Wed 6/15/94 Costumes 10 1w
Thu 6/16/94 Wed 6/22/94
Invitation list 5 Wed 6/1/94 1d Wed 6/1/94
Hire 11 168h
Thu 6/23/94 Thu 7/21/94
Determine budget 4 Wed 6/1/94 1d Wed 6/1/94
Selection 6 Thu 6/2/94 120h Wed 6/22/94
Public relations 15 Fri 7/22/94 88h Fri 8/5/94
Rent Equipment 18 Mon 8/8/94 40h Fri 8/12/94
Caterer 12 2d
Entertainment 13 9d
Keynote speaker 14 Fri 7/8/94 2w Thu 7/21/94
Thu 6/23/94 Fri 6/24/94
Mon 6/27/94 Thu 7/7/94
Resource Loading
T 1.6 May 29, '94 W T F S S M T Jun 5, '94 W T F S S M T Jun 12, '94 W T F S S M T Jun 19, '94 W T F
1.4
1.2
1.0
0.8
0.6
0.4
0.2
Peak Units:
1
1
1
0.75
0.75
0.75
0.75
1.5
1.5
1.5
1.5
0.5
0.5
0.5
0.5
0.5
0.5
0.5
R02
Overallocated:
Allocated:
Project Plan Execution
? ?
Majority of project’s budget is expended. Product of the project is created by this process.
? ?
Directly effected by application area Technical and managerial interfaces must be coordinated
?
Performance against the baseline should be monitored
Inputs…
? ?
Project plan
? Including
other plans.
design documents
Supporting detail
? Specification, ? Standards
?
Organizational policies
? Formal
and informal policies used by the project units effect the execution
?
Corrective / preventive action
? An
output of all control processes. ? Completes the feedback loop for effective project management.
Tools and Techniques
?
General management skills
? Leadership,
communicating, negotiating are
essential.
?
Product skills and knowledge
? Solution
domain – software engineering domain knowledge and skills
?
Problem domain – knowledge and skills related with the problem area
Tools and Techniques
? ?
General management skills ? Leadership, communicating, negotiating are essential. Product skills and knowledge ? Solution domain – software engineering domain knowledge and skills
?
Problem domain – knowledge and skills related with the problem area
Tools and Techniques
?
Work authorization system
? ? ?
A formal procedure for authorizing project work Written authorization to begin work on a specific activity or work package Value of the control should be balanced with the cost of the control Regularly scheduled meetings to exchange information.
? ? ?
Status review meetings
?
Project management information system Organizational procedures
?
Formal and informal procedures for units involved in the project are useful
Output…
?
Work results
? Outcomes
of the activities performed to accomplish
the project
? ? ?
Software requirements specification report Software design report Software test report
? Information
on work products – cost, quality, time is an input to performance reporting process time, cost usually identified during execution
?
Change requests
? Scope,
Integrated Change Control
?
Concerns
? Influencing
factors that create change to ensure changes are beneficial. ? Determining that change has occurred. ? Managing the actual changes
Integrated Change Control
Integrated Change Control
Inputs
? ?
Project plan
? Establishes
? Provide
the baseline
Performance reports
information on project performance.
?
Change request
? Occur
?
in many forms
Written and oral ? Direct or indirect ? Externally or internally initiated ? Legally mandated or optional
Tools and Techniques
?
Change control system
? Formal,
documented procedures for changing official project documents ? Includes paperwork, tracking systems, authorization mechanisms ? Usually include a change control board (CCB) to approve or reject change requests. ? Must include procedures to handle changes without prior review.
Tools and Techniques
?
Configuration management
? Formal
? ?
documented procedure to apply technical and administrative direction to:
Identify and document the functional and physical characteristics of an item or system. Control any changes to such characteristics. Record and report the change and its implementation status. Audit the items and system to verify conformance to requirements.
?
?
?
Performance measurement
? Enable
to assess whether variances require corrective action.
? ?
Additional planning Project management information system
Output
?
Project plan updates
? Any
modifications to the contents of the project plan and supporting detail. ? Appropriate stakeholders should be notified.
Corrective action ? Lessons learned ? The root causes, reasoning for corrective action should be documented for short term and long term use.
?
Thank You…
?
Thank You…
Agile Planning
?
? ?
This technique is an iterative and feature-based approach to project planning Agile planning is feature-based, iterative, owned by the team, and uses different levels of detail. These characteristics provide teams an opportunity to get rapid feedback on their designs and processes, apply learning from past experiences quickly, and keep their project plans simple, but effective.
Agile Planning
?
?
?
Provides project teams with a means to produce features in a short amount of time in order to gain useful feedback from users, customers, and stakeholders. It also allows teams to defer decisions on detailed requirements until the feature is being developed, allowing them to apply the most current and accurate information possible. This approach works when the team has decided to follow an iterative and incremental project approach and is most useful in situations where the product of the project can be delivered in small increments
Project Life Cycle
Project Life Cycle Sequential Model
Planning Definition Design Implementation Integration System Test Operation
Phased (Waterfall) Model
Planning Definition Design Implementation Integration Time System Test
Shortened Interval
Earlier Time-to-Market
Operation
doc_719657004.ppt
purpose of project integration management, what is project charter, project plan elements, project planning methodology, elements of project plan, gantt chart, PERT chart.
Project Integration Management
.
Project Integration Management
?
Purpose: Integration of Resources for coordinating all the work across a project to ensure the right choices and tradeoffs are made, customer needs are met, and the project is ultimately successful.
Project Integration Management
? Coordinate
Project Elements ? Project Plan Development ? Project Plan Execution ? Overall Change Control
Project Integration Management
Also described with following steps: ? Project Charter ? Preliminary Scope Statement ? Project Management Plan ? Project Execution Management, Monitoring, and Control ? Change Control ? Project Close-out
Coordinate Project Elements
?
Process required in integration management ensures that all the various elements of the project are properly coordinated to meet or exceed the stakeholders’ expectations.
? Primary
processes required to integrate the components of the project. ? All project management processes are integrative to some extend.
Project Charter
?
?
? ?
?
? ? ? ?
New Product Business Plan New Project Proposal Business Requirements Document Marketing Requirements Document Opportunity Screening Worksheet Setting Strategic Project Selection Criteria Strategic Project Prioritization Worksheet Project Selection and Controlling Project Starts Project Charter
Project Management Plan
?
? ? ? ?
?
Guide Project Execution Document Assumptions Document Decisions Facilitate Communication Define Management Reviews Baseline For Control
Project Plan Development
?
?
?
Project plan uses output of other planning processes Plan development is an iterative process. Project plan is only a result of the process.
Project Plan
?
? ? ?
?
? ? ? ? ?
Project Charter Management Approach Scope Statement/ Vision Statement Work Breakdown Structure (WBS) Cost Estimates Baselines For Schedules And Cost Major Milestones Key Or Required Staff Risk Management Plan Open Issues
Project Charter
The Project Charter is a high-level, short document created at project initiation to communicate the major parameters of the project the executives have approved to proceed. It summarizes briefly: ? business drivers and justification ? scope, schedule, cost targets ? high-level resource needs ? key roles assigned for the project (sponsor and project manager)
Preliminary Scope Management
Project Scope Definition: Vision Document ? Introduction to Software Release Trains ? Software Release Life Cycle Overview
?
? SDLC
for typical software projects
?
Project Planning Techniques Brief
? Agile
Technique Brief: Agile Planning ? Waterfall / Iterative/ V - Process
Project Vision
A brief document created by a team in the early days of a project. ? The project vision builds the case for doing a project, negotiates the overall scope and requirements at the highest customerfocused level, and obtains team alignment and captures agreement on the project definition.
?
Project Plan Elements
? ? ? ? ? ? ? ? ? ? ?
Project Definition - Overview (Scope), Requirements Objectives - Statement of Work, General Approach Specifications Budget/ Schedule Organization and Systems - Responsibility, Communication, Reporting, Decision Making Human Resources and Other Resources Logistics and Support Contracting & Procurement - - With Client, Subcontractor, Vendors Design, Development, Construction Testing and Evaluation Methods Potential Problems - Risks, Events
Project Plan Evolves From..
?
? ? ?
?
? ? ?
?
?
Executive Summary Program Plan Management Approach Acquisition Plan Implementation Plan (Schedules) Budget and Resources Plan Test (Validation and Verification) Plan Deployment Plan Acceptance Plan Deactivation / Closure Plan
Other Inputs
? ?
?
?
Historical information ? Estimation database, performance database Organizational policies ? Quality management – process improvement goals ? Personnel administration – performance reviews ? Financial controls – required expenditure reviews, accounting codes Constraints ? Factors that will limit the project team’s options. ? Predefined schedule or budget ? Contractual provisions Assumptions ? Factors, for the purpose of planning considered to be true. ? The date a key hardware will become available may be assumed ? Assumptions generally involve a degree of risk
Tools and Techniques
?
Project planning methodology
? Structured
approach to guide the project team during plan development. ? Can be as simple as forms and templates
?
Planning methodologies include
? Representation
techniques and notations ? Planning process ? Planning heuristics
A project Planning methodology
?
Scope the project
? Create
a draft project overview statement (POS) by means of a Joint Project Planning Session ? JPPP should involve the customer, the project manager and key members of the project team.
?
? ? ? ?
Problem / opportunity Project goal Project objectives Success criteria Assumptions, risks, obstacles
? ?
POS approval Create the project definition statement
Project Planning Methodology
Identify project activities ? Estimate activity duration, resource requirements and costs ? Construct and analyze the project network diagram ? Finalize the schedule based on resource availability
?
Tools and Techniques
?
Stakeholder skills and knowledge
? Who,
when and what ? Project planning team should determine the answers
?
Project management information system
?A
system to gather, integrate and disseminate outputs of project management processes
?
Thank You…
Outputs…
Project plan ? Formal, approved document to manage project execution. ? Project plan is expected to change overtime as more information becomes available. ? Project schedule lists planned dates for performing activities and meeting milestones identified in the project plan. ? Performance measurement baseline change only in response to an approved scope change.
Project Plan Includes
?
Project plan includes:
? ? ? ? ? ? ? ? ? ? ? ?
Project charter Project management approach Scope statement (deliverables and objectives) Work breakdown structure as a baseline scope document Cost estimates, schedules, start dates and responsibility assignment appropriate with the WBS Performance measurement baselines for schedule, cost and scope. Major milestones and their target dates Key or required staff Risk management plan: Key risks and planned responses for each Subsidiary management plans: Scope, schedule, cost, quality, staffing, communications, procurement. Open issues and pending decisions Other project planning outputs as necessary
Outputs… samples
Risk Management Matrix (Example)
Initial Risk Impact Risk Description Management Strategy Prototype User Interface Early Involve Real Users (Prototype) Set Up Project Review Meetings and Newsletter Residual Risk
H
H
Human Interaction and Interfaces Extensive and Unknown
M/L
M
H
Project Communications
L
H
L
Any High Risk
ELIMINATE
NONE
H
H/M
Any High Risk
NO MATTER WHAT STRATEGY
H
PERT Chart
Theme 7 Thu 6/2/94 2d Fri 6/3/94 Date 8 Mon 6/6/94 3d Wed 6/8/94 Site 9 Thu 6/9/94 1w Wed 6/15/94 Costumes 10 1w
Thu 6/16/94 Wed 6/22/94
Invitation list 5 Wed 6/1/94 1d Wed 6/1/94
Hire 11 168h
Thu 6/23/94 Thu 7/21/94
Determine budget 4 Wed 6/1/94 1d Wed 6/1/94
Selection 6 Thu 6/2/94 120h Wed 6/22/94
Public relations 15 Fri 7/22/94 88h Fri 8/5/94
Rent Equipment 18 Mon 8/8/94 40h Fri 8/12/94
Caterer 12 2d
Entertainment 13 9d
Keynote speaker 14 Fri 7/8/94 2w Thu 7/21/94
Thu 6/23/94 Fri 6/24/94
Mon 6/27/94 Thu 7/7/94
Resource Loading
T 1.6 May 29, '94 W T F S S M T Jun 5, '94 W T F S S M T Jun 12, '94 W T F S S M T Jun 19, '94 W T F
1.4
1.2
1.0
0.8
0.6
0.4
0.2
Peak Units:
1
1
1
0.75
0.75
0.75
0.75
1.5
1.5
1.5
1.5
0.5
0.5
0.5
0.5
0.5
0.5
0.5
R02
Overallocated:
Allocated:
Project Plan Execution
? ?
Majority of project’s budget is expended. Product of the project is created by this process.
? ?
Directly effected by application area Technical and managerial interfaces must be coordinated
?
Performance against the baseline should be monitored
Inputs…
? ?
Project plan
? Including
other plans.
design documents
Supporting detail
? Specification, ? Standards
?
Organizational policies
? Formal
and informal policies used by the project units effect the execution
?
Corrective / preventive action
? An
output of all control processes. ? Completes the feedback loop for effective project management.
Tools and Techniques
?
General management skills
? Leadership,
communicating, negotiating are
essential.
?
Product skills and knowledge
? Solution
domain – software engineering domain knowledge and skills
?
Problem domain – knowledge and skills related with the problem area
Tools and Techniques
? ?
General management skills ? Leadership, communicating, negotiating are essential. Product skills and knowledge ? Solution domain – software engineering domain knowledge and skills
?
Problem domain – knowledge and skills related with the problem area
Tools and Techniques
?
Work authorization system
? ? ?
A formal procedure for authorizing project work Written authorization to begin work on a specific activity or work package Value of the control should be balanced with the cost of the control Regularly scheduled meetings to exchange information.
? ? ?
Status review meetings
?
Project management information system Organizational procedures
?
Formal and informal procedures for units involved in the project are useful
Output…
?
Work results
? Outcomes
of the activities performed to accomplish
the project
? ? ?
Software requirements specification report Software design report Software test report
? Information
on work products – cost, quality, time is an input to performance reporting process time, cost usually identified during execution
?
Change requests
? Scope,
Integrated Change Control
?
Concerns
? Influencing
factors that create change to ensure changes are beneficial. ? Determining that change has occurred. ? Managing the actual changes
Integrated Change Control
Integrated Change Control
Inputs
? ?
Project plan
? Establishes
? Provide
the baseline
Performance reports
information on project performance.
?
Change request
? Occur
?
in many forms
Written and oral ? Direct or indirect ? Externally or internally initiated ? Legally mandated or optional
Tools and Techniques
?
Change control system
? Formal,
documented procedures for changing official project documents ? Includes paperwork, tracking systems, authorization mechanisms ? Usually include a change control board (CCB) to approve or reject change requests. ? Must include procedures to handle changes without prior review.
Tools and Techniques
?
Configuration management
? Formal
? ?
documented procedure to apply technical and administrative direction to:
Identify and document the functional and physical characteristics of an item or system. Control any changes to such characteristics. Record and report the change and its implementation status. Audit the items and system to verify conformance to requirements.
?
?
?
Performance measurement
? Enable
to assess whether variances require corrective action.
? ?
Additional planning Project management information system
Output
?
Project plan updates
? Any
modifications to the contents of the project plan and supporting detail. ? Appropriate stakeholders should be notified.
Corrective action ? Lessons learned ? The root causes, reasoning for corrective action should be documented for short term and long term use.
?
Thank You…
?
Thank You…
Agile Planning
?
? ?
This technique is an iterative and feature-based approach to project planning Agile planning is feature-based, iterative, owned by the team, and uses different levels of detail. These characteristics provide teams an opportunity to get rapid feedback on their designs and processes, apply learning from past experiences quickly, and keep their project plans simple, but effective.
Agile Planning
?
?
?
Provides project teams with a means to produce features in a short amount of time in order to gain useful feedback from users, customers, and stakeholders. It also allows teams to defer decisions on detailed requirements until the feature is being developed, allowing them to apply the most current and accurate information possible. This approach works when the team has decided to follow an iterative and incremental project approach and is most useful in situations where the product of the project can be delivered in small increments
Project Life Cycle
Project Life Cycle Sequential Model
Planning Definition Design Implementation Integration System Test Operation
Phased (Waterfall) Model
Planning Definition Design Implementation Integration Time System Test
Shortened Interval
Earlier Time-to-Market
Operation
doc_719657004.ppt