18
Slide 1 ICT 327 Management of IT Projects Semester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Embed Size (px)

Citation preview

Page 1: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 1 ICT 327 Management of IT Projects Semester 2, 2004

Topic 11

Executing & Controlling Projects

Page 2: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 2 ICT 327 Management of IT Projects Semester 2, 2004

Topic 11 Reading

• Essential• Schwalbe Chapter 3

• Recommended• PMBOK Chapter 3

Page 3: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 3 ICT 327 Management of IT Projects Semester 2, 2004

Learning Objectives

At the end of this topic, you should be able to:• Describe the five project management process

groups, the typical level of activity for each, and the interactions among them

• Explain how the project management process groups relate to the project management knowledge areas

• Discuss how organizations develop information technology project management methodologies to meet their needs

Page 4: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 4 ICT 327 Management of IT Projects Semester 2, 2004

Learning Objectives

At the end of this topic, you should be able to:• Review a case study of an organization and

identify the project management process groups required to manage an information technology project

• Explain the contribution that effective project initiation, project planning, project execution, project control, and project closing makes to project success

Page 5: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 5 ICT 327 Management of IT Projects Semester 2, 2004

Key terms

• planning processes — devising and maintaining a workable scheme to accomplish the business need that the project was undertaken to address

• process — a series of actions directed toward a particular result

• project management process groups — the progression of project activities from initiating to planning, executing, controlling, and closing

Page 6: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 6 ICT 327 Management of IT Projects Semester 2, 2004

Key Terms

• closing processes — formalizing acceptance of the project or phase and bringing it to an orderly end

• controlling processes — actions to ensure that project objectives are met

• executing processes — coordinating people and other resources to carry out the project plans and produce the products or deliverables of the project

• initiating processes — actions to commit to begin or end projects and project phases

Page 7: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 7 ICT 327 Management of IT Projects Semester 2, 2004

Project Management Process Groups

• Project management can be viewed as a number of interlinked processes

• The project management process groups include• initiating processes• planning processes• executing processes• controlling processes• closing processes

Page 8: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 8 ICT 327 Management of IT Projects Semester 2, 2004

Overlap of Process Groups in a Phase

(PMBOK® Guide, 2000, p. 31)

Page 9: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

ITPM Methodology

See figure in text. Note thatmany parts of this approachmap to the PMBOK, but some activities have beenchanged to meet the needsof the organization.

Page 10: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 10 ICT 327 Management of IT Projects Semester 2, 2004

Project Initiation

• The main goal is to formally select and start off projects

• Key outputs include:• Assigning the project manager• Identifying key stakeholders• Completing a business case• Completing a project charter & getting

signatures on it

Page 11: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 11 ICT 327 Management of IT Projects Semester 2, 2004

Initiation

InitiationProject request

Business case

Page 12: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 12 ICT 327 Management of IT Projects Semester 2, 2004

Project Planning

• The main purpose of project planning is to guide execution

• Key outputs include:• A team contract• A scope statement• A work breakdown structure (WBS)• A project schedule, in the form of a Gantt chart

with all dependencies and resources entered• A list of prioritized risks

Page 13: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 13 ICT 327 Management of IT Projects Semester 2, 2004

Project Executing

• It usually takes the most time and resources to perform project execution since the products of the project are produced here

• The most important output of execution is work results

• Project managers must use their leadership skills to handle the many challenges that occur during project execution

Page 14: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 14 ICT 327 Management of IT Projects Semester 2, 2004

Project Controlling

• Controlling involves measuring progress toward project objectives, monitoring deviation from the plan, and taking corrective actions

• Controlling affects all other process groups and occurs during all phases of the project life cycle

• Status and progress reports are important outputs of controlling

Page 15: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 15 ICT 327 Management of IT Projects Semester 2, 2004

Question

• Identify control activities for each of the other process areas?

Page 16: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 16 ICT 327 Management of IT Projects Semester 2, 2004

Change control

• What other areas does a change request affect?

Page 17: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 17 ICT 327 Management of IT Projects Semester 2, 2004

Project Closing

• The closing process involves gaining stakeholder and customer acceptance of the final product and bringing the project, or project phase, to an orderly end

• Even if projects are not completed, they should be closed out to learn from the past

• Project archives and lessons learned are important outputs. Most projects include a final report and presentations

Page 18: Slide 1ICT 327 Management of IT ProjectsSemester 2, 2004 Topic 11 Executing & Controlling Projects

Slide 18 ICT 327 Management of IT Projects Semester 2, 2004

Post-Project Follow-up

• Many organizations have realized that it’s important to review the results of projects a year or so after they have been completed

• Many projects project potential savings, so it’s important to review the financial estimates and help learn from the past in preparing new estimates