Slide 1ICT 327 Management of IT ProjectsSemester 1, 2005 Topic 3 Executing & Controlling & Closing Projects

Slide 2ICT 327 Management of IT ProjectsSemester 1, 2005 Reading Essential Schwalbe Chapter 3 Recommended PMBOK Chapter 3

Slide 3ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 4ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 5ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 6ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 7ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 8ICT 327 Management of IT ProjectsSemester 1, 2005 Overlap of Process Groups in a Phase (PMBOK® Guide, 2000, p. 31)

Slide 9ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 10ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 11ICT 327 Management of IT ProjectsSemester 1, 2005 Task Review your WBS from last week for the unit. Add milestones Add activities Add time next each

Slide 12ICT 327 Management of IT ProjectsSemester 1, 2005 Executing

Slide 13ICT 327 Management of IT ProjectsSemester 1, 2005 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 (deliverables) Project managers must use their leadership skills to handle the many challenges that occur during project execution Quality assurance

Slide 14ICT 327 Management of IT ProjectsSemester 1, 2005 Activities Project plan execution Quality assurance Team development Information distribution Source selection Contract administration

Slide 15ICT 327 Management of IT ProjectsSemester 1, 2005 Question How are you going with your project plan execution for this unit?

Slide 16ICT 327 Management of IT ProjectsSemester 1, 2005 ITPM Methodology

Slide 17ICT 327 Management of IT ProjectsSemester 1, 2005 Controlling

Slide 18ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 19ICT 327 Management of IT ProjectsSemester 1, 2005 Activities Integrated change control Scope verification Scope change control Schedule control Cost control Quality control Performance reporting Risk monitoring & control Is folder structure important?

Slide 20ICT 327 Management of IT ProjectsSemester 1, 2005 Change control How would you verify the scope of your activities for this unit? What does it mean control scope? Suggest how you could do this.

Slide 21ICT 327 Management of IT ProjectsSemester 1, 2005 Closing

Slide 22ICT 327 Management of IT ProjectsSemester 1, 2005 Project Closing Gaining stakeholder and customer acceptance of the final product. 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 Lessons learned are important outputs. Most projects include a final report and presentations What can be learned from a failed project?

Slide 23ICT 327 Management of IT ProjectsSemester 1, 2005 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

Slide 24ICT 327 Management of IT ProjectsSemester 1, 2005 Case study Electronic Warfare System Large budget Strong standards (Military) Failed project

Slide 25ICT 327 Management of IT ProjectsSemester 1, 2005 Activities Administrative closure Post-implementation review/ Lessons learnt Document archive