Listen to The PM Podcast

This episode is reserved for subscribers of the Premium Podcast. Learn how to subscribe to the Premium Podcast to access this interview and transcript...

This episode is sponsored by The PDU Podcast:

I am once again joined by Todd Williams, author of the book Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure. 

In our last interview Todd gave us an overview over the process, tools & techniques he recommends for rescuing problem projects. As our next step, we want to hear from Todd how he ensures that projects don’t get into trouble in the first place.

Play Now:

This episode is sponsored by The PDU Podcast:

When project budgets are dwindling, deadlines passing, and tempers flaring, then the usual response is to browbeat the project team and point fingers of blame - usually toward the project manager. That’s not really all that helpful. For these situations, what is needed is an objective process for accurately assessing what is wrong and a clear plan of action for fixing the problem.

Enter Todd Williams, PMP who wrote the book Rescue the Problem Project: A Complete Guide to Identifying, Preventing, and Recovering from Project Failure. Todd and I sat down at the PMI® Global Congress last year and in this interview we discuss approaches to project rescue.

Here’s a brief book overview of Todd’s book: Rescue the Problem Project provides project managers, executives, and customers with the answers they require. Turnaround specialist Todd Williams has worked with dozens of companies in multiple industries resuscitating failing projects. In this new book, he reveals an in-depth, start-to-finish process.

As always when we have an author discussing his book we are giving away two copies and by now you should know how that works. One copy is reserved for our premium listeners and one for everyone else. If you want a chance of winning the book, please go to www.facebook.com/pmpodcast and look for the book giveaway announcement. All you have to do is leave a comment.

Play Now:

This episode is sponsored by The PDU Podcast:

If you are a PMP® credential holder then you know what the acronym PDU stands for. It stands for Professional Development Units. Every PMP needs to earn 60 of these PDUs every 3 years in order keep his or her certification. The idea behind having to earn these PDUs is a simple one. PMI wants every PMP to continuously learn. Just like doctors or pilots who have to take classes regularly and practice new skills in order to keep their license, PMI wants us PMP® credential holders to learn new project management skills so that we can be the best project managers possible.

The rules describing which activities count towards PDUs and how you have to report and claim them is documented in the “PDU Category Structure and Policies” document. In March 2011 PMI released a new version of these rules that is a lot less complex than the old one. So this has been out for about 10 months now, however, I still receive a lot of emails from confused PMP® credential holders who have questions about it. So I went ahead and sat down with Rory McCorkle from PMI to discuss the new structure and get clear descriptions and explanations directly from the horses mouth.

Here are some topics that Rory will discuss in the interview

• Why were the PDU policies changed?
• We’ll define the rule that “One hour of effort is equal to one PDU”
• We’ll discuss the PDU Divisions and Categories
• We give examples of PDU earning activities
• And lot’s more.

Listen Now:

Seriously... there are no bloopers this year. So don't bother looking for any.

Move along now... no bloopers to see here. Or hear here.

Now really... why are you still here? Go to another episode now.

But if you don't believe me and insist on still pressing the play button above, then please do enjoy yourself. We try hard to record our episodes as flawlessly as we can, but unfortunately we just keep stumbling over our tongues (or draw a complete blank when trying to ask Peter Taylor a question). Have fun.

But as I said... there are NO bloopers here. ;-)