Project Management

Time to turf these project management terms!

From the Easy in theory, difficult in practice Blog
by
My musings on project management, project portfolio management and change management. I'm a firm believer that a pragmatic approach to organizational change that addresses process & technology, but primarily, people will maximize chances for success. This blog contains articles which I've previously written and published as well as new content.

About this Blog

RSS

Recent Posts

Leading Through Crisis Means Leading Through Context

"It's the end. But the moment has been prepared for." - retirement lessons from the Doctor

Just because they are non-critical, doesn't mean they are not risky!

Just because they are non-critical, doesn't mean they are not risky!

How will YOU avoid these AI-related cognitive biases?

Categories

Agile, Artificial Intelligence, Career Development, Change Management, Communications Management, Decision Making, Governance, Hiring, Kanban, Lessons Learned, Personal Development, PMO, Portfolio Management, Project Management, Resource Management, Risk Management, Risk Management, Schedule Management, Scheduling, Tools

Date

linkedin twitter facebook Request to reuse this  


Project management practices have been used since human beings first started to work together to achieve greater outcomes than they could have accomplished as individuals. Modern practice of the profession started in the 1950's so it is natural that certain practices, tools and nomenclature will be discarded as the profession evolves.

Unfortunately, some anachronistic project management terms still linger in spite of overwhelming evidence that their time has passed.

Waterfall & Traditional

Waterfalls usually provide a one-way journey for those unlucky enough to take a ride over them. Even the most deterministic lifecycle will provide some instances (no matter how small) of iterating back. Traditional is a subjective term. The Manifesto for Agile Software Development was signed in 2001 and before its arrival launched agile into the mainstream, adaptive lifecycles had been used for many years. Traditional could be equally applied to deterministic and adaptive lifecycles when we consider that many new project managers were born around Y2K!

Resources (when referring to people)

The PMBOK's Project Resource Management knowledge area might cover the management of both people and materials, but calling our team members "resources" encourages poor management practices by equating them to commodities and furthers the myth and resulting risks of fungibility. There are many positive synonyms which can be used to reference the people on our teams including their names(!), "talent", "contributors" and "performers" so there's no reason to use such a divisive term.

Best practices

I applaud the efforts of the PMBOK Guide, Sixth Edition volunteer team in adding the Tailoring Considerations section to each knowledge area chapter but this is just the first step in a long journey of providing guidance for adapting project management practices and tools to the context of a specific project and organizational culture. Certain other professions might have standard procedures which are appropriate in all circumstances (e.g. turn the power off before working on an electrical circuit) but while the principles of project management are universally applicable, specific practices or tools are not.

The practice of trepanation was used in ancient times as a cure for the evil spirits possessing sick people's heads. However, if a doctor was to approach your head with a drill, in all except the most extreme circumstances, you would be forgiven for running away! If we wish to demonstrate the evolution of the project management profession, similar Spring cleaning is needed with our lexicon.


Posted on: August 26, 2018 07:00 AM | Permalink

Comments (24)

Page: 1 2 next>

Please login or join to subscribe to this item
avatar
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates New Westminster, British Columbia, Canada
Good post Kiron, Cheers

avatar
Drew Craig Sr. Agile & Product Coach| Vanguard Philadelphia, Pa, United States
Great points, Kiron. Will be more cautious when slinging the 'traditional' tem around. Also, spot on for 'resources'. I have brought that up in meetings before, and though most recognize its negative conentation, often remains as is. In my next allocation exercise, I will modify to 'talent' allocation. Maybe I can start the shift away from bad habits.

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Thanks Rami & Andrew - as with everything else, as leaders we need to model the right behavior (and nomenclature) we'd want our team members and other stakeholders to use.

Kiron

avatar
Tamer Zeyad Sadiq Assistant Cost Manager| Turner & Townsend Riyadh, Ar Riyad, Saudi Arabia
Good article Kiron about changing of PMBOK last version!!!

avatar
Girija Ramakrishnan Chennai, Tamilnadu, India
Good post, Kiron. Though we've Talent Acquisition teams to identify project 'contributors', usually team members are still referred as 'resources'. I am not a supporter of this word - resources for people and I'll also make changes at my end like Andrew does.

Thanks for sharing !!

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Thanks Tamer & Girija - change happens one person (not resource!) at a time!

Kiron

avatar
Sante Delle-Vergini, PhD Senior Project Manager| Infosys Melbourne, Victoria, Australia
Change in terminology is relevant to the times. What we change today may not be relevant tomorrow. But granted we need to use universal terminology.

avatar
Pravin Kumar Shrivastava Associate Vice President| Aithent Technologies Pvt Ltd Gurgaon, Haryana, India
Good post and useful insight. Thanks for sharing.

avatar
Brian Riehle IT Program Manager| US Government Fairfax, Va, United States
Love the aspect of doing away the generic term "resources". People are often the most important aspect of any project. "Contributers" is a great alternative! Thanks Kiron!

avatar
Vincent Guerard Coach - Trainer - Speaker - Advisor| Freelance Mont-Royal, Quebec, Canada
Nice points, Thanks Kiron

Ressource is to me the one that needs to change, think I like better "Contributors" give a reward to individuals in the project.

avatar
Cibin Thomas Reston, Va, United States
Thanks for sharing Kiron!!

avatar
Eduin Fernando Valdes Alvarado Project Manager| F y F Fabricamos Futuro Villavicencio, Meta, Colombia
Thanks for sharing,

avatar
Damian Perera Monitoring & Evaluation Specialist| Chrysalis Mellawagedara, Western Province, Sri Lanka
It's great to have tailoring considerations under each project management knowledge area in the PMBOK 6th edition.

avatar
Damian Perera Monitoring & Evaluation Specialist| Chrysalis Mellawagedara, Western Province, Sri Lanka
It's great to have tailoring considerations under each project management knowledge area in the PMBOK 6th edition.

avatar
Guilherme Caloba Production Engineer| PETROBRAS Rio De Janeiro, Rio De Janeiro, Brazil
Short and to the point. Thank you!

avatar
Anish Abraham Privacy Program Manager| University of Washington Auburn, Wa, United States
Good article, Kiron and thanks for sharing.

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Wow - this post must have touched a few nerves given the volume of feedback I've received!

Thanks everyone for the kind words!

Kiron

avatar
Henry Hattenrath Project Consultant| Tectonic Engineering MSA LLC New York, Ny, United States
Kiron - You are on target. The sixth edition definition is a step backwards, and for practitioners it provide an incomplete scope that crosses other practice areas as well as integration with schedule practices and contract standards regarding work restrictions, access constraints and necessary support services. For rail transit project, the often overlooked resources includes track outages, personnel for supervising movement of on-track vehicles, and protective personnel for support services.

Fifth Edition - Resource: Skilled human resources, equipment, services, suppliers, commodities, materials, budget or funds.

Sixth Edition - Resource: A team member or any physical item needed to complete the project.

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Thanks Henry - perhaps the PMBOK Guide is a case study of that old cliche that a camel is a horse created by a committee?

Kiron

avatar
Michael Delaney Partner| Delaney Management LLC West Chester, Pa, United States
Good post, it is important to update our language. I often use the term roadmap and realize in the era of google maps many do not know what one is.

Page: 1 2 next>

Please Login/Register to leave a comment.

ADVERTISEMENTS

If a woman has to choose between catching a fly ball and saving an infant's life, she will choose to save the infant's life without even considering if there is a man on base.

- Dave Barry

ADVERTISEMENT

Sponsors