Project integration management

Project integration management – Mindmap

One of the key roles of the project manager is to perform project integration throughout the project.

  • IPD – Integrated Project Delivery is the emerging trend in project management
  • It’s emphasis is on collaborative teams working together from the contracting phase till the project completion
  • Project teams comprises of teams of different disciplines and they develop their plans (subsidiary plans)  like;
    • Engineering -> Engineering plan
    • Construction -> Construction plan
    • Quality -> Quality management plan
    • Procurement -> Procurement management plan
    • Risk management -> Risk management plan
    • Resourcing – > Resource management plan
    • Communications -> Communications management plan
    • Owner / Architect / Business analysts – Requirements / Scope management plan
  • These efforts can be further distributed among Owners, Architects, Contractors, Sub-contractors and Suppliers
  • Project integration management comprises of integrating the efforts of all these different disciplines towards the accomplishment of project goals of Time, Cost and Scope throughout the project management life cycle of;
    • Initiation
      • Develop project charter
    • Planning 
      • Develop project management plan
    • Execution
      • Direct and manage project work
      • Manage project knowledge
    • Monitoring & Controlling 
      • Monitor and control project work
      • Perform integrated change control
    • Closing 
      • Close project / phase

Data dictionary for Project Integration Management 

  • Business case – Investment, Return on investment (ROI), Payback period
  • Benefits management plan – How the benefits from the project will be measured and compared against the benefits forecast made initially to justify the project.
  • Agreements – Signed between the owner , contractor, sub-contractor, Architect
  • Enterprise environmental factors ;
    • Government / industry standards
    • Legal requirements
    • Market conditions
    • Culture, politics
    • Organizational types
      • Functional
      • Matrix
        • Weak matrix
        • Strong matrix
        • Balanced matrix
      • Projectized
      • Composite
  • Organizational process assets 
    • Standards, policies, guidelines
    • Quality management systems
    • Portfolio, program, project governance framework
    • Historical data
    • Re-usable components
  • Expert judgment – Judgment by experts in the specific field
  • Brainstorming – Idea generation technique used in groups. Governed by a moderator. People are encouraged to come out with their ideas. At the time of idea generation, there is no validation of the ideas.
  • Focus groups – Task force to address any specific problem
  • Conflict management – To eliminate conflicts across stakeholders to arrive at decisions related to the project
  • Facilitation – Ability to effectively guide
  • Meeting management – Agenda, timeliness, action items, meeting norms, minutes of the meeting, follow up
  • Project charter 
    • Document owned and approved the project sponsor / management representative
    • Prepared during initiation phase
    • Authorizes the project manager
    • Contains;
      • Project purpose
      • Measurable project objectives
      • High level scope
      • High level risks
      • Milestone schedule
      • Key stakeholder list, their roles and responsibilities
      • Project approval criteria
      • Project exit criteria
      • Assigned project manager, roles and responsibilities
        • Authorizes the project manager
        • Provides authority to the project manager
      • Name and authority of the approving authority of the charter
  • Assumption log – Log of assumptions made while starting the project like
    • Manpower availability
    • Climatic conditions
    • Raw material availability and cost
    • Transportation facilities
  • Checklists 
    • Contract review checklists
    • Requirements review checklist
    • Design review checklist
  • Interviews
  • Project management plan 
    • Not the schedule. Schedule is only part of the plan
    • Explains how the project will be executed, monitored and controlled
    • Has the consolidation of the subsidiary plans
      • Scope management plan
      • Requirements management plan
      • Schedule management plan
      • Cost management plan
      • Quality management plan
      • Resource management plan
      • Communications management plan
      • Risk management plan
      • Procurement management plan
      • Stakeholder engagement plan
      • Change management plan
      • Configuration management plan
      • Scope baseline
      • Schedule baseline
      • Cost baseline
      • Performance measurement baseline (time based budgets)
      • Project life cycle description
      • Development approach
  • Baselines (Basis for project tracking)
    • Scope baseline
    • Schedule baseline
    • Cost baseline
  • Change log – Log for maintaining the change requests
  • Lessons learned register – Register for maintaining the lessons learned during the project
  • Milestone list – Project road map with dates. High level summary of the schedule for the use of senior stakeholders.
  • Project communications – Internal, external, upward, downward, lateral, written, verbal, technology
  • Project schedule – Teams plan for meeting the objectives of the projects. Contains activity sequences with start and end dates.
  • Requirements trace ability matrix – Mapping of requirements to design, design to final product
  • Risk register – Register of risks.
  • Risk report – Qualitative, Quantitative, Risk trends
  • Approved change requests 
  • Project management information system (PMIS) – Time accounting, defects accounting, accident logs, trends
  • Work performance data – Planned Vs actuals
  • Issue log
  • Change requests
    • Corrective actions
    • Preventive actions
    • Defect repair
    • Updates
  • Project management plan updates 
  • Project documents updates 
    • Activity list
    • Assumption log
    • Lessons learned register
    • Requirements documentation
    • Risk register
    • Stakeholder register
  • Stakeholder register 
  • Project team assignments 
  • Resource breakdown structure – Once the work break down structure is defined, the resources required to develop the work packages are developed which is known as the resource breakdown structure and contains manpower, material, equipment
  • Source selection criteria
  • Knowledge management – Knowledge management tools 
    • Networking
    • Communities
    • Meetings
    • Job rotation
    • Discussion forums
    • Seminars, conferences , workshops
    • Story telling , experience sharing
  • Information management 
    • Lessons learned register
    • Project management information systems
  • Active listening – Intense listening to understand the other person’s point of view
  • Facilitation– Guide a group to successful decision
  • Leadership
  • Networking 
  • Political awareness 
  • Basis of estimates – How the various estimates were derived. Assumptions.
  • Cost forecasts 
  • Quality reports 
  • Risk report 
  • Schedule forecasts 
  • Work performance information 
  • Alternatives analysis 
  • Cost benefit analysis 
  • Earned value analysis 
  • Root cause analysis – RCA, Ishikawa diagrams, Fish bone diagrams, Pareto analysis, Control charts
  • Trend analysis 
  • Variance analysis – Planned Vs actuals for schedule, cost, scope, quality etc
  • Cost forecasts – EAC = AC+(BAC-EV)/CPI
  • Schedule forecasts – When will the project get over, based on the current trends
  • Change management plan 
  • Configuration management plan – Version controlling
  • Scope baseline 
  • Schedule baseline 
  • Cost baseline 
  • Change control tools 
  • Voting 
  • Autocratic decision making – Unilateral decision making by the leader
  • Multi-criteria decision analysis – Weights against different parameters and then scoring against them to arrive at professional decisions like recruitment, procurement etc

If any of the concepts are not clear, post your questions as comments to this post and I will answer them.

4 thoughts on “Project integration management

  1. Could you please explain what is liner programming, Integer programming Dynamic programming and Multiobjective programming


      1. Please see Rita’s book Pg 128- Constrained Optimization Methods- Listed under sub topic “Project Selection”.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: