pm101: lecture 20 · 2020. 5. 10. · zavanak.com © eric woodcock 2020 pm101: lecture 20 output...
TRANSCRIPT
© Eric Woodcock 2020ZAVANAK.com
PM101: Lecture 20Output delivery and progression
1
© Eric Woodcock 2020ZAVANAK.com
The typical project life cycle
Definition
Planning
Decision
Production
Delivery
Progression
Deciding what to do and why
Working out how to do it, who will do it and when
Getting approval to go ahead
Creating and testing the product or service, controlling progress
Getting the customer to accept it
Closing down, and learning for next time
2
© Eric Woodcock 2020ZAVANAK.com
The actual project life cycle
Definition
Planning
Decision
Production
Delivery
Progression
Approval to spend resources on
planning
Approval to begin full scale
production
Acceptance that the output is satisfactory
3
© Eric Woodcock 2020ZAVANAK.com
Achieving a smooth delivery of the project output is a goal that should be at the forefront of the project manager’s mind from the very start.
Photo: Fauxels from Pexels
4
© Eric Woodcock 2020ZAVANAK.com
Why it is difficult to end the project
The customer may keep on asking for extra pieces of work
There may be an ongoing dispute with the customer
Project team members are reluctant to finish their work off
Customers want to maintain some grip on the supplier in case of problems with the output
Too many projects spend 90% of their time 90% complete
Ensure the scope and specification is clear and change control is effective
Good fences make good neighbours
Make sure people have a clear future after the project. Offer references
Work hard to build real trust so the customer relationship is fair and open
Maylor, H. 3rd ed. (2005). Project management. Harlow, UK: Pearson Education.
5
© Eric Woodcock 2020ZAVANAK.com
Ways to hasten project delivery
Have incentives for the project team
Ensure all activities are completed
Resist requests for extra pieces of unpaid work
Ensure the customer believes the output will produce the desired
benefits
Ensure all the key stakeholders are
satisfied
Ensure all agreed warranty and after-sales support
arrangements are in place
Maylor, H. 3rd ed. (2005). Project management. Harlow, UK: Pearson Education.
6
© Eric Woodcock 2020ZAVANAK.com
Managing perceptions
Satisfaction = Perception - Expectation
Responsiveness
Communication
Competence and professionalism
Courtesy
Accessibility
Integrity
Prompt and complete answers
Open and frequent
Conscientious, skilful and experienced
Polite and sensitive to cultures and rules
Available at all reasonable times
Truthful at all times
7
© Eric Woodcock 2020ZAVANAK.com
Approaches to delivery
Full output “big bang”
Pro
ject
sta
rt
Benefits only come at the end
Few early warnings of customer problems
Teething troubles may be severe
Too late to fix the output if it is not quite right
All or nothing – no opportunity for a partial solution
The supplier is likely to be paid later
Sometimes there is no choice
8
© Eric Woodcock 2020ZAVANAK.com
Approaches to delivery
Output part 2
Output part 3 Output part 5Output part 1
Output part 4
Pro
ject
sta
rt
Benefits some earlier – ‘quick-wins’
Customer problems are evident with time to resolve them
Sorting out issues with early output avoids more later on
In-service problems can be sorted out as you go along
If the project stops, the customer still gets a useful product
The supplier can be paid sooner for output as it is delivered
9
© Eric Woodcock 2020ZAVANAK.com
The transition plan
Think like the customer
What would make the customer refuse the take delivery of the output?
What would make the customer especially happy?
Ask the customer and the end users if possible. This is part of the customer project.
Pinto, J. 2nd ed. (2010). Project management, achieving competitive advantage. Upper Saddle River, NJ, US: Pearson
Prentice-Hall; Turner, J, ed. 4th ed. (2007). Gower handbook of project management. Aldershot, UK: Gower.
10
© Eric Woodcock 2020ZAVANAK.com
Preparing for deliveryPoint of delivery
(for each part of the output)
Real sustained success means locking into the
mainstream
“Bring in the systems guys”
Prepare documentation, training materials, etc
Set up customer support – train own staff, rehearse
Plan the handover
Help end users get ready to use the output
Prepare the decision makers to accept output
Close contracts, audit invoices and payments
Get everything finished
Use task forces to resolve hard issues
Change the project manager?
Train the users
Handover event
1 month6 monthsTime
Peters, T. (1999). The project 50. New York: Knopf.
11
© Eric Woodcock 2020ZAVANAK.com
Managing the transition
Support the users
Sort out teething troubles
Bed in maintenance regime
Deal with warranty claims
1 month 1 year 3 years
Discuss enhancements and extensions
Real sustained success means locking into the
mainstream
Time
Point of delivery(for each part of the output)
Train the users
Handover event
Peters, T. (1999). The project 50. New York: Alfred A. Knopf.
12
© Eric Woodcock 2020ZAVANAK.com
Project governance
Organisation management board
Project board
Project manager
Project team
The project board:
• approves the business case
• starts the project
• allows each stage to begin
• approves payments
• approves changes
• resolves major issues
• signs off completed outputs
• closes the project
Sponsor
13
Senior relevant experts and executives
© Eric Woodcock 2020ZAVANAK.com
Celebrate!
A symbolic event that marks the passage of the output into use
Gives powerful stakeholders a chance to endorse the project
There can be an ‘official’ celebration for the outside world…
… and celebrations for the project team and partners
Peters, T. (1999). The project 50. New York: Knopf. Photo: NASA Johnson, Creative
Commons, Attribution-NonCommercial-NoDerivs 2.0 Generic (CC BY-NC-ND 2.0)
14
© Eric Woodcock 2020ZAVANAK.com
The typical project life cycle
Definition
Planning
Decision
Production
Delivery
Progression
Deciding what to do and why
Working out how to do it, who will do it and when
Getting approval to go ahead
Creating and testing the product or service, controlling progress
Getting the customer to accept it
Closing down, and learning for next time
15
© Eric Woodcock 2020ZAVANAK.com
Stages of team development
Forming
Storming
Norming
Performing
Adjourning They learn lessons and disperse
Tuckman, B and Jensen, M (1977) “Stages in small group development revisited “, Group and
Organisational Studies, 2, p419, cited in Pinto (2007, p 191)
Re-forming
Release people sensitively from the project
Capture new knowledge before they go
Analyse knowledge and translate it into useful formats
Store information in ways it can be used
Embrace the growing role of social media
16
© Eric Woodcock 2020ZAVANAK.com
Post project review
Source: PRINCE2, TSO (2005). Photo: Amanda Mills, USCDCP, Pixnio.com
Have the expected benefits been realised?
Have the success criteria been met?
Have there been problems in use of the product or service?
User feedback
Customer reaction
Product or service
performance
Impact on the organisation
Better client
approach
Potential new activities
Better supplier
approach
Supplier team
Client team
17
© Eric Woodcock 2020ZAVANAK.com
The project manager makes their mark
Ensure a fabulous transition
Embed the output in the mainstream
Find and bring in an inspired successor
Manage your reputation
Celebrate success
Send out lots and lots of thank you notes
Peters, T. (1999). The project 50. New York: Knopf. Photo: Laurabusiness0, Pixabay
18
© Eric Woodcock 2020ZAVANAK.com
Delivery and progression: core ideas19
The project manager should be managing towards a smooth delivery of the output all the way through the Production phase, ensuring that the customer is satisfied with the way the work is being conducted.
Ending the project may be difficult because the client is reluctant to release the project team.
Achieving a smooth delivery means deliberately working towards a definite end point.
An agreed transition plan sees the project output transferred into the possession of a client well-prepared to accept it.
If it is possible, developing the output as a series of modules (rather than one big entity) brings the client early benefits.
The end of the project should be celebrated, and people thanked properly for their contributions.
Capturing knowledge and lessons from project participants should be done seriously. After a period of time the project supplier and client should have an honest review to discuss what can be learned from the project.