To avoid a dire fate, don’t forget to iterate!
From the Easy in theory, difficult in practice Blog
by Kiron Bondale
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.
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
Anyone who has read the PMBOK Guide or taken the PMP exam knows that project management is made up of an interconnected and iterative set of processes. Even a highly predictable project requires a team to iterate back to earlier executed processes when faced with a change request.
So why is it that we tend to forget to re-execute certain key project management processes? It’s likely because they aren’t as well understood by our team, sponsor and other key stakeholders. It’s rare that maintaining schedule or financial baselines and forecasting these project dimensions is neglected as there are usually external forces ensuring that this occurs periodically.
But let’s think about risk and stakeholder identification and analysis. Just like developing a schedule or a budget, these processes are commonly performed early in the life of our projects. But it is very common to find projects where these processes are never revisited.
The risk of ignoring them is significant.
Skipping out on full lifecycle risk management means we could continue to invest in monitoring obsolete risks while remaining blissfully unaware of new threats or opportunities. We might also be missing changes in the profile of existing risks. Some low risks on our watch-list might have increased in severity whereas others which we are actively responding to could have dropped in priority. As risk responses are implemented we want to understand what residual risk remains and update our knowledge of these risks accordingly.
The same holds true for stakeholder information and engagement activities. We might miss a new highly influential or impactful stakeholder that arrives on the scene after our initial stakeholder analysis. Or a stakeholder whom we felt had little interest in our project might become more visible than before.
We expect that overall risk and the relative influence of stakeholders should decrease over the life of a project as we start delivering scope and uncertainty decreases but if we keep looking in our rear view mirrors we are likely to miss the runaway Mack truck bearing down on us.
Avoiding this requires discipline on the part of the project manager. Consciously challenging themselves and the team to periodically revisit risk and stakeholder registers for currency and accuracy can reduce the likelihood of occurrence.
To extend Donald Rumsfeld’s famous taxonomy, we create unknown-knowns by not iterating back through all applicable project management processes.
(Note: this article was originally written and published by me in September 2017 on my personal blog, kbondale.wordpress.com)
Posted on: February 28, 2018 07:51 AM |
Permalink
Comments (9)
Please login or join to subscribe to this item
Rami Kaibni
Community Champion
Senior Projects Manager | Field & Marten Associates
New Westminster, British Columbia, Canada
I fully agree with you: Reassessment, Revisiting, Auditing those all are importamt for a successful project management of a project.
It would be good to have or develop some universal metrics for measuring the iterations of certain key processes, in particular 1. was it ever revisited, 2. how often was it revisited, 3. what what the impact of not revisiting or not revisiting enough? It should also be tied to risk and assumptions.
There seems to be a low voter loose today. In this and another posts that deserve a high rating, instead they got a 1 or 2 it seems. Like I said in the other post, I imagine the reader has no imagination. Yes rating is very personal, so I'm personally rating this post a 6, and the reader who posted a 1 or 2, well I give them a 0 :-)
Anish Abraham
Privacy Program Manager| University of Washington
Auburn, Wa, United States
I agree with you, Kiron. and thanks for sharing your insights.
Revisiting is very important for the success of the project.
RAJESH K L
Project Manager, PMP| Bharat Electronics, Bengaluru, India
Bengaluru, Karnataka, India
Good one and interesting. Thanks for sharing
Refreshing to have read this post Kiron and the community thoughts also!
Sante - love the ‘voter on the loose’ comment, is it not one of them Abot, Bbot or Cbot gang?
Hi Suzi, no bots in this case, just some people that just go around voting posts a 1 when others rate it a 4 or 5, which drags down the "average rating". It's a free world I suppose :-)
Please Login/Register to leave a comment.
|
"Always do right. This will gratify some people and astonish the rest."
- Mark Twain
|