Project Management

Please login or join to subscribe to this thread

Help Needed: Streamlining Risk Management and Project Closure

linkedin twitter facebook  
avatar
PANAGIOTA BOURCHA IT Project Manager| Alpha Supporting Services Athens, Greece

Hi PMI Community!



I am a junior IT Project Manager and this is my first post here. I am currently facing an issue related to my company's processes. I am preparing a proposal to change these processes, specifically focusing on risk management, and I need your expertise to ensure my proposal is well-founded.



The current processes state that if security findings are discovered during a penetration test, they must be resolved and the risk reduced to at least medium before risk acceptance can be granted and approval given for promotion to production. However, even after the project goes into production, it remains open, and corrective actions continue until all security findings are fully resolved within a reasonable timeframe. Only once complete resolution is confirmed can the project be closed.



This approach creates significant problems when resolution is not straightforward and requires development work. My proposal suggests that once risk acceptance has been granted and the project has been delivered to production with the identified assumptions, the initial project should be closed. If the implementation and resolution horizon is one year or longer, a new project should potentially be opened to address the findings.



I would appreciate your feedback on this approach and any insights or experiences you can share.



Thank you!

avatar
Kiron Bondale Retired | Mentor| Retired Welland, Ontario, Canada
Panagiota -

It is often the case that there are project issues which remain unresolved after all the deliverables have been completed. In such a case, decision makers are faced with the question of whether to close the project and transfer those issues to operational owners or to keep the project open till those are resolved.

In this case, it really comes down to the policies related to IT security within the company. If those mandate that all identified vulnerabilities are sufficiently mitigated prior to project closure then you would need to engage the owners of that policy to see if they are willing to go with your approach.

While such a change would certainly be cleaner from a project management perspective, I have seen cases in my past where once issues had been transitioned out of a project, they were no longer viewed as a priority, and in the case of an IT security vulnerability, this could become a major concern down the road.

Kiron

Please login or join to reply

Content ID:
ADVERTISEMENTS

Vote early and vote often.

- Al Capone

ADVERTISEMENT

Sponsors