This document provides an overview of project management. It defines a project as a temporary production line established to deliver a unique product or service. It discusses the key activities of project management, including identifying requirements, setting goals, managing risks, and communicating. It also covers popular project management methodologies like PRINCE2 and PMBOK, and notes that the project manager requires skills in management, communication, and adapting to different environments and cultures. The document advocates for a pragmatic approach to project management with open communication and focus on quality.

1. PROJECT MANAGEMENT
AT A GLANCE
Ed van de Griend - 25/5/2009

2. Project management
at a glance
 Content
 What?
 Definition of project management & activities
 Why?
 Why should we define a project?
 How?
 What methodology shall we use?
 When?
 Project, or not?
 Who?
 What do you require from your Project Manager?

3. PM – What?
 A project is a temporary [specific start and end]
production line [team, budget, method,
location, time schedule] established to deliver
[produce] an unique product or service [with
predefined quantity, predefined quality]
 A project is part of a production life cycle
 A project needs an Executive who delegates
the project management tasks to a PM
 A project needs a Business Case which has a
positive value at the bottom

4. PM – What?
 Project management consists of activities
 Identifyrequirements
 Set up goals (quantity and quality)
 Test feasibility
 Get the right balance between quality, scope, time
schedule and costs
 Adjust specifications and plans
 Manage risk, issues and perception (stakeholder
management)
 Communicate

5. PM – Why?
 Pro  Restart able and
 Predefined product repeatable project
produced due to implicit and
explicit
 Dedicated
documentation
monitoring during
production
 Clear costs related
to scope changes
 Project controls
defined to assure
costs, time & quality

6. PM – How?
Methodology  Prince2
Consists of  UK Government
 Processes &  PMP/PMBOK®
Decision points  US/APAC standard
 Terminology
 J.B.F.
 Phases
 No standard
 Techniques
 Templates
 Organization

7. PM – How? Prince2
 Process groups  Components
 Starting up a Project  Business Case
 Initiating a Project  Plans
 Directing a Project  Organization
 Managing Stage  Risk Management
Boundaries  Quality Control
 Controlling a Stage  Change Control
 Planning  Configuration Mgt
 Managing Product  Controls
Delivery
 Closing a Project

8. PM – How? PMBOK®
 Process groups  Knowledge areas
 Start-up  Integration
 Scope
 Planning
 Time
 Execution
 Costs
 Close down
 Quality
 Monitoring
 Team
(continuously)
 Communication
 Risk
 Purchasing

9. PM – When?
 All kind of situations  Define projects as
 Product development response to
 Organization change  A client’s request
 Service introduction  A department’s
 Implementation of
requirement
software  A technology push
 Building facility  A new or changed law
 Implement new
procedure
 Response to RFI

10. PM – When?
 Result of portfolio  Type of job =
{xxx,yyy}
and program
 No project:
management
 Else
 Criteria to be
defined
 Define project when:
$ > €25000
 Team > 3 suppliers
 Schedule > 6 weeks
 Stakeholder = xxx

11. PM – Who?
 Skill set PM  Management skills
 PM knowledge (recruiting,
(method, template, purchasing,
processes) negotiation, financials,
administrative,
 Standards, laws, organization, team
knowledge of builder)
application area (ISO,
 Social skills
privacy)
(communication, multi
 Knowledge of culture, directive
environment (habits, influence, leading,
language, culture, motivation, delegation,
time zones, physical problem solving)
area, weather)

12. PM – Who?
 More administrative  Communication,
tasks can be meeting setup,
delegated inbound mail
 Schedule monitoring
 Resource mgt
& triggering
 Standard template
 Quality control
development
 Configuration mgt
 Risk management
 Use of tools

13. PM – Next?
 Define your standard  Default project phase
definitions definition related to
 Choose your application area
methodology  Level of PM process
 How would you share execution during
documentation projects
 What tasks will be
delegated
 Which tools to be used
 Checklist development
 Training

14. Pragmatic approach with open communication and quality
Mail: info@ipmarea.com
2009 © IPMArea.com