ICPM

This email address is being protected from spambots. You need JavaScript enabled to view it. This email address is being protected from spambots. You need JavaScript enabled to view it. The International Community for Project Managers
Brought to you by TenStep, Inc.
2363 St. David's Square
Kennesaw, GA 30152
877-536-8434 or 770-795-9097

This email address is being protected from spambots. You need JavaScript enabled to view it.
You are here: Home Blogs Deming's 2nd Point in Project Management
Tuesday, 08 May 2007 20:24

Deming's 2nd Point in Project Management

Written by 
Rate this item
(0 votes)

 

Adopt a Philosophy of Cooperation Where Everyone Wins and Teach it to Everyone

Often, projects can become battlegrounds where the project manager and team are at odds with the sponsor and other stakeholders. These conflicts can arise when the project environment is not conducive to a win-win approach.

In project planning and initiation, clearly define the WIIFM (What’s in it for me) for everyone on the project.

This includes the sponsor, stakeholders, project team, and project manager. When you keep all parties in mind when planning your project, it helps create a win-win strategy in which everyone benefits. The functional managers from which you are pulling resources need to understand the benefit of the project to their department and the organization as a whole. This is important, and should be clearly communicated to everyone early and often.

During execution, a win-win philosophy will help keep individual issues from turning into project-killing conflicts. It creates the ‘one big team’ environment where people are willing to be creative and take educated risks, because they know they are supported by their team from all angles. If someone makes a mistake, they should not fear retribution from other parties, and they should not want to cover it up. The win-win environment spearheaded by the project manager and sponsor should make everyone think about issues and conflicts in terms of what is the best method of dealing with it for the whole project and everyone involved.

In the case of two or more project managers with their own teams working on a single complex project, Deming’s point #2 is even more important. In this situation it is easy to start pointing fingers at the other groups, withholding information, and other counterproductive practices. An acquaintance who works for another company told me about their situation. Any software development as part of a project is sent to a separate group. The software development group doesn’t care about her project; they just get sub-projects that are prioritized based on pre-determined criteria. The communication is sub-par, and she never knows when she will get her deliverables. I envisioned a big question mark on her project schedule. This is not a win-win project environment, and you can imagine the finger-pointing that inevitably results.

Additionally during execution, a project manager should not hold so tightly to the original requirements and throw up artificial barriers to positive changes. As long as the formal change management system is in place and utilized properly, any request should increase value for the whole project, period. If more money or time is required to increase the scope, the net effect should still be win-win for the organization. Sponsors must realize that increasing the scope will do one or more of 3 things: increase cost, delay the project, or decrease quality. The team atmosphere created by a win-win philosophy helps everyone get on the same page about these considerations.

When the project is finished, everyone should be involved in the celebration together. In the ‘us versus them’ scenario, a project team is segregated from rest of the stakeholders, and they usually celebrate separately.

If you have ever had the pleasure of working for a project manager with a win-win attitude, you know exactly why that is the way to run a project.


Deming's 14 Points
  1. Commitment from the Top to Continuous Improvement as a Way of Life
  2. Adopt a Philosophy of Cooperation Where Everyone Wins and Teach it to Everyone
  3. Inspection is a Tool for Improvement, Not a Whip
  4. Consider Costs and Benefits of the Entire System and Deliverable Lifetime
  5. Continuous Improvement
  6. Job/Task-Related Training
  7. Teach and Institute Leadership
  8. Drive Out Fear and Create Trust
  9. Break Down Departmental Barriers in Pursuit of a Common Goal
  10. No Slogans or Disingenuous Pep Talks
  11. Attribute Results to Processes
  12. Enable Pride of Workmanship
  13. Training Not Related to Job/Task
  14. Total Participation Starting From the Top


References and Resources

Managing for Quality and Performance Excellence
Deming and Goldratt
Out of the Crisis
The Deming Management Method
The New Economics
Four Days with Dr. Deming
Deming Route to Quality and Productivity
Deming The Way We Knew Him


Josh Nankivel is the Vice Chair of Special Projects for the Students of Project Management SIG of PMI, and a project management student/enthusiast. His website is http://www.pmstudent.com.

Read 5133 times Last modified on Sunday, 13 December 2009 19:15
Login to post comments

News and Promotions

Keep up to date with the latest happenings by signing up for our newsletter. Subscribe below.

Twitter Update

Who's Online

We have 406 guests and no members online

Got something to say?