Of course, it was nice to Crossderry included. It was even better that my “short post” style was appreciated. Lots of sweat goes into getting these posts under 250 words!
I’ve been working on an initiative called “Value Delivery,” which will incorporate value management into our various PMO methods, tools, etc. These activities are often listed as typical PMO functions, but this really only honored in the breach. Value management never seems to take off given a PMO’s traditional emphasis on implementing project management methods, tools, training, etc.
In our approach, we will ensure that value management has its own identity, especially when it comes to training. While value and benefit management is baked into the various program and portfolio standards around, it isn’t part of the typical project manager’s skill set. Rolling out value management separately should emphasize the organizational and personal changes required to be successful.
What is value management’s objective? To ensure that execution remains focused on delivering against executives’s and stakeholder expectations. How does value management happen? Maybe the best way to illustrate is to briefly lay out the lifecycle we’re using below:
- Value Discovery: Establish a performance baseline
- Value Realization: Identify required process improvements and KPIs
- Value Optimization: Review and steer benefit attainment
Glen Alleman and a number of commenters contributed to a great thread on math, PM, and complexity (here).
I try to keep the ideas of complexity “science” in mind when planning strategy and its execution. In particular, I have a deep respect for the power of self-organization and the need to create flexible rather than brittle management systems.
However, I’m not sure how powerful CAS really is as a theory, at least w/r/t/ project management. For example, how do its predictions advance my estimation approach beyond what we’re doing w/ probability distributions (e.g., Monte Carlo simulations via Crystal Ball)? To I really need math beyond that to get “good enough” estimates?
Filed under: Complexity, Portfolio Management, Program Management, Project Management, Strategy Management | Tagged: complex adaptive systems, complexity theory, Glen Alleman, Herding Cats | 3 Comments »
Greg Balestrero — CEO of the Project Management Institute — recently posted (here) on his experiences at the Scrum Gathering in Orlando. In my experience, Greg and the PMI staff have been very eager to foster a better relationship among the various methodology camps. Per Greg’s post,
[t]he intent of the visit was to bridge the gap between the Scrum Alliance and PMI. But I guess the real reason we attended was to dispel the myths that surround the PMBOK® Guide and Agile practice. There is a widely held opinion that the PMBOK® Guide and Agile don’t mix… they can’t be “shaken, nor stirred” together.
Please read the post…it gives an interesting perspective on how to build alliances among disparate points of view and how to overcome misconceptions.
Regular readers know that I’ve been harping on the increasing importance of program management, especially when it comes to realizing the benefits or value of projects. Project managers who simply run projects without reference to the larger business environment are becoming a commodity.
During the recent Global Corporate Council forum, I heard two thoughts that illustrated the challenge for PMs:
- Greg Balestrero, the CEO of the Project Management Institute (Greg’s blog is here), calls project management “table stakes”. In other words, PM has become so widespread that it is no longer differentiating for an organization or person to be good at PM. In Greg’s opinion, PM-only lets/keeps you in the game…no more.
- One council member quanitified the value of the PMP in terms of experience. He had to counsel a project manager who was very itchy to advance but was perplexed that his PMP hadn’t taken him further. The council member put it to him bluntly: “A PMP is worth about two years of experience in our organization, which is something… But it isn’t equivalent to leading and delivering a multi-year project or program.”
One of the reasons I’ve been remiss in my posting is that I’ve been preparing to host the Spring 2009 executive forum of PMI’s Global Corporate Council. My SAP colleagues did a great job helping me host and this forum was particularly productive.
“Networking” is a pat response when one talks about joining or leading industry groups. What exactly that means came home to me after discussions with my counterparts from Siemens, Joe Sopko and Kevin McDevitt. On two topics, just a few minutes of conversation helped me confirm the validity of one approach (on how to augment on program management content) and introduced a better metaphor (for the architecture of our new methodology).
Nothing big, eh? But how much benchmarking and justification will I avoid because I can say “well, Siemens had a similar problem and they did X“?
FYI, a Wall Street Journal article (“Dangers of Clinging to Solutions of the Past”) based in part on interviews w/ yours truly came out today (link here, page B4 in the paper). Thanks to Kishore Sengupta of INSEAD for pointing the WSJ my way and to Phred Dvorak of the WSJ for conveying the perils of experience so well and so succinctly.
As I’ve noted to a couple of colleagues, it is hard to believe that only 250 words of copy came out of two hours of interview time. Insert your own joke re: my verbosity here…
Filed under: Complexity, Knowledge Management, Organizational Change Management, People Development, Performance Management, PMO, Portfolio Management, Program Management, Project Management, Project Success Factors | Tagged: INSEAD, Kishore Sengupta, Paul Ritchie, Phred Dvorak, The Experience Trap, Wall Street Journal | 1 Comment »
As a follow up, over 250 people attended last week’s SAP PMO webcast (original post here) hosted by Keith Johnson, the VP for the SAP North America PMO VP and Jim Curry, Program Delivery Director. It’s always great to have a customer — in this case, Kelly Gear, Senior Program Manager, Johns Manville — confirm the value of some of what SAP offers and suggests.
How to establish the critical link between the steering committee’s goals and the project team’s activities.
The recording is available here – you will need to do a free registration if you don’t have a SAP.com login already.
Filed under: Methodology, PMO, Portfolio Management, Program Management, Project Management, SAP | Tagged: Jim Curry, Johns Manville, Keith Johnson, Kelly Gear, PMO services, SAP America, SAP Services, SAP webcast | Leave a comment »
Effective estimating requires a strong understanding of variance in estimating and how to account for/govern this variance.
Ditto and amen… my experience in implementing logistics optimization (I worked for formerly-independent component of Descartes) helped me get comfortable with the fuzziness of estimation (e.g., variance). Two b-school courses were also helpful: mathematical modeling for marketing and applied multivariate analysis (I keep the latter’s textbook by my desk). This background may not make me an expert, but I have a decent estimation BS detector.
Politically driven estimates are just irresponsible management. I remember a conversation with an executive where I told him “This is a 46 week effort. If you need to say 32 to get funding, then you can say 32 and deliver 14 weeks late – or we can say 46. It’s up to you.” We presented at 46 weeks, got the funding, and delivered on time. If an organization can’t afford to do a project, it shouldn’t be done based on false estimates – this is malfeasance.
As Dennis suggests in this case, pretending that the earlier delivery target does not compromise the product or mean inevitable delays is foolish, even unethical. My experience is that this self-sabotaging approach happens because the project can’t or won’t demonstrate the impact of such decisions on the initiative’s business case.
To that point about the business case, I’ll use a future post to lay out how we used a simple illustration of our business case to justify an internal program’s proposed release schedule.
One of the unexpected challenges in our PMO journey has been that success can make an enterprise-level PMO appear less relevant. A PMO must transform its approach to stakeholders or it won’t take full advantage of the improvements it fostered. One manifestation of the problem unfolds thusly:
- An enterprise PMO composed of PM thought leaders executes a PM improvement program that delivers methodology, training, tools, and change management initiatives to its stakeholders (e.g., regional, local, unit PMOs).
- Those stakeholders [largely] adopt those initiatives and transform their project operations in significant and measurable ways.
- This transformation creates a new set of PM thought leaders, who often surpass the knowledge and hands-on experience of the original enterprise PMO.
The business problem has reversed; the enterprise PMO now becomes the organization that needs to change to reflect the new reality. Deliverables that were relevant in moving from low maturity processes no longer work with a more sophisticated audience. This issue is compounded by the difficulty in recognizing the changed environment. Who wants to admit that he/she is no longer automatically at the vanguard of knowledge?
In other words, the challenge for a successful enterprise PMO is: “Who will change the change agents?”
Filed under: Methodology, Organizational Change Management, People Development, PMO, Portfolio Management, Program Management, Project Management | Tagged: business change, Enterprise PMO, personal change, process maturity | 3 Comments »