Involving Governance Stakeholders (Part 1)

Joe Wynne is a versatile Project Manager experienced in delivering medium-scope projects in large organizations that improve workforce performance and business processes. He has a proven track record of delivering effective, technology-savvy solutions in a variety of industries and a unique combination of strengths in both process management and workforce management.

  Communications Management   Governance   Requirements Management   Risk Management  

It was the best of times--your project seemed to be going along swimmingly. It was the worst of times--suddenly there was a surprise from a governance stakeholder. Take time out now to avoid getting yourself sent to the guillotine. Learn from other project manager’s mistakes so you get to see where exactly a problem occurred and then trace it back to the source(s) in context. This is especially useful to improve your ability to incorporate stakeholders from legal, compliance and risk management.

Here is the first example showing how you can manage in this Age of Governance. It covers a problem experienced very late in the project, and one found earlier in the project will follow. For the purposes of this article, a governance stakeholder is any potential project representative such as from legal, regulatory compliance, operational risk (or other risk management group) and even quality management. In today’s hyper-sensitive regulatory environment and ever-observant news cycle, these representatives feel that they are a line of defense against lawsuits, fines, fraud, budget overruns, stained corporate reputation and more.

Situation 1: Surprise Stop
Abigail’s last project, implementing a new customer-facing web application resulting in a significantly improved business process, was stopped by surprise shortly before go-live due to a compliance issue.…

Please log in or sign up below to read the rest of the article.