Playing The Project Management Game

Download as pdf or txt
Download as pdf or txt
You are on page 1of 39

Playing The Project

Management Game

Tools and Techniques to Win the Game


Dean Athanassiades, PMP
Nancy Stetson, PMP

Version 2003-12-02 (c) Dean Athanassiades 2003 1


Presenters
¾ Dean Athanassiades, PMP
– Philips Medical IT Professional Services
¾ Nancy Stetson, PMP
– ChartMaxx Project Manager
– MedPlus, Inc

Version 2003-12-02 (c) Dean Athanassiades 2003 2


Workshop Objective
¾ Provide attendees with opportunity to learn /
practice / apply project management skills and
techniques using a “game” oriented approach
¾ Provide attendees with a set of project tools that
they can use in managing projects within their
organizations
¾ Provide attendees with a game-oriented
framework that they can use within their own
organization to facilitate learning among their own
project teams
Version 2003-12-02 (c) Dean Athanassiades 2003 3
Time Guidelines
¾ 10:00-10:10 – Introductions
¾ 10:10-10:20 – Game background and rules
¾ 10:20-10:35 – Project management basics
¾ 10:35-10:50 – Initiation Phase
¾ 10:50-11:05 – Planning Phase
¾ 11:05-11:20 – Control and Execution Phase
¾ 11:20-11:35 – Closing Phase
¾ 11:35-11:50 – Game Wrap-Up and Questions
Version 2003-12-02 (c) Dean Athanassiades 2003 4
Project Management
Overview

Version 2003-12-02 (c) Dean Athanassiades 2003 5


What Is Project Management
¾ Process of planning, scheduling, and
controlling project activities
¾ Science and art of making tradeoffs
between schedule, scope, cost, and quality
while solving the problem defined for the
project

Version 2003-12-02 (c) Dean Athanassiades 2003 6


Why Projects Fail
¾ Disagreement about desired result
¾ Disagreement about how to achieve desired result
¾ Insufficient or inappropriate resources
¾ Insufficient time to complete project
¾ Inadequate budget to complete project
¾ Poor communications
Ill-defined roles
(Source Unknown)

Version 2003-12-02 (c) Dean Athanassiades 2003 7


Games as a Learning Tool
¾ Gaming defined
– Use of games as a tool to practice and apply business
skills
¾ Examples of Games used as learning tools
– EIS
– Banking / Finance Asset Management
– Industrial Marketing
– Pharmaceutical
– Merger and Acquisition

Source: http://www.insead.fr/facultyresearch/teaching_tools/simulations.htm

Version 2003-12-02 (c) Dean Athanassiades 2003 8


Case Scenario
¾ Your organization has elected to re-design its emergency
department processes to better serve its clients
¾ Scope of the project may involve
– Physical redesign (bigger, smaller, different location)
– Change in processes and workflow
– Changes in equipment
– Changes in staffing
¾ You have been appointed to lead the effort to come up with
the desired physical and logical workflow for the new ED

Version 2003-12-02 (c) Dean Athanassiades 2003 9


Rules of the Game
¾ Game flow similar to popular board game called
“Cranium”
¾ Form teams based upon attendance at workshop
¾ Game “board” has 4 sides representing 5 phases of
a project:
– Initiation
– Planning
– Executing & Controlling
– Closing

Version 2003-12-02 (c) Dean Athanassiades 2003 10


Rules of the Game
¾ Within each Phase, there are multiple “stops” for
the key project Knowledge Areas:
– Integration management
– Scope management
– Time management
– Cost management
– Quality management
– Human resource management
– Communications management
– Risk management
– Procurement management
¾ At each “stop”, the player will have to correctly
answer a question related to the Knowledge Area
Version 2003-12-02 (c) Dean Athanassiades 2003 11
Rules of the Game
¾ Object of the game is to traverse the board
through the 5 phases of project management
before any of the other players

Version 2003-12-02 (c) Dean Athanassiades 2003 12


Rules of the Game
¾ Complete the tool provided for the Phase
– Example: for Initiation Phase, the tool provided
is a Charter Statement
¾ Then, move through each Phase by
answering one or more Knowledge Area
questions related to that Phase

Version 2003-12-02 (c) Dean Athanassiades 2003 13


Rules of the Game
¾ Movement through each Phase is controlled
by the draw of Random Number Cards.
¾ If you draw 1 through 9, you move forward
that number of spaces and answer the
Knowledge Area question associated with
the space that you land on.
¾ If you draw 10, 11, or 12, you go directly to
the beginning of the next Phase

Version 2003-12-02 (c) Dean Athanassiades 2003 14


Rules of the Game
¾ If you answer the Knowledge Area question
correctly, then, on your next turn, you roll again.
– If you answer incorrectly, on your next turn, you draw
another question from the same Knowledge Area.
¾ You reach the end of the Knowledge Areas for a
Phase by:
– either by answering Knowledge Area questions
correctly,
– or drawing 10, 11, or 12,
– drawing an Outcome card, and perform the action on
the card.

Version 2003-12-02 (c) Dean Athanassiades 2003 15


Game Materials
¾ Game board
¾ Tokens
¾ Toolkit for each Project Phase
¾ Deck of cards with Knowledge Area
questions
¾ Deck of cards with Outcome Issues
¾ Random number cards

Version 2003-12-02 (c) Dean Athanassiades 2003 16


Supporting Handouts

Version 2003-12-02 (c) Dean Athanassiades 2003 17


Project Management
Framework
¾ PMI Project Management Framework
– Initiation
– Planning
– Execution
– Control
– Close

Source: PMBOK 2000, Project Management Institute

Version 2003-12-02 (c) Dean Athanassiades 2003 18


Initiating
¾ Recognizing that a project is worth doing
¾ Determining what the project should
accomplish
¾ Defining the overall project goal
¾ Defining general expectations of customers,
management, and other stakeholders
¾ Defining the general project scope
¾ Selecting the initial team members
Version 2003-12-02 (c) Dean Athanassiades 2003 19
Planning
¾ Refining project scope including balance between
results, time, and resource
¾ Listing tasks and activities that will lead to
achieving project goals
¾ Sequencing activities in the most efficient manner
possible
¾ Developing a workable schedule and budget for
assigning resources to the activities required to
complete the project
¾ Getting the plan approved by appropriate
stakeholders
Version 2003-12-02 (c) Dean Athanassiades 2003 20
Executing
¾ Leading the team
¾ Meeting with team members
¾ Communicating with stakeholders
¾ Fighting Fire
¾ Securing necessary resources to carry out
the project plan

Version 2003-12-02 (c) Dean Athanassiades 2003 21


Controlling
¾ Monitoring deviation from plan
¾ Taking corrective action to match progress with
plan
¾ Receiving and evaluating project change requests
from stakeholders and team members
¾ Adapting resource levels as necessary
¾ Changing project scope
¾ Returning to planning stage to make adjustments
to project goals
¾ Securing approval for changes from stakeholders

Version 2003-12-02 (c) Dean Athanassiades 2003 22


Closing
¾ Shutting down the project and disbanding
the team
¾ Learning from the project experience
¾ Reviewing the project process and
outcomes with team members and
stakeholders
¾ Writing a final report

Version 2003-12-02 (c) Dean Athanassiades 2003 23


Project Management
Knowledge Areas
¾ Integration ¾ Communications
Management Management
¾ Scope Management ¾ Quality Management
¾ Time Management ¾ Risk Management
¾ Cost Management
¾ Procurement
¾ Quality Management Management
¾ Human Resource
Management
Source: PMBOK 2000, Project Management
Institute

Version 2003-12-02 (c) Dean Athanassiades 2003 24


Integration Management
¾ Project plan development
¾ Project plan execution
¾ Integrated change control

Version 2003-12-02 (c) Dean Athanassiades 2003 25


Scope Management
¾ Initiation
¾ Scope planning
¾ Scope definition
¾ Scope verification
¾ Scope change control

Version 2003-12-02 (c) Dean Athanassiades 2003 26


Time Management
¾ Activity definition
¾ Activity sequencing
¾ Activity duration estimating
¾ Schedule development
¾ Schedule control

Version 2003-12-02 (c) Dean Athanassiades 2003 27


Cost Management
¾ Resource planning
¾ Cost estimating
¾ Cost budgeting
¾ Cost control

Version 2003-12-02 (c) Dean Athanassiades 2003 28


Quality Management
¾ Quality planning
¾ Quality assurance
¾ Quality control

Version 2003-12-02 (c) Dean Athanassiades 2003 29


Human Resource
Management
¾ Organization planning
¾ Staff acquisition
¾ Team development

Version 2003-12-02 (c) Dean Athanassiades 2003 30


Communication Management
¾ Communication planning
¾ Information distribution
¾ Performance reporting
¾ Administrative closure

Version 2003-12-02 (c) Dean Athanassiades 2003 31


Risk Management
¾ Risk management planning
¾ Risk identification
¾ Quantitative risk analysis
¾ Qualitative risk analysis
¾ Risk response planning
¾ Risk monitoring and control

Version 2003-12-02 (c) Dean Athanassiades 2003 32


Procurement Management
¾ Procurement planning
¾ Solicitation planning
¾ Source selection
¾ Contract administration
¾ Contract closeout

Version 2003-12-02 (c) Dean Athanassiades 2003 33


12 Rules for Project
Management Success
¾ Gain consensus on project ¾ Remember that people
outcomes count
¾ Build the best team that ¾ Gain formal and ongoing
you can support of management
¾ Develop a comprehensive and stakeholders
viable plan and keep it up ¾ Be willing to change
to date ¾ Keep people informed of
¾ Determine how much stuff what you are up to
you really need to get ¾ Be willing to try new
things done things
¾ Have a realistic schedule ¾ Be a leader as well as a
¾ Do not try to do more than manager
can be done
Version 2003-12-02 (c) Dean Athanassiades 2003 34
Initiation Tools
¾ Project Charter Statement

Version 2003-12-02 (c) Dean Athanassiades 2003 35


Planning Tools
¾ Scope
¾ WBS
¾ Resource Plan
¾ Budget Estimate
¾ Risk Assessment

Version 2003-12-02 (c) Dean Athanassiades 2003 36


Execution Tools
¾ Project dependent

Version 2003-12-02 (c) Dean Athanassiades 2003 37


Control Tools
¾ Status
Report
¾ Change Request

Version 2003-12-02 (c) Dean Athanassiades 2003 38


Closing Tools
¾ Milestone Acceptance Form
¾ Deliverable Acceptance Form

Version 2003-12-02 (c) Dean Athanassiades 2003 39

You might also like