1 CS-413 Integration Management (Part 6) Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009 Dr.Çağatay ÜNDEĞER Instructor Bilkent University, Computer Engineering Middle East Technical University, Game Technologies & General Manager SimBT Inc. e-mail : [email protected]
Integration Management (Part 6). Dr.Çağatay ÜNDEĞER Instructor Bilkent University, Computer Engineering Middle East Technical University, Game Technologies & General Manager SimBT Inc. e-mail : [email protected]. Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009. - PowerPoint PPT Presentation
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
1CS-413
Integration Management (Part 6)
Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009
• Introduction• Project Plan Development• Project Plan Execution• Integrated Change Control
4CS-413
Integration Management(Introduction)
• Includes the process required to ensure that– Elements of project are properly
coordinated.• Involves making tradeoffs among competing
objectives and alternatives – To meet stakeholder needs and
expectations.
5CS-413
Integration Management(Introduction)
• All project management components are integrative to some extend,
• But integration management is primarily integrative.
• Although process will be presented as discrete elements with well-defined interfaces,
– In practice, they may usually overlap and interact.
6CS-413
Integration Management(Major Phases)
• Project Plan Development:– Integrating and coordinating all project
plans to create a consistent, coherent document.
• Project Plan Execution:– Carrying out project plan by performing
activities included in the plan.• Integrated Change Control:
– Coordinating changes across entire project.
7CS-413
Integration Management(Major Phases)
8CS-413
Integration Management
• Introduction• Project Plan Development• Project Plan Execution• Integrated Change Control
9CS-413
Project Plan Development(Introduction)
• Uses outputs of other planning processes.• It is an iterative process;
– Initial draft may include a coarse plan;– Subsequent versions includes details.
10CS-413
Project Plan Development (Introduction)
• Scope of the project plan is usually determined;– Using a work breakdown structure, and– Iteratively decomposing tasks.
• All of the tasks must be;– Planned,– Estimated,– Scheduled, and– Authorized.
11CS-413
Project Plan Development(Objective)
• Project plan is used to:– Guide project execution,– Document project planning assumptions,– Document project planning decisions,– Faciliate communication among
stakeholders,– Define key management reviews,– Provide a baseline for progress
measurement and project control.
12CS-413
Inputs, Tools & Techniques, and Outputs
13CS-413
Project Plan Development(Inputs)
• Other planning outputs• Historical information• Organizational policies• Constraints• Assumptions
14CS-413
Project Plan Development(Inputs)
• Other planning outputs:– Work breakdown structures,– Gantt Charts, network diagrams, etc.– Outputs of planning processes in other
knowledge areas:• e.g. time, cost, quality management
• Scope, schedule and cost– Major milestones and their target dates– Key or required staff and their expected costs– Key risks and their planned responses if happened– Subsidiary management plans:
• Preventive actions:– Any action done that reduces the risks.
• Corrective actions:– Any action done that brings project
performance in line with the baseline plan.
34CS-413
Project Plan Execution(Tools & Techniques)
• General management skills• Product skills and knowledge• Work authorization system• Status review meetings• Project management information system
(PMIS)• Organizational procedures
35CS-413
Project Plan Execution(Tools & Techniques)
• General management skills:– Leadership, communicating, negotiation
skills are essential.• Product skills and knowledge:
– Project team must have skills and knowledge about the project domain.
– If required, new staff can be acquired.
36CS-413
Project Plan Execution(Tools & Techniques)
• Work authorization system:– A formal procedure for authorizing project
work– To ensure that work done at the right time
and in the proper sequence.– Usually written authorization to begin work
is used.
37CS-413
Project Plan Execution(Tools & Techniques)
• Status review meetings:– Regular scheduled meetings to exchange
information about project situation.– May be held on different levels and
frequencies.• Project management team (weekly)• Customer (monthly)
38CS-413
Project Plan Execution(Tools & Techniques)
• Project management information system (PMIS)– Consist of tools and techniques used to;
• Gather, integrate and disseminate outputs of the project management process.
• Organizational procedures:– All organizations involved in project may
have formal and informal procedures that are useful.
39CS-413
Project Plan Execution(Outputs)
• Work results• Change requests
40CS-413
Project Plan Execution(Outputs)
• Work results:– Outcomes of activities performed to
accomplish the project:• Results of activities (completed, failed,
cancelled etc.)• Documents produced (requirements,
design, test report, etc.)
41CS-413
Project Plan Execution(Outputs)
• Change requests:– Sometimes, change requests about scope,
cost and schedule occur during the plan execution.
– The approved ones are reflected to the project plan.
42CS-413
Integration Management
• Introduction• Project Plan Development• Project Plan Execution• Integrated Change Control
43CS-413
Integrated Change Control
• Concerned with:– Influencing factors, which create changes,
• To ensure that changes are agreed upon;
– Determining that a change has occured;– Managing actual changes when and as
they occur.
44CS-413
Integrated Change Control
• Project scope and performance baseline must be maintained by continuously managing changes:– Rejecting new changes, or– Approving changes and integrating them
into a revised baseline.
45CS-413
Integrated Change Control
• Requires:– Maintaining integrity of performance
measurement baselines;– Ensuring that product scope changes are
reflected to planned scope.– Coordinating changes across knowledge