Project assurance methodologies, such as Collaborative Intervention?, are based on the following principles or best practices:
1. Identify the real issues. At the leadership level, you need to develop an executive dialog that allows business and organizational issues to be identified and analyzed with clarity and without emotion. Continue this dialog throughout the implementation process. Remove organizational barriers both within the organization and with third party vendors. All parties should be aligned with the common goal of project success.
2. Set realistic timeframes. Don't rely on the existing schedule. Many organizations will set overly optimistic go-live dates in spite of the realities and limitations of the actual project. For example, the design phase extends, but the time line doesn't. You must monitor project progress throughout the implementation and start discussions regarding key project dates early in the project's lifecycle to avoid downstream impacts.
3. Align the work streams. You need to identify, align and continuously monitor work streams to ensure smooth progress throughout the organization. Understand dependencies between work streams during project plan development to ensure proper resource allocations and project time frames. Continue to monitor the interdependencies throughout the project.
4. Look beyond the indicators. Contrary to popular opinion, green may actually be red. Realistic monitoring and analysis of progress of the implementation can show that even though all project management indicators are green, warning signs indicate endangered components. If indicators are only addressing past phases, but not addressing readiness for upcoming project tasks and activities, they are definitely trailing indicators and not trustworthy predictions of the future.
5. Manage the expectations. Critical to maintaining control of the project, you need to manage the confluence of overly optimistic go-live dates against outside influences and interdependencies, such as available resources and realistic expectations. Set realistic expectations upfront and keep expectations current in the mind of project team members so that they don't lose sight of the forest while maneuvering around a tree.
6. Seek objectivity. Assessments conducted by an outside expert add both value to the project implementation and protection against the high cost of failure. Expertise delivers the know-how and the objective oversight needed to overcome organizational roadblocks. It also provides you with peace of mind. Assessments should be conducted by an executive project manager or software implementation expert who has managed enough projects successfully to know how to recognize subtle indicators, intervene to accommodate the situation, and adjust expectations accordingly.
At the end of the day, having a project assurance methodology gives you the power to go beyond traditional project management barriers and gives you the answers you need to assure supply chain software project success. It helps you to identify and resolve the strategic, tactical and intangible issues — and manage the human factors — before issues become insurmountable. And best of all, project assurance gives you (and everyone else involved) peace of mind that the project is on the right track.
About the Author: Rob Prinzo is the founder and CEO of The Prinzo Group, which provides project assurance expertise for enterprise transformation and technology projects. He is the author of No Wishing Required: The Business Case for Project Assurance. More information on The Prinzo Group at www.prinzogroup.com.
More Articles of Interest
- Innovation Leadership — How to Reignite Innovation in Your Organization
- The EQ Factor — Navigating through the emotions around Lean changes, by Nestle USA Supply Chain Leader Scott Barrella, MS CPIM