Podcast: Play in new window | Download
Subscribe: RSS
PMI Talent Triangle: Ways of Working (Technical)
Welcome to the PMO Strategies Podcast + Blog, where PMO leaders become IMPACT Drivers!
NOTE: For the very best experience, listen to this episode on your favorite podcast provider here.
This episode is sponsored by
Show Notes:
Hey there, IMPACT Driver!
In this episode, we talk about the very real issues organizations and PMs and Agilists are facing as we figure out how to deliver on our organization’s strategy. We tackle the big “us and them” conversations that are happening in companies around the world and talked about ways to move past the methodology wars to solving the real business problems we are there to address. And yes…that’s the punchline…sometimes it’s easy to lose focus on the real reason we are all gainfully employed in our organizations. We are there at the behest of the business to serve the business needs and help the organization deliver on its strategy. That could play out in a lot of ways in each organization, but the goal is to spend our energy focusing on the outcomes we are striving to achieve in our organizations instead of getting caught up in outputs.
Check out this week’s podcast episode to learn:
- why both the Agile and PMO camps are right and wrong
- how to find common ground to move forward productively
- how to get straight on the terminology for more effective conversations
- services a PMO can provide to support Agile projects
- benefits of Agile that high-IMPACT PMOs love (and can leverage)
If you love this podcast, please leave a rating and review on your favorite podcast player.
T
hanks for taking the time to check out the podcast!
I welcome your feedback and insights!
I’d love to know what you think and if you love it, please leave a rating and review in your favorite podcast player. Please leave a comment below to share your thoughts. See you online!
Warmly,
Laura Barnard
@Laura you really need to be cautious about following PMI too closely. Their PMBOK Guide has never worked, a fact they have validated it by their abandonment in the 7th Edition and PMI’s move towards Agile, which we know for a fact DOES WORK but not in all circumstances.
These are the FACTS:
1) “agile” is nothing more than the same “trial and error” method used by Neanderthals to tame fire or 6000 years ago was used to invent the wheel and around the 12th Century, became known as the “Scientific Method” which in the ensuing 1000 years or so has brought us hundreds of thousands of new products and services, https://is.gd/RygM7f
2) “Agile” or more appropriately, the “trial and error” or “Scientific Method” is just one of a whole spectrum of ASSET DELIVERY OPTIONS that any organization can choose from to “create, acquire, expand, update, maintain, repair and eventually dispose of ORGANIZATIONAL ASSETS. https://is.gd/JGBBZe
If you are honest and candid in communicating these facts, then I think or at least hope it will go a long way to clarifying many of the common misperceptions and confusion.
BR,
Dr. PDG, Jakarta
Thanks, Paul. Agile is not a PMI concept, so I’m not sure I’m clear on the comment about following PMI too closely. There are many ideas that go under multiple names and many people are familiar with Agile as a framework/method. As I shared on our LinkedIn discussion, you must meet your stakeholders where they are and use a language they understand. To clarify, “agile” is not a method, but an adjective. “Agile” is a method or framework that is similar to the scientific and trial and error methods with some specifics added to relate it to software/technology projects to make it easy to understand and adopt. As always, thanks for your input!