Excellent Project Management Blogs
Are Program Managers on the Career Path to the C-Level?
PMP Prep Tools
Here are some awesome resources I found; if you are plaanning to take the exam or simply learn more:
Good luck.
Project Management Science Corner – The Dunning-Kruger Effect
A colleague and friend (thanks Leon) has introduced me to the Dunning-Kruger Effect.
The Dunning-kruger Effect (which is a scientific elaboration on a famous quote by Charles Darwin that “Ignorance more frequently begets confidence than does knowledge”) simply states that ignorance results fairly frequently with over confidence and self certainty, even in the face of evidence and body of knowledge suggesting otherwise.
The first thing that came to my mind when investigating this phenomena were some previous discussions I’ve been party to with regard to the issue of projects’ failure rate and the various studies / publications attempting to persuade us that a large portion of IT projects end up in utter failure.
Are we witnessing a live example of the Dunning Kruger Effect, where people without the proper scientific or methodological experience make use of unsubstantiated data to prove a point they’ve already had in their mind but were simply looking for a ‘study’ to confirm the point they’ve already formed?
Think about it!
Inspirational Quote about Feelings via Jonathan Mårtensson
choose which one to surf.
- Jonatan Mårtensson
See also:
- Inspirational Quote about Motivation via Jamie Oliver At some point you have to stop worrying about what...
- Inspirational Quote about Worrying [via John Power] Worrying is the same thing as banging your head against...
- Inspirational Quote about Communication You either tell your story or someone is going to...
- Inspirational Quote about Uncertainty [via H.L. Mencken] It’s the dull man who is always sure and the...
- Inspirational Quote about Your Energy Level [via Rev Run] The world belongs to the energetic! - Rev Run...
The Complete Failure of Our Public Education System ?!?
Sorry, couldn't resist.
The Project Rationale for Sustainability
As we’ve mentioned before, several excellent books really brought EarthPM from an idea we’ve long shared to a real book and a small but growing consulting company.
But we have never stopped reading. And we won’t.
One of the most recent books we’re finding invaluable is The Necessary Revolution, by Fifth Discipline author Peter Senge.
You’ll probably see a few postings here with their roots in this book, because it is that rich with good ideas.
One we wanted to share with you immediately is the concept of “The Business Rationale for Sustainability”, which actually comprises a full chapter of the book. As usual, we see portfolios, programs, and projects as microcosms of business.
So, with that, we’ve interpreted (interpolated?) the models that Senge uses for those of us who are at the “business end” of business – project managers.
We start with Senge’s assertion that for many years – in fact, during most of the entire Industrial Age, business leaders saw the economy in the following way:
Industrial Age view of the economy, society, and the environment
But instead, consider this view (below) which considers that business is a “wholly-owned subsidiary of nature”. And our addition – that portfolios, programs, and projects are at the core of the enterprise’s business.
A better view - including project management as the "business end" of business
-
Without giving you the whole chapter, we want to show you how closely connected the concept is to the assertions that we make as EarthPM. Those assertions are here.
- There is significant money to be saved
- There is significant money to be made
- You can provide your customers with a competitive edge
- Sustainability is a point of differentiation
- You an shape the future of your industry
- You can become a preferred supplier
- You can change your image and brand
Compare those with Senge’s rationale for sustainable business:
You will see more from this book.
For now, think about the way this may help you express sustainability to your stakeholders.
Steps to Performing a Project Quality Audit - Intro and planning
Identifying Resistance to Change
Why Agile Might Not Work (Video)
I was minding my own business when I noticed a tweet by Alistair Cockburn. He clearly thought something was funny so I figured I’d check it out. What awaited me was this video. If you understand Agile or just interested about it, you should spend the next 3 minutes and 14 seconds enjoying a creative perspective on why Agile might not work for you. It’s very tongue-and-cheek. You should also check this out: http://www.pmi.org/resources/pages/agile.aspx Again, don’t take it too serious.
Leadership Tip: Too Many Drivers Will Not Take Your Car Anywhere.
We have all seen these emails. Emails from your Vice President where he wants a certain Fred to look at your project and provide “inputs”.
You know the famous architecture team story by Joel Spolsky.
That kind of inputs.
Before you know it, "consultants" with terrible blind spots who are awesome at playing the jargon game and who have zero knowhow about the domain, zero understanding of your team dynamics and zero expertise in the technical space are meddling in every decision your team is taking.
Well not exactly those consultants, but if you have been through an architecture review meeting with external consultants you know exactly what I am talking about here.
Every small change is questioned and discussed in meetings that no productive programmer would want to attend in the first place but then you suddenly find yourself in these meetings spending hours defending the most common sense driven decisions you took.
You know your car is going round and round in circles. You are not getting anywhere. The fact that you are going around in circles is common sense. You have too many drivers fighting to take control of the driving wheel.
Obviously, you are not moving ahead. Obviously, throwing in more drivers is not going to solve the problem. Obviously, you need to pick a single driver to drive your project. Obviously, you need to check his track record closely before you pick him. Obviously, you need to learn how to trust him. But then again, obviously, obvious is not so obvious, especially when it comes to big organizations that are trying to pretend to be even bigger than they really are.
If you run a team or an organization, remember that every time you get more than one driver at the wheel you run the risk of getting nowhere. So the next time you invite those external consultants to review a project that is moving just fine or fu@#k up a department that is moving along smoothly, think twice.
Here is my humble word of advice from the forefronts of software development: Pick a single capable trust worthy driver. It doesn’t matter who you pick, as long as the person is competent and trust worthy.
Then move to the back seat and let the person you picked drive without bothering him.
You may not get to your exact destination. You might get just a little closer to it. But then at least it is better than moving round and round in circles.
I wish you good luck.

Recent comments
6 hours 31 min ago
7 hours 8 min ago
1 day 5 hours ago
1 day 6 hours ago
1 day 23 hours ago
2 days 6 hours ago
2 days 6 hours ago
2 days 21 hours ago
3 days 6 hours ago
3 days 6 hours ago