Activity
Effective Project Management:
Presented by
(facilitator name)
Traditional, Agile, Extreme, Hybrid
8th Edition
Ch08: How to Launch a TPM Project
*
Using tools, templates, and processes to launch a TPM project
Recruiting the project team
Conducting the project kick–off meeting
Establishing team operating rules
Managing scope changes
Managing team communications
Assigning resources
Resource – leveling strategies
Finalizing the project schedule
Writing work packages
Summary of Chapter 8
Ch08: How to Launch a TPM Project
*
Explain how each of these contributes to the growing importance of project management in the business world.
Recruiting the Project Team
Team Operating Rules
Problem Solving
Decision Making
Conflict Resolution
Consensus Building
Brainstorming
Team Meetings
Scope Change Management Process
Communications Management Planning
Work Packages
Resource assignment
Finalize the project schedule
Tools, Templates & Processes Used to Launch a Project
Ch08: How to Launch a TPM Project
*
Explain how each of these contributes to the growing importance of project management in the business world.
A project team is a group of professionals committed to achieving common objectives, who work well together and who relate directly and openly with one another to get things done.
Project team membership
Co-Project manager – developer (chosen before Scoping)
Co-Project manager – client (chosen before Scoping)
Core team (chosen before Planning)
Developer team (chosen before Launching)
Client team (chosen before Launching)
Contracted team (chosen after Launching)
What is a Project Team?
Ch08: How to Launch a TPM Project
*
Commitment
Shared responsibility
Flexibility
Task-oriented
Ability to work within schedules and constraints
Willingness for trust and mutual support
Team-oriented
Open-minded
Ability to work across structure and authorities
Ability to use project management tools
Characteristics of the core team
Ch08: How to Launch a TPM Project
*
Must understand their business unit processes
Must be able to make decisions and commitments for their business unit
Client Team Members
Ch08: How to Launch a TPM Project
*
Little variance in times they are available
Know how their tasks relate to the project
Commitment can be a problem
Quality of work may be poor
May require more supervision than core team
Contract Team Members - Implications
Ch08: How to Launch a TPM Project
*
Developing a team deployment strategy
Developing a team development plan
Balancing a Team
Ch08: How to Launch a TPM Project
*
Work methods and procedures
Knows appropriate technology
Associate attraction and retention
Staffing flexibility
Service and product quality use
Rate of output
Decision making
Reduced staff support level
Reduced supervision
Where Project Teams Can Improve
Ch08: How to Launch a TPM Project
*
Team Member Responsibilities
- Open communication
- Good listening skills
- Shared goals
- Positive outlook
- Creativity
- Respect for others
- Growth and learning
Ch06: How to Launch a TPM Project
*
Sponsor-led part
Introduce the sponsor to the project team
Introduce the importance of the project by the sponsor
Introduce the project (client)
Introduce the project (project manager)
Kick-Off Meeting Agenda
Ch08: How to Launch a TPM Project
*
Introduce the project team members to each other
Write the Project Definition Statement
Establish team operating rules
Problem solving
Decision making
Conflict resolution
Consensus building
Brainstorming
Team meetings
Review the project plan
Finalize the project schedule
Write work packages
The Working Session Project Manager-led Agenda
Ch08: How to Launch a TPM Project
*
Expands the POS
Project objectives
Assumptions, risks and obstacles
Project Definition Statement – Contents
Ch08: How to Launch a TPM Project
*
As a basis for continued project planning
To clarify the project for the project team
As a reference that keeps the team focused in the right direction
As an orientation for new team members
As a method for discovery by the team
Project Definition Statement – Purpose
Ch08: How to Launch a TPM Project
*
Problem solving
Decision making
Conflict resolution
Consensus building
Brainstorming
Team meetings
Establishing Team Operating Rules
Ch08: How to Launch a TPM Project
*
Define the problem & the owner
Gather relevant data and analyze causes
Generate ideas
Evaluate and prioritize ideas
Develop an action plan
Five Steps to Solving a Problem
Source: Creative Problem Solving and Opportunity Finding
J. Daniel Couger, 1995
Ch08: How to Launch a TPM Project
*
Directive
Participative
Consultative
Decision Making Styles
Ch08: How to Launch a TPM Project
*
Conflict Resolution
Conflict is good.
Conflict is bad.
I’ll win at any cost!
Ch08: How to Launch a TPM Project
I have a differentidea!
*
Conflict Resolution
Ch08: How to Launch a TPM Project
- Avoidant
- Combative
- Collaborative
*
Consensus Building
Be careful--a consensus decision that equally satisfies all parties may be a bad decision after all.
Ch08: How to Launch a TPM Project
*
- Assemble individuals with knowledge of problem area
- Throw any/all ideas on the table
- Continue until no new ideas are uncovered
- Discuss items on the list
- Solutions begin to emerge
- Test each idea with an open mind
Brainstorming Method
Look for solutions that no individual could identify but the group may identify.
Ch08: How to Launch a TPM Project
*
What is your purpose?
How often? How long?
Who should attend?
Do we need an agenda?
Are there minutes? Who takes them? Who gets them?
Team Meetings
Ch08: How to Launch a TPM Project
*
Before the Meeting
Is the meeting necessary?
Determine the purpose of the meeting
Set the ground rules for the discussion
Determine who really needs to be present and only invite those people
Make notes and rehearse your presentation
Start and end the meeting on time
Guidelines for Managing Meetings
Ch08: How to Launch a TPM Project
*
During the Meeting
Specify a time limit and stick to it
Identifying the specific objectives
Gather input from the participants
Keep things moving
Use visual aids
Periodically summarize the results of the discussion in terms of consensus achieved or disagreements still in progress
Assign action items to team members
Guidelines for Managing Meetings
Ch08: How to Launch a TPM Project
*
After the Meeting
Time, place and instructions for the next meeting
Time and place of the meeting and list of attendees with their project role
Agenda items discussed
Decisions reached or held for further studies
Action items and persons responsible for follow up and reporting back to the team at the next meeting
Guidelines for Managing Meetings
Ch08: How to Launch a TPM Project
*
Daily status meetings
Problem resolution meetings
Project review meetings
Project Meetings
Frequency
Length
Purpose
Team Room
Ch08: How to Launch a TPM Project
*
- 15 minutes
- Everyone stands
- Only reporting on tasks open for work and not yet done
- Status
- I’m on plan
- I am x hours behind schedule but have a plan to be caught up by this time tomorrow
- I am x hours behind plan and need help
- I am x hours ahead of plan and available to help
Daily Status Meetings
Ch08: How to Launch a TPM Project
*
- Only attended by those involved in the problem
- Who owns the problem?
- What is the resolution?
- When will it be completed?
Problem Resolution Meeting Agenda
Ch08: How to Launch a TPM Project
*
- Held at project milestone events
- Project review panel
- Formal presentation of project performance to date
Project Review Meetings
Ch08: How to Launch a TPM Project
*
Physical layout
Variations
Operational uses
Team War Room
Ch08: How to Launch a TPM Project
*
Typical Scope Change Management Process
Submit
change
request
Change
approved for
implementation
Request
impact study
Review
impact
study
Review
change
request
Reject
Reject
Rework & Resubmit
Rework & Resubmit
Ch08: How to Launch a TPM Project
*
What is the expected benefit of the change?
How would the change affect the project’s cost?
How would the change affect the project’s schedule?
How would the change affect the software’s quality?
How would the change affect the project’s resource allocation?
Can the change be deferred to a later stage of the project or a later version of the software?
Is the project at a point when making the change would risk destabilizing the software?
Project Impact Statement - Contents
Ch08: How to Launch a TPM Project
*
It can be accommodated within project resources and time lines
It can be accommodated but will require extension of deliverable schedule
It can be accommodated within the current deliverable schedule but additional resources will be needed
It can be accommodated but additional resources and extension of deliverable schedule will be required
It can be accommodated with a multiple release strategy and by prioritizing the deliverables across the release dates
It cannot be accommodated without a significant change to the project
Project Impact Statement – Possible Outcomes
Ch08: How to Launch a TPM Project
*
Scope Change Request Form
Project Name
Change Requested By
Date Change Requested
Description of Change
Business Justification
Action
Approved By
Date
Ch08: How to Launch a TPM Project
*
Business needs change or are discovered during the project
Scope change requests are expected
Project team will analyze the request’s impact on the project plan
Project impact statement will define alternatives for accommodating the request
Client will choose the alternative to be followed
Project manager will adjust project plan accordingly and inform the client
Tips to help the client understand scope change
Ch08: How to Launch a TPM Project
*
A percentage (5-10%) of the project duration is set aside as a time contingency for processing and incorporating scope change requests.
Utilizing a Scope Bank to store prioritized functions and features not yet integrated into the solution will help manage Management Reserve.
Management Reserve
Ch08: How to Launch a TPM Project
*
Set up a scope request bank account with an initial deposit of time (5-10 percent of total project work time) to be used to process cope changes and adjust the schedule.
Utilize the Scope Bank to store prioritized change requests not yet integrated into the solution.
Change requests can be handled at the end of a project cycle or as needed.
Scope Bank
Ch08: How to Launch a TPM Project
*
Establishing a Communications Model Including:
Timing
Content
Choosing Effective Channels
Managing Team Communications
Ch08: How to Launch a TPM Project
*
Communications Management – The Process
Ch08: How to Launch a TPM Project
Sender
Receiver
Generates
the idea
Encodes
the message
Decodes
the message
Checks
the meaning
Feedback
Transmits
through a channel
*
- One-to-one
Conversations (in person and on the phone)
Meetings
- Electronic
Email messages
Web sites
Databases
- Written
Memos
Letters
Documents
Reports
Two-way
One-way
Communications Management – Types
Ch08: How to Launch a TPM Project
*
Communications Management – Interfaces
Project
Manager
Client
Team
Managers
Project
Team
Members
Sponsor
Public
3rd Parties
Ch08: How to Launch a TPM Project
*
Delegation: RASCI Matrix
R= Responsible, accountable for successful completion
A= Needs to Approve decisions
S= Will provide Support for the “R”
C= Available to Coach and Consult
I= Needs to be kept informed of status
R
I
C
S
A
Confirm customer approval of scope
Choose project team
R
Define Budget
R
I
Plan project
R
S
Plan Kick-Off Meeting
R
I
Ch08: How to Launch a TPM Project
*
Expanded Variation of the RASCI Matrix
Ch08: How to Launch a TPM Project
Y
End
B C
7/14/08
7/16/08
7/14/048
Harry
D
N
D
A
7/13/08
7/10/08
7/5/08
Cheryl
C
Y
D
A
7/13/08
XXXX
7/5/08
Bob
B
Y
B
Start
7/2/08
7/3/08
7/1/08
Jack
A
Comments
CP?
Succ.
Pred.
Est. End
End Date
Start Date
Task Lead
Tasks
*
Assigning Resources
Ch08: How to Launch a TPM Project
*
Utilizing available slack
Shifting the project finish date
Smoothing
Resource-Leveling Strategies
Ch08: How to Launch a TPM Project
*
Further decomposition of tasks
Stretching tasks
Assigning substitute resources
Alternative Methods of Scheduling Tasks
Ch08: How to Launch a TPM Project
*
Launch the Project – Finalize Resources & Schedule
Ch08: How to Launch a TPM Project
A1
3
C1
3
B1
2
C2
2
B2
2
C3
1
A2
2
M
T
W
R
F
S
S
M
T
W
R
F
S
S
Duffy
Ernie
Fran
a1
a1
a1
b1
b1
a2
a2
b2
b2
b2
c1
c1
c1
c2
c2
c2
c3
c3
*
Launch the Project – Work Packages
A Work Package is a brief description at the subtask level that describes how a task will be completed. It is a primitive project plan.
Work Packages should be written for:
- Critical path tasks
- High-risk tasks
- Tasks requiring scarce resources
- Tasks with large duration variances
Ch08: How to Launch a TPM Project
*
Launch the Project – Work Package Assignment Sheet
Ch08: How to Launch a TPM Project
*
Launch the Project – Work Package Description Form
Ch08: How to Launch a TPM Project
*