By Lauren Clark on May 08, 2012
Welcome to the fifth (and final) blog entry of the series on PMI’s 2012 Pulse of the Profession . The previous blog entry focused on Key Finding #4: Organizations will renew their focus on talent development as they look to grow and gain competitive advantage in new markets. That entry highlighted how the OUM Training Program prepares project team members in various roles to be effective on an OUM project.
In this blog entry we will look at PMI’s Key Finding #5: Despite tight economic conditions, organizations have been and will continue to increase their focus on benefits realization success metrics. PMI’s research shows project/program managers must maintain a focus on the strategic objectives of the project. Anyone who has been on a project knows it is not easy to keep the big picture in mind when we are caught up in our day-to-day tasks. So in this blog entry we will take a look at some of the key elements in OUM that help keep projects aligned with the organization’s strategic goals.
Whenever we talk strategy in OUM we turn our attention to the Envision Focus Area. The development and maintenance of enterprise level IT strategy, architecture, and governance done in Envision helps to ensure IT delivery is in alignment with the organization’s strategy. Ideally, every enterprise should be executing the processes in Envision or similar processes.
I am going to get on my soapbox at this point and say, because the processes in Envision provide the glue between the business and IT strategies, true benefits realization will be very difficult (or nearly impossible)to achieve without an Envision or similar engagement. We discussed in the first blog entry of this series how Envision helps ensure projects will align with an organization’s objectives by providing the processes to support effective portfolio management. We know that organizations who focus only at the project level will wind up with a collection of stovepipe projects that have limited ability to address the organization’s strategic needs or provide return on investment. We also know that project teams starting out without an enterprise IT strategy and architecture, or the appropriate IT governance in place will often find it necessary to gather enough information to establish the project’s objectives, scope, and estimates for the solution. This can cause significant project delays and possibly lead to costly re-work.
In order to understand the connection between the artifacts produced in the Envision Focus Area and how they relate directly to the tasks in the Implement Focus Area, project teams should be aware of the Envision Touch Points found in the OUM Method Overview page. These touch points are potential prerequisites from Envision work products to Implement tasks. As we know, an Envision engagement does not always precede an Implement engagement and, therefore, these touch points are not always available to the project as artifacts. The project team must then determine the degree to which the Envision tasks should be executed to generate the necessary information to proceed.
The project manager should also look to the Envision artifacts when establishing the project structure to make sure the project is set up to achieve the expected benefits of the project. During the Project Start Up phase of the OUM Manage Focus Area, resources are allocated to achieve specific objectives, satisfy needs, and set expectations through a planned and organized approach. The project manager should start with the enterprise IT strategy and governance when formulating this approach, and then document the approach as part of the Project Management Framework (the precursor to the Project Management Plan).
As you can tell, I am a big fan of Envision. I put a great deal of value in this focus area of OUM because I have seen so many projects that benefited by having a view of the big picture. But, if you disagree with my assessment of how important enterprise-level work is to benefits realization, please let me know in the comments section. For some really good advice on the role of an Oracle Enterprise Architect and how they can benefit a project, check out a blog entry written by my colleague called “When to Call an Oracle Enterprise Architect”.
This wraps up the series on PMI’s 2012 Pulse of the Profession. I hope you enjoyed reading these entries as much as I did writing them. It’s been a great opportunity to demonstrate how OUM is in-tune with leading industry trends. The series has generated quite a bit of inspiration for future blog entries. So please keep watching this blog, as well as our LinkedIn Group and Twitter for OUM information, tips, and techniques. If you have a suggestion for a future blog entry or have a question, you can reach us at firstname.lastname@example.org.