WEEK 6 Introduction to Project Management. Agenda Phase 4: Controlling.

Slides:



Advertisements
Similar presentations
Project Management 6e..
Advertisements

WEEK 6. InitiatingPlanning Executing Controlling Closing “keeping things in control and in order“ Controlling Projects.
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
Defining the Project CHAPTER FOUR Student Version Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved. McGraw-Hill/Irwin.
Project Change Management
Message Design and Content Creation 23 January 2007 Kathy E. Gill.
1 SWE Introduction to Software Engineering Lecture 6 - Software Project Management.
Project Management Session 7
Chapter 3: The Project Management Process Groups
Author:Prof.Dr.Tomas Ganiron Jr1 CHAPTER 7 PROJECT EXECUTION, MONITOR & CONTROL PROCESS 7-1 Project Executing process 7-2What is Project monitor & control.
4 4 By: A. Shukr, M. Alnouri. Many new project managers have trouble looking at the “big picture” and want to focus on too many details. Project managers.
Purpose of the Standards
©2003 Prentice Hall Business Publishing, Accounting Information Systems, 9/e, Romney/Steinbart 16-1 Accounting Information Systems 9 th Edition Marshall.
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
How the Change Control Process Affects Project Quality
WEEK 7 Introduction to Project Management. Wk 7 Agenda Review Phase 5: Closing Out the Project Review for test Assignment Discussion Quiz.
WEEK 5 Introduction to Project Management. Agenda Phase 2: Planning ◦ Compressing the Schedule ◦ Risk Analysis Phase 3: Executing.
Module 8: Risk Management, Monitoring and Project Control We would like to acknowledge the support of the Project Management Institute and the International.
Project Management Process Overview
Copyright Course Technology 1999
Information Technology Project Management, Sixth Edition Note: See the text itself for full citations.
Introduction PMBOK® © Whizlabs.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Certificate IV in Project Management Introduction to Project Management Course Number Qualification Code BSB41507.
Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.
Centro de Estudos e Sistemas Avançados do Recife PMBOK - Chapter 4 Project Integration Management.
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
WEEK 6. Agenda Phase 4: Controlling Controlling Projects “keeping things in control and in order“ InitiatingPlanning Executing Controlling Closing.
MD Digital Government Summit, June 26, Maryland Project Management Oversight & System Development Life Cycle (SDLC) Robert Krauss MD Digital Government.
Copyright 2009  Describe the five project management (PM) process groups, the typical level of activity for each, and the interactions among them  Understand.
SacProNet An Overview of Project Management Techniques.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
BSBPMG505A Manage Project Quality Manage Project Quality Project Quality Processes Diploma of Project Management Qualification Code BSB51507 Unit.
Project Life Cycle.
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Certificate IV in Project Management Qualification Code BSB41507 Unit.
Managing the Information Systems Project © Abdou Illia MIS Spring /26/2015.
Copyright 2008  Project management process groups progress from initiating activities to planning activities, executing activities, monitoring and controlling.
Refrences: Information Technology Project Management, Sixth Edition(ch#3) Note: See the text itself for full citations.
Dr. Jana Jagodick Polytechnic of Namibia, 2012 Project Management Chapter 5 Project Integration Management.
Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.
Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.
PLUG IT IN 6 Project Management. 1.Project Management for Information Systems Projects 2.The Project Management Process 3.The Project Management Body.
Apply Quality Management Techniques Project Quality Processes Certificate IV in Project Management Qualification Code BSB41507 Unit Code BSBPMG404A.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Lesson 1: Examining Professional Project Management Topic 1A: Identify Project Management Processes.
BSBPMG404A Apply Quality Management Techniques Apply Quality Management Techniques Project Quality Processes C ertificate IV in Project Management
Communications Management
Project Management Project Integration Management Minder Chen, Ph.D. CSU Channel Islands
Project Management Basics. 2 Please introduce yourself…  Name  Business Unit / Function / Process  Current Project / Process  Team Size  Ice Breaker.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
Quick Recap.
Project Management Processes for a Project
Introduction to Project Management
Apply Project Scope Management Techniques Project Scope Processes – Part 2 Week 4 Certificate IV in Project Management Qualification Code BSB41507.
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
WEEK 6 Introduction to Project Management. Wk 6 Agenda Verify Hybrid Wk 5 Review Wk 5 ◦ Compressing the Schedule ◦ Risk Identification Techniques ◦ Project.
Chapter 3: The Project Management Process Groups: A Case Study Information Technology Project Management, Fourth Edition Project Execution & Closing Thursday,
BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.
Chapter 7 Project Management and Event Implementation
The Project Management Process Groups
Successfully Managing Customer Expectations Change is expected to occur during the life of any project, but this change must be controlled and managed.
Slide 1ICT 327 Management of IT ProjectsSemester 1, 2005 Topic 3 Executing & Controlling & Closing Projects.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XI)
Project Management PTM721S
Project Planning: Scope and the Work Breakdown Structure
5.5 Control Scope The process of monitoring the status of both the project and product scope Focuses on managing any changes to the scope baseline and.
Controlling Projects “keeping things in control and in order“
Project Integration Management
Mastering Change Control
Chapter 3: The Project Management Process Groups: A Case Study
Presentation transcript:

WEEK 6 Introduction to Project Management

Agenda Phase 4: Controlling

Controlling Projects “keeping things in control and in order“ InitiatingPlanning Executing Controlling Closing

Controlling Phase Ensuring that the project objectives are met by monitoring and measuring progress and taking corrective action when needed.

Controlling Phase Focus Involves measuring progress toward project objectives, monitoring deviation from the plan, and taking correction actions Outputs include performance reports, requested changes, and updates to various plans

Triple Constraint You must work with your clients to determine what their definition of success is. Scope Time Quality Cost

Project Change Management Definition: “a general term describing the procedures used to ensure that changes are introduced in a controlled and coordinated manner.”

Change Management Processes Change Request ◦ Requests to expand or reduce the project scope, modify policies, processes, plans or procedures, modify costs or budgets, or revise schedules. Change Order ◦ Used in some companies to identify approved change requests (order once it has been approved)

Changes Most change requests are the result of:  An external event  An error or omission in defining the scope of the product or project  A value-adding change (e.g., new technology, new software version, etc.)

Scope Creep Changes to the project that result in additional work. If not properly identified and managed properly, your project may come in considerably over budget and/or behind in schedule.

Scope Creep Avoidance Document, document, document! ◦ Anticipate areas of miscommunication. ◦ Be as succinct as possible. ◦ Add what is NOT required. ◦ Obtain sign-off by key stakeholders. Use signed-off scope and requirements documents to manage your project ◦ What’s “in” and what’s “out”

Hybrid / Homework Read Chapter 4 Complete all activities required while reading chapter 4 Complete the Matching exercise for Chapter 4 Complete the Multiple Choice for Chapter 4

Quiz Time