Project Management Methodology Overview * * YIKES! What does

1
Project Management Methodology Overview
2
Agenda

• What is a project and why do we need methodology?
• The main processes of Project Management and the
  related deliverables
• Sample project
• Tools to make project management easier

3
Michele Raupp, PMP

• University of Illinois graduate
• 11 years in Marketing and Advertising
• Television
• Newspaper
• Cable
• Diversified company
• 10 years in the IT industry
• COBOL, Visual Basic, JCL, Lotus Script
• Project Coordination, Implementation, Staff
  Management

4
Project Management

• Project management is the discipline of
  organizing and managing resources in such a way
  that the project is completed within defined
  scope, quality, time and cost constraints. A
  project is a temporary, one-time endeavor
  undertaken to create a unique product or service,
  which brings about beneficial change or added
  value. This property of being a temporary and
  one-time undertaking contrasts with processes, or
  operations, which are permanent or semi-permanent
  ongoing functional work to create the same
  product or service over and over again. The
  management of these two systems is often very
  different and requires varying technical skills
  and philosophy, hence requiring the development
  of project management.

5
Project Management

• Project management is the discipline of
  organizing and managing resources in such a way
  that the project is completed within defined
  scope, quality, time and cost constraints. A
  project is a temporary, one-time endeavor
  undertaken to create a unique product or service,
  which brings about beneficial change or added
  value. This property of being a temporary and
  one-time undertaking contrasts with processes, or
  operations, which are permanent or semi-permanent
  ongoing functional work to create the same
  product or service over and over again. The
  management of these two systems is often very
  different and requires varying technical skills
  and philosophy, hence requiring the development
  of project management.

6
Project Management

• Project management is the discipline of
  organizing and managing resources in such a way
  that the project is completed within defined
  scope, quality, time and cost constraints. A
  project is a temporary, one-time endeavor
  undertaken to create a unique product or service,
  which brings about beneficial change or added
  value. This property of being a temporary and
  one-time undertaking contrasts with processes, or
  operations, which are permanent or semi-permanent
  ongoing functional work to create the same
  product or service over and over again. The
  management of these two systems is often very
  different and requires varying technical skills
  and philosophy, hence requiring the development
  of project management.

7
Points to Remember

• A project is temporary.
• A project is a one-time endeavor.
• Tasks are managed to ensure they are completed
  within time, scope, and cost constraints.

Triple Constraint
8
Project Management

• Project management is the discipline of
  organizing and managing resources in such a way
  that the project is completed within defined
  scope, quality, time and cost constraints. A
  project is a temporary, one-time endeavor
  undertaken to create a unique product or service,
  which brings about beneficial change or added
  value. This property of being a temporary and
  one-time undertaking contrasts with processes, or
  operations, which are permanent or semi-permanent
  ongoing functional work to create the same
  product or service over and over again. The
  management of these two systems is often very
  different and requires varying technical skills
  and philosophy, hence requiring the development
  of project management.

9
Project Lifecycle
Project Management Route
Application Development Route
10
Main Processes

• Initiation
• Planning
• Executing
• Controlling
• Closing

Based on PMBOK
11
Initiation

• The purpose of the Project Initiation Phase is to
  specify what the project will accomplish. As part
  of Initiation, you will define project
  objectives, scope, purpose and deliverables to be
  produced. You will also determine your project
  team, review the project, and gain approval to
  proceed to the next phase of the project,
  Planning.

12
Initiation Project Activities

• Describe project
• Determine value
• List objectives and measures of success
• Identify governance
• Develop estimates
• List assumptions
• List risks
• List constraints
• List dependencies

13
Initiation - Deliverables

• Project Charter - This deliverable defines the
  project objectives, contains high level estimates
  for what is needed to achieve those objectives
  and gives approval for resources to be assigned
  to the project.

14
Planning

• The purpose of Project Planning is to determine
  what needs to be done, by whom, and by when, in
  order to complete the project. It also details
  the processes that the project manager will use
  to manage the project.

15
Planning Project Activities

• Define Scope
• Create Schedule
• Define Budget
• Quality Planning
• Quality Control
• Quality Assurance
• Communication Planning
• Risk Planning
• Change Planning
• Resource Planning

16
Planning - Deliverables

• Project Plan
• Schedule
• Quality Plan
• Communication Plan
• Risk Plan
• Change Plan
• Resource Plan

17
Execution and Control

• The purpose of the Execution and Control phase of
  the project is to manage the delivery of the
  products and services.
• The project plan is executed and the team
  completes the activities identified in the
  project schedule.
• The Project Manager monitors and reports project
  progress and takes corrective action when needed.
• Project Management tools used during execution
  and controlling include risk, issue, quality and
  change control documentation and procedures.

18
Execution and Control - Project Activities

• Manage Issues
• Manage Change
• Manage Risks
• Manage Schedule
• Manage Communications
• Manage Quality
• Manage Procurement
• Manage Resources

19
Execution and Control
Project Management Route
Application Development Route
20
Execution and Control - Deliverables

• Products and Services
• Supporting Facilitating Documentation
• Product Development Lifecycle Deliverables

21
Closing

• The purpose of the Project Closing phase is to
  ensure that project documentation is completed
  and those items requiring further attention or
  support are transitioned appropriately before
  closing the project. This phase
• Concludes all project activities
• Administratively closes the project
• Turns the delivered product or service over to a
  support group
• Assesses project outcomes and team performance
• Documents and operationalize best practices and
  lessons learned
• Celebrates project success.

22
Closing Project Activities

• Gather Lessons Learned
• Create Project Summary
• Administrative Closeout
• Celebrate!

23
Closing - Deliverables

• Project Management Toolkit improvements/updates
• Recommendations to other processes
• Project Summary

24
Sample Project Website Redesign

• Initiation
• What is it and why are we doing it?
• What will the project create/implement?
• How will the success of the project be measured?
• Keep in mind that the measure of success here is
  not how many people use Illinois in a Box, but
  rather does the project meet the objectives and
  did it come in on time and on budget.
• What are the risks and issues?

25
Sample Project Website Redesign

• Planning
• What are the tasks that need to be completed?
• How long will they take?
• What is the budget?
• How will communications be managed? Risks?
  Issues?
• How will change requests be handled?

26
Sample Work Breakdown Structure
27
Sample Project Website Redesign

• Executing and Controlling
• Begin the work to create the new website
• As issues and risks occur, refer back to Issue
  and Risk Management Plans
• Follow Communications Management Plan for
  communicating project statuses
• Manage changes

28
Sample Project Website Redesign

• Closing
• Complete all activities
• Document Lessons Learned
• Turn finished product over to area that will have
  ultimate responsibility for it
• Assess success, measure objectives
• Celebrate!

29
What makes Project Management Easy

• Templates
• Repeatable processes
• Some processes are optional
• Quality is built-in
• Time spent up front in planning
• Proper planning prevents problems
• Less costly to fix mistakes early in the project
• Lessons Learned
• Update methodology and templates
• Feedback for next project

30
Wrap-up

• A project is
• Temporary
• A one-time endeavor
• Regulated by the Triple Constraint
• IPECC
• Project Management Methodology can be applied to
  anything
• Special thanks to Bradford Neavear, Rick Getty
  and Daryl Fritchey