Project Management Concepts

Slides:



Advertisements
Similar presentations
Project management.
Advertisements

Project Management Concepts
Developing the Schedule
Chapter 6 Scheduling. 222 Learning Objectives Estimate the duration for each activity Establish the estimated start time and required completion time.
© The McGraw-Hill Companies, Software Project Management 4th Edition Activity planning Chapter 6.
CP Chapter 4 Schedule Planning.
PRJ566 Project Planning and Management Lecture: Network Diagrams.
PRJ566 Project Planning and Management Lecture: Dependencies and Network Diagrams.
Project Management CHAPTER SIXTEEN McGraw-Hill/Irwin Copyright © 2011 by the McGraw-Hill Companies, Inc. All rights reserved.
F O U R T H E D I T I O N Project Management © The McGraw-Hill Companies, Inc., 2003 supplement 3 DAVIS AQUILANO CHASE PowerPoint Presentation by Charlie.
PROJECT MANAGEMENT Outline What is project mean? Examples of projects…
PROJECT SCHEDULE PROJECT SCHEDULE Able to : a)Produce a network diagram based on the activities in a construction work b)Produce a network.
3-1 © Prentice Hall, 2004 Chapter 3: Managing the Object-Oriented Information Systems Project Object-Oriented Systems Analysis and Design Joey F. George,
Project Management Concepts.  What is a Project?  Common Project Terms  What does a Project Manager do?  What’s in a Project?  Project Management.
Advanced Project Management - CPH
Chapter 10: Project Schedule Planning
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 3.1.
1 Operations Management Lesson 5 Project Management.
© 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.
© 2015 Cengage Learning. All Rights Reserved. May not be scanned, copied or duplicated, or posted to a publicly accessible website, in whole or in part.
Project Management. What is a Project? One Time Effort Identifiable Start/End Points Specific Objectives Multiple Tasks Resources from Across the Organization.
Project Management. Maintenance and Reliability 14 Aug 2001.
Importance of Project Schedules
McGraw-Hill/Irwin ©2008 The McGraw-Hill Companies, All Rights Reserved SECTION 12.1 PROJECT MANAGEMENT.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 1 Slide 1 Project management.
Chapter 4: Project Management Objectives Define the terms project and project management, and differentiate between project and process management. Describe.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Project management.
Roberta Russell & Bernard W. Taylor, III
Project Time Management
1 SOFTWARE PRODUCTION. 2 DEVELOPMENT Product Creation Means: Methods & Heuristics Measure of Success: Quality f(Fitness of Use) MANAGEMENT Efficient &
This work is licensed under a Creative Commons Attribution 3.0 Unported LicenseCreative Commons Attribution 3.0 Unported License (CC-BY). Project Management.
Project Time Management J. S. Chou, P.E., Ph.D.. 2 Activity Sequencing  Involves reviewing activities and determining dependencies.  A dependency or.
HIT241 - TIME MANAGEMENT Introduction
Project Management An overview. What is a Project A temporary job to accomplish a specific task A temporary job to accomplish a specific task Attributes.
Time Management Week 7 - Learning Objectives You should be able to: n List and describe the processes, activities, inputs, and outputs in time management.
PROJECT MANAGEMENT Outline What is project mean? Examples of projects… Project Planning and Control Project Life Cycle Gantt Chart PERT/CPM.
Project Time Management J. S. Chou, P.E., Ph.D.. 2 Activity Sequencing  Involves reviewing activities and determining dependencies.  A dependency or.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
POST GRADUATE PROGRAM OF INFORMATION TECHNOLOGY
Chapter Extension 18 Large-Scale Systems Development © 2008 Pearson Prentice Hall, Experiencing MIS, David Kroenke.
Information Technology Project Management, Seventh Edition Note: See the text itself for full citations.
IT Project Management, Third Edition Chapter 6 1 Chapter 3: Project Time Management.
BIS 360 – Lecture Two Ch. 3: Managing the IS Project.
Lecture 7. Review of Lecture 6 Project Scheduling: The process of defining project activities, determining their sequence, estimating their duration Scheduling.
Managing Project Resources. Project Resources Human Resources Project stakeholders: – Customers – Project team members – Support staff Systems analyst.
Ahmad Al-Ghoul. Learning Objectives Explain what a project is,, list various attributes of projects. Describe project management, discuss Who uses Project.
1IT Project Management, Third Edition Chapter 6 Chapter 6: Project Time Management.
Work Systems and the Methods, Measurement, and Management of Work by Mikell P. Groover, ISBN ©2007 Pearson Education, Inc., Upper Saddle.
CSEM01 - wk8 - Software Planning1 Software Planning CSEM01 SE Evolution & Management Anne Comer Helen Edwards.
PROJECT MANAGEMENT Outline What is project mean? Examples of projects… Project Planning and Control Project Life Cycle Gantt Chart PERT/CPM.
PROJECT MANAGEMENT Outline What is project mean? Examples of projects… Project Planning and Control Project Life Cycle Gantt Chart PERT/CPM.
Project Management Concepts
1 Project management. 2 Topics covered Management activities Project planning Project scheduling Risk management.
Information Systems System Analysis 421 Chapter 3 Managing the Information Systems Project.
PROJECT MANAGEMENT Outline What is project mean? Examples of projects…
Chapter 7 – PERT, CPM and Critical Chain Operations Management by R. Dan Reid & Nada R. Sanders 4th Edition © Wiley 2010.
Project Time Management Ashima Wadhwa. Schedule Development – Determining start and finish dates for project activities – Without realistic dates, project.
Project Time Management
Chapter 6 Scheduling. 222 Learning Objectives  Estimate the duration for each activity  Establish the estimated start time and required completion time.
(M) Chapter 12 MANGT 662 (A): Procurement, Logistics and Supply Chain Design Purchasing and Supply Chain Analysis (1/2)
TK3333 Software Management Topic 6: Scheduling. Contents  Estimate the duration for each activity  Establish the estimated start time and required completion.
Copyright 2006 John Wiley & Sons, Inc. Beni Asllani University of Tennessee at Chattanooga Project Management Operations Management - 5 th Edition Chapter.
Develop Schedule is the Process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create the project schedule.
1 Project management Organising, planning and scheduling software projects.
Chapter 16 – Project Management
Project Management: PERT/CPM
Chapter 6: Project Time Management
Project Time Management
CIS 210 Systems Analysis and Development
Importance of Project Schedules
Presentation transcript:

Project Management Concepts

Topics What is a Project? Common Project Terms What does a Project Manager do? What’s in a Project? Project Management Processes Getting Started Planning a Project Executing the Plan Finishing the Project

What is a project? A project is an activity that : is temporary having a start and end date is unique brings about change has unknown elements, which therefore create risk

What is a project? Generally projects are formed to solve a problem or take advantage of an opportunity. Business as usual activities can often be mistaken for projects. Generally it is the uniqueness of the activity that is the deciding factor – do we do this every year? If so, then it is not truly a project – although you can use project methods to get it done.

Quiz- Are these projects? Building a deck Implementing a new system Mowing the lawn Planning a wedding Setting up a business Planning a student graduation Yes No

Common project terms Deliverables: Tangible ‘things’ that the project produces Milestones: Dates by which major activities are performed. Tasks: Also called Actions. Activities undertaken during the project Risks: Potential problems that may arise Issues: Risks that have happened Gantt Chart: A specific type of chart showing time and tasks. Usually created by a Project Management program like MS Project. Stakeholder: Any person or group of people who may be affected by your project

Example – Building a deck Deliverables: A plan, a consent form, the deck Milestones: Tasks: Plan drafted Plan approved 1 Dec 15 Dec Plan submitted 16 Dec 15 Jan Materials purchased Resources booked Equipment identified Deck constructed Deck tested Deck quality approved “Deck warming” completed 16 Jan 19 Jan 23 Jan 24 Jan 28 Jan tasks Subtasks Plan drafted Requirement gathered Best practice researched Draft 1 prepared Distributed to stakeholders Plan approved Feedback gathered Amendments made Final plan prepared Sign-off obtained

Example Continued Risks: Issues: Gantt Chart: Stakeholder: Plan is not approved after first round of feedback Resources are not available at the required time Plan is not given consent For each of the above, you should have a contingency plan, or do some activity that may prevent it happening in the first place. Issues: If any of the above actually happens, then it becomes an issue to solve. Gantt Chart: Stakeholder: House owner, Builder, Council, ???

Project Manager A person with a diverse set of skills – management, leadership, technical, conflict management, and customer relationship – who is responsible for: initiating, planning, executing, controlling, monitoring, and closing down a project.

What does a PM do? Project Managers are essentially jugglers. They must make sure that everything keeps to task, that potential issues are quickly eliminated and the project is delivered on time, all the while making sure everyone knows what is happening and the project quality and budget are acceptable. Specifically they: direct all activities required to successfully meet the project objectives manage risk – scanning ahead for potential issues and resolving them before they become a problem solve problems - recommending alternative approaches to problems that arise and providing guidance to the Project Sponsor track and report project progress communicate to all stakeholders in the project

Characteristics of Projects A project contains a well defined objective. The project objective is defined in terms of scope ( or requirements), schedule, and cost. A project is carried out via a set of interdependent tasks. A project uses various resources to carry out these tasks.

Characteristics of Projects Three critical drivers Scope (or requirement), cost, and time Trade-offs exist in any project against time and costs Time can only be reduced to a point Adding more people can create diseconomies of scale Increasing time may reduce or increase costs

Characteristics of Projects A project has a definite start date and an expected completion date. The actual completion date may not always be the same as the expected date. A project is a one time or unique endeavor. A project has a customer. So why do projects fail? See later material!

Characteristics of Projects A project has a degree of UNCERTAINTY. In project planning many assumptions are made regarding: access to resources. resource capability. impact of environmental factors. These assumptions are not always accurate.

Measuring Project Success We measure the success of a project using 4 major project constraints, specifically: Scope. Cost. Schedule (Time). Customer satisfaction (quality and performance).

Project Constraints Project scope – Have all the project requirements (i.e., deliverables) been completed? Project cost – Is the cost of the project close to the amount the customer has agreed to pay? Schedule – Was the project completed on time? Customer satisfaction – Is the customer happy with the quality of the project?

Project Goal The goal of a project is therefore: Complete the project scope within budget, time, and to the customer’s satisfaction. Examples of sources of project failure: The project manager underestimated the costs or resources required to complete the project. Uncertainties (e.g., weather, strikes, fire) may cause delays in the project. Customers may change requirements during the project. This is very common in software and new product development projects.

Work-Breakdown Structure WBS Hierarchy of tasks required to complete project Each task is broken into smaller tasks that can be managed and estimated Define task dependencies Some tasks must begin at the same time, some must end at the same time and some cannot start until the other tasks have finished. Estimate task durations and cost May be inputted into project management software Final WBS plan is called baseline WBS

WBS

IT projects fail … a lot. 31.1% of projects will be cancelled before they ever get completed…. Over 50% of projects cost almost triple their original estimates. 1 million dollar project turns into a 3 million dollar project Estimate: in 1995 American companies and government agencies spent $81 billion for cancelled software projects. On the success side, the average is only 16.2% for software projects that are completed on-time and on-budget.

Project Failure (French Study)

Baseline Plan Things don’t always go according to plan critical people turnover, natural disasters, hiring freeze, technology change, new managements, competitors may make project more or less important Requires project managers to re-assess and trade-offs between requirements, costs, and time

The Project Life Cycle 5 major phases of a project are: Identifying a need. Developing a proposed solution. Performing the project. Monitoring and control Terminating the project.

Typical development phases of a project

Demos Project Management Demo

Project Scheduling

Activity Duration Estimates The first step in scheduling is to estimate how long each activity will take. The duration estimate is the total elapsed time for the work to be done PLUS any associated waiting time. The person responsible for performing the activity should help make the duration estimate. 6 7 7 5 7 5 6 5 5 5

Project Start and Finish Times It is necessary to select an estimated start time and a required completion time for the overall project. 7 8 8 6 8 6 7 6 6 6

Schedule Calculations A project schedule includes: the earliest times (or dates) at which each activity can start and finish, based on the project's estimated start time (or date) the latest times (or dates) by which each activity must start and finish in order to complete the project by its required completion time (or date) 8 10 10 7 10 7 8 7 7 7

Earliest Start and Finish Times Earliest start time (ES) is the earliest time at which a particular activity can begin. Earliest finish time (EF) is the earliest time by which a particular activity can be completed. EF – ES = Activity Duration Estimate 9 11 11 8 11 8 9 8 8 8

Latest Start and Finish Times Latest start time (LS) is the latest time an activity must be started in order for the entire project to be completed by its completion time. Latest finish time (LF) is the latest time an activity must be finished in order for the entire project to be completed by its completion time. LF – LS = Activity Duration Estimate 11

Slack time Slack or float is the amount of time that a task in a project network can be delayed without causing a delay to: subsequent tasks (free float) project completion date (total float) An activity that has a total float equal to zero is said to be a 'critical activity', which means that a delay in the finish time of this activity will cause the entire project to be delayed by the same amount of time.

Free vs Total slack Free slack: The free slack of an activity is the time this activity can be delayed without impact on the following activity. Total slack: The total slack of an activity is the time this activity can be delayed without impact on the finish date of the project.

Total Slack (Cont.) If total slack is positive, it is the maximum time the activities on the path can be delayed. If total slack is negative, it is the amount of time the activities on the path must be accelerated. 14 17 17 11 17 11 14 11 11 11

Example

Critical Path The critical path is the longest path in the diagram. The activities that make up the critical path have the least slack. 15 18 18 12 18 12 15 12 12 12

Types of Critical Paths Noncritical paths have positive values of total slack. Critical paths have zero or negative values of total slack. 16 19 19 13 19 13 16 13 13 13

Critical Path Analysis Sequence of activities charted Longest path through the network of activities Task dependencies compressed as much as possible Tasks may be moved to non-critical paths to shorten critical path If tasks on critical path run late, the project will be late.

Determining the Critical Path for Project X

Various Project Management Tools/Techniques Gantt Chart a simple bar chart that depicts project tasks against a calendar Program Evaluation and Review Technique (PERT) is a graphical network model that depicts a project’s tasks and the relationships between those tasks (Dependencies and Critical paths are found in PERT charts) Critical Path Method (CPM) A method used for determining the sequence of task activities that directly affect the completion of a project Microsoft Project Most widely used project management software http://office.microsoft.com/en-us/project/default.aspx

Develop a schedule Gantt Chart

Gantt Chart of WBS created by MS Project Figure CE 18-5

PERT Chart Example

Planning Large-Scale Systems Development Projects Biggest challenge is scheduling Errors accumulate Difficult to do credible planning Every task may be on critical path MS Vista Operating system was delivered two years late. Was suppose to take 3 Y but took 5 Y ( 67% schedule overrun) Office 2003 was late. MS SQL server 2005 barely made it into 2005.

Managing Large-Scale Systems Development Project Challenges Coordination Projects often organized into independent groups Diseconomies of scale Adding people increases coordination requirements Configuration control Changes must be carefully manages and monitored Unexpected events Chance of disruption due to unanticipated events

Dealing with Uncertainty Policies and procedures implemented to instill these principles: Business users take responsibility for new systems’ success Users work with IS throughout systems development Users take active role in project planning, management, and reviews Development phase not complete until work reviewed and approved Users actively test system Future systems developed in small increments