Project management Topic 1 Introduction.

Slides:



Advertisements
Similar presentations
Options appraisal, the business case & procurement
Advertisements

Recall The Team Skills 1. Analyzing the Problem (with 5 steps) 2. Understanding User and Stakeholder Needs 3. Defining the System 4. Managing Scope 1.
Introduction to PRINCE2 Dimitrovski Dejan M.B.A. Webster University Vienna Fall 2,
Bryan Roach Chairman Crime Stoppers Australia. Strategic Planning The process for defining strategy (direction) and decision making For Crime Stoppers,
4/28/20151 PRESENTED BY NAKABAGO JOHN CONTRACT MANAGEMENT AND ADMINISTRATION IPPU PRESENTATION JOHN NAKABAGO.
Project Development: Planning & Implementation. What is a Project? “An enterprise undertaken to achieve planned results within a time frame and at some.
HEPCIT 29 th August 2003 Successes and Failures. The purpose of innovations Increase revenue Avoid costs Improve educational outcomes Prove and/or test.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
1 LaCrosse PMI Chapter Meeting A discussion about the Introduction of PM within your business 4/20/2011 Jim Strong Mayo Clinic DLMP PMO Director.
Project Management Process. Project Complexity means that: a team of people are needed to supply expertise the work needs to be broken into manageable.
Supporting people with a learning disability Introduction to Project Management Presenter: Steve Raw FInstLM, FCMI.
W5HH Principle As applied to Software Projects
THE ABILITY OF IT PROJECT MANAGER. Learning Objectives Defining project management The importance of IT project management Skills for a successful project.
Project Plans CSCI102 - Systems ITCS905 - Systems MCS Systems.
Program Management Overview (An Introduction)
Introduction to Project Management Avneet Mathur
Managing Change Implementing and Managing Change “Faced with change, employees have one question: “What’s going to happen to me?” A successful change management.
Return On Investment Integrated Monitoring and Evaluation Framework.
Course Technology Chapter 3: Project Integration Management.
Chapter 3: The Project Management Process Groups
By Saurabh Sardesai October 2014.
Project Management Basics
Change Request Management
Opportunities & Implications for Turkish Organisations & Projects
Presented by Levent Yıldızgören TTC Language Services Ltd & Learnproject.
Charting a course PROCESS.
Release & Deployment ITIL Version 3
Project Management: Madness or Mayhem
SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.
IT Project Management Cheng Li, Ph.D. August 2003.
Communication in Project Management: Does it have to be so difficult?
PLAN YOUR WORK AND WORK YOUR PLAN Bill Davis’s six project and time management tips.
Software Project Management Introduction to Project Management.
Free Powerpoint Templates Page 1 Free Powerpoint Templates How do we do it? Class 7.
MGT 461 Lecture # 19 Project Initiation Phase (I OF II)
Why we should manage projects professionally Better outcomes (benefit & risk) Better decision-making Better management of expectations More efficient.
Lecture 4 Title: The Scope Management Plan
Introduction- Project Management By Ctrl+C & Ctrl+V 1.
How Communication Management Improves Localization Management Isabelle Fleury ©
© 2012 Cengage Learning. All Rights Reserved. This edition is intended for use outside of the U.S. only, with content that may be different from the U.S.
1.  Describe an overall framework for project integration management ◦ RelatIion to the other project management knowledge areas and the project life.
Reducing the Risk of Failed Performance Measurement Programs: Assessing and establishing a solid foundation Laurie Graffo The MITRE Corporation.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
Software Project Management By Deepika Chaudhary.
©Copyright OMRON Corporation All Rights Reserved A Step by Step Approach for Creating an Environment for Successful Projects IWFST2005 Nov. 8-10,
1IT Project Management, Third Edition Chapter 4 Chapter 4: Project Integration Management.
Northwest ASSIST How to obtain maximum value from consultants 3 rd April 2008 Nadine Fry Julian Todd.
Lecture 3 Title: Information Technology Project Methodology By: Mr Hashem Alaidaros MIS 434.
Project Management Communications Overview Copyright ©
Practical Investment Assurance Framework PIAF Copyright © 2009 Group Joy Pty. Ltd. All rights reserved. Recommended for C- Level Executives.
Prince 2 and Project Management By Sayed Ahmed Just E.T.C.Technologies Inc. Just E.T.C Education Inc.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
Project Management Workshop James Small. Goals Understand the nature of projects Understand why Project Management is important Get an idea of the key.
Applied Software Project Management Andrew Stellman & Jennifer Greene Applied Software Project Management Applied Software.
An introduction to Project Management Ainsley Smith
Project management Topic 1 Project management principles.
Project management Topic 4 Organisation.
Project Management Starting out. What makes projects different to BAU (Business as Usual)?  Change - Projects are the means by which we introduce change.
PPTTEST 12/26/ :41 1 IT Ron Williams Information Technology Management Project Management.
Project management Topic 4 Starting up a project.
~ pertemuan 4 ~ Oleh: Ir. Abdul Hayat, MTI 20-Mar-2009 [Abdul Hayat, [4]Project Integration Management, Semester Genap 2008/2009] 1 PROJECT INTEGRATION.
Overview PRINCE Hogeschool Rotterdam. 2 Project definition  A project is a temporary organization that is created for the purpose of delivering.
© 2013 Gartner, Inc. and/or its affiliates. All rights reserved. Gartner is a registered trademark of Gartner, Inc. or its affiliates. The Value Review.
Project management Topic 2 Product based planning.
Company LOGO. Company LOGO PE, PMP, PgMP, PME, MCT, PRINCE2 Practitioner.
Lecturer: Eng. Mohamed Adam Isak PH.D Researcher in CS M.Sc. and B.Sc. of Information Technology Engineering, Lecturer in University of Somalia and Mogadishu.
AGRO PARKS “The Policy Cycle” Alex Page Baku November 2014.
Change Request Management
Workplace Projects.
Introduction to Projects
Presentation transcript:

Project management Topic 1 Introduction

Why do projects fail? Business case is not valid Lack of quality control Product not acceptable Outcomes not clearly defined Lack of communications with stakeholders Product is not what they wanted Roles and responsibilities not adhered to Poor decision making and control Poor Estimates of time and costs Time and money overruns Lack of planning Poor scheduling Lack of control over progress Status of project not clear

Confusion for team members How much responsibility? How much authority? How much accountability?

Guiding principles A project is a finite process with a definite start and end Projects always need to be managed in order to be successful All parties must be clear about: Why the project is needed What should be achieved How to achieve the expected outcome What the responsibilities are of each role

Benefits of using a method A single common structured method Is repeatable and teachable Builds on experience Ensures everyone knows what to do Early warning of problems Proactive not reactive Controlled management of change Active involvement of all stakeholders

Prince™ 2 standard Projects IN Controlled Environments Standard used for all government information system projects in UK Defacto standard used extensively for all projects in UK and internationally Developed from PROMPTH Simpact Systems and established by CCTA in 1989 Widely used in Australia in IT environments Government and corporate

Benefits of Prince™2 Controlled use of resources Effectively manage risk Proven best practice Common language for all team members Formal recognition of responsibilities within a project Focus on what the project is to deliver: why, when and for whom

Terms Business Case Customer Product Supplier User Used to define the information that justifies the setting up, continuation or termination of a project. It answers the question ‘Why should this project be done?’. It is updated at key points throughout the project. Customer Used to represent the person or group who has commissioned the work and will be benefiting from the end results Product Used to describe everything that the project has to create or change. This can be physical items such as building a network or creating a software program or intangible things such as culture change and public perception Supplier The group that is providing specialist resources and skills to the project or is providing goods and services to create the project outcome User The person or group who will use or operate the final product. In some situations, the customer and the user may be the same group