Office of Administration
 Matt Blunt, Governor - Larry Schepker, Commissioner
 
 
 
Information Technology Services

Comprehensive Project Management

Duration:

2 Days

Description:

This intensive two-day course focuses on ways employees can run projects
faster and more effectively. This course recommends a six-phase process as well as numerous preventative actions to efficiently speed up a project. Participants will learn how to successfully create, monitor, and guide the project’s scope and critical path as well as how to manage multiple projects. Participants will diagnose and prevent problems such as scope creep, time slippage, and team conflicts.

Objectives:

Define the six step project management process

Understand the project’s life cycle

Determine five ways to give proper leadership within culture

Design an agenda for the first project team meeting

Identify the triple constraints of every project

Define the project drivers

Demonstrate interviewing techniques that will assist in determining project specifics

Review constraint red flags to watch

Show how to set, control, and monitor project scope

Summarize major areas to brainstorm

Classify who to place on your project team

Label role descriptions and project responsibilities when you have no position power

Facilitate brainstorming and planning meetings

Create a modified code of conduct for running an empowered team

Examine forms in scheduling a project and possible scheduling issues

Formulate a WBS, work breakdown structure

Track multiple projects

Evaluate a real time line

Evaluate why time calculations are wrong

Examine characteristics of a milestone

Analyze strengths and weaknesses of a Gantt chart

Define the critical path

Evaluate the strengths and weaknesses of a critical path

Explore how to handle delays

Discuss effects of a late start

Examine steps in creating a project budget and developing a master budget control process

Discuss implementation of project plan

Identify seven things which must be communicated in every project

Review who should be communicated to

Evaluate the results of poor communication

Identify a checklist for team meetings

Analyze signs of poor updates

Describe ways to communicate bad news

Classify how to manage the project through influence rather than power

Summarize danger signals to watch

Assess how to crash a project

Implement close down checklists and handoff procedures

Identify phase out of the project

Conduct a postmortem

Scheduled Classes