Professional Documents
Culture Documents
1
Project Management Institute
•Initiation
•Scope Planning, Definition and Verification
•Scope Change Control
•Requirements Definition
•Work Breakdown Structure
•Product Baseline Control
•Project Baseline Control
4
Project Time Management
Processes required to ensure timely completion of the
project.
•Activity Definition
•Activity Sequencing
•Activity Duration Estimating
•Project Schedule Development
•Schedule Control
•Schedule Estimating
•Critical Path Analysis
•Schedule Tracking
5
Project Cost Management
Processes required to ensure that the project is
completed within the approved budget.
•Resource Planning
•Cost Estimating
•Cost Budgeting
•Cost Control
•Cost and Schedule Control System
•Cost Analysis
6
Project Quality Management
Processes required to ensure that the project will
satisfy the needs for which it was undertaken.
7
Project Human Resource Management
•Organizational Planning
•Staff Acquisition and Development
•Project Leadership
•Staffing Plan
•Project Organization
•Project Team Building
8
Project Communication Management
9
Project Risk Management
The systematic process of identifying, analyzing, and
responding to project risk. It includes maximizing the
probability and consequences of positive events and
minimizing the probability and consequences of adverse
events to project Objectives.
•Procurement Planning
•Solicitation Planning
•Solicitation
•Source Selection
•Contract Administration
•Contract Closeout
11
Project Stakeholder Management (added in 2013)
Processes required to identify all individuals or
organizations impacted by the project, analyzing
stakeholder expectations and impact on the project,
and developing the appropriate management
strategies for effectively engaging stakeholders in
project decisions and execution.
• Identification of Stakeholders
• Planning Stakeholder Management
• Managing Stakeholder Engagement
• Controlling Stakeholder Engagement
What is going to be our Approach for the
Project?
• The first decision made on any project is what
methodology/approach is best suited for that
type of project
• One size/type Project Management approach
does not fit all projects…comfortably
Plan
Define
Execute
Plan
Partition the
Solution
Execute
Monitor ...
Monitor
Control
..
Monitor
Control Control
Close Close
Taxonomy of Project Management Approaches
• Adaptive (Agile) Approach
– What if the goal is clear but the solution is not clear?
– Project will follow a very detailed plan (not built at the beginning of the
project)…the plan is built in stages at the completion of each project
cycle/phase… it is iterative.
– The budget and time line is specified at the outset of the project
• Adaptive Approach works well:
– If you feel the requirements are apt to change
– If you feel you will learn about remaining requirements during the course
of doing the project
– If the project is oriented to new product development or process
improvement
– If the development schedule is tight and you can’t afford rework or
planning
– Requires that empowered individuals are readily available for input.
Adaptive Approach (Iterative)
Define Detailed
Planning
High end
Incorp. Monitor &
Planning
Feedback Control
Launching
Customer
Feedback
Closing
Taxonomy of Project Management Approaches
• Extreme Approach
– The goal is not clear…solution is not clear
– Projects do not follow a plan in the manner deployed
with the traditional or adaptive approaches
– The project proceeds based on informed, non-specific
“guesses” of what the final goal (or solution) will be
– At the conclusion of each cycle, what was learned or
discovered is factored into a newly specified goal
– Uses an open, elastic, undeterministic approach. Best
fitted for R&D Projects
Measuring and Reporting – Metrics
(Can build trust, communicate progress, expose problems and illustrate
effectiveness of the Process)
Traditional/Waterfall Adaptive/Agile
• Focus is on tracking efforts • Focus on tracking what has been
incrementally delivered
on each activity
• Velocity
• GANTT Chart • Burn Down – what features have
• Percent complete been completed
• Burn Up – what features have been
• Time per team member per promised
task • Running tested features
• Actual time versus • Defect density
estimated time • Cycle time
• Code quality
• Earned Business Value