{"id":59,"date":"2014-03-05T06:30:17","date_gmt":"2014-03-05T06:30:17","guid":{"rendered":"https:\/\/sofintsys.com\/blog\/?p=59"},"modified":"2016-09-26T19:40:49","modified_gmt":"2016-09-26T19:40:49","slug":"programme-management-risk-management","status":"publish","type":"post","link":"https:\/\/sofintsys.com\/blog\/programme-management-risk-management\/","title":{"rendered":"Programme Management – Risk Management"},"content":{"rendered":"

Risk Management is routinely asked for on big projects and it inevitably ends up as a big process of hierarchies of spreadsheets or a database that identifies the risk, the potential impact and ways to mitigate it. I have seen many systems, and also seen many project and programme managers pay lip-service to them, by filling in either the bare minimum, or populating it with racing certainties! E.g. \u2018Lack of resources\u2019; This is not a risk, it is a management decision.<\/p>\n

Yet, as far as software programme management<\/b> is concerned, for any new development featuring any form of novelty (product, technology, architecture, people, organisation), risk management<\/b> should be one of the key tools<\/b> for planning the programme.<\/p>\n

Significant risks<\/b> are, actually, usually pretty obvious<\/b>… and a browse through the system requirements by someone with even little appreciation of the project, and little experience, will quickly identify the major issues that are likely to have big impacts. Once the big issues are addressed, there will be a much greater number<\/b> of lesser issues<\/b> which may take more expertise to assess with regards investment of \u2018mitigation\u2019. Iterating this process quickly drops you into the usual \u2018noise\u2019 of typical project variation.<\/p>\n

Where the risk responsibility<\/b> lies is often a key factor, in getting authority<\/b> to address it. It is rare that big impact risks exist within a single discipline (and if it does the technical discipline manager is usually loathe to admit he doesn\u2019t know the solution). These factors make declaring risk unattractive<\/b> to some practitioners and may put the project and business at risk.<\/p>\n

Investing in \u2018experiments\u2019<\/b> is really what risk management is about. When you don\u2019t understand the science<\/b> well enough to have some suitable engineering solution<\/b> that has provenance, you create a task, switch from engineer to scientist (but with a focus on a particular problem), and look for possible solutions, or to gain some understanding, that allows you to mitigate, avoid, control or at least \u2018size\u2019 the problem and the effort required in solving the same.<\/p>\n

But there is absolutely no point in defining and executing experimental tasks, if the learning is then not applied, in a timely fashion, to your real project. Classical failures<\/b> in risk management are:<\/p>\n

i)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Doing the experiment too late<\/b>, or on the project<\/b> when eventually encountered<\/p>\n

ii)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Not using the information<\/b> gleaned from the experiment to modify<\/b> the programme, or product<\/p>\n

iii)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Failing to understand<\/b> the underlying science<\/b> that creates the risk, such that mitigation actions can be assessed<\/p>\n

iv)\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Adding<\/b> extra complexity, further<\/b> technology risk<\/b> or unproven processes in the solution<\/p>\n

Often risk reduction programmes require trades between different parts of the system and need multi-discipline skills. Often these will be executed with third parties who have a better understanding of the underlying science, or an ability to think more openly (e.g. academic researchers and institutions).<\/p>\n

Technology development programmes are inherently risk management\/risk reduction exercises and show a maturity of the business in tackling the problem ahead of bidding a programme that deploys the technology in question.<\/p>\n

Embedded software in control and information systems say, is practiced by a wide community of businesses but is largely protected as intellectual property within those businesses (and often inside individual business units). It is fair to say, that most problems in software will probably have already been encountered, and in most cases a solution exists, but others will be unaware.<\/p>\n

Even if solutions don\u2019t exist there is potential for finding partners who face that common problem to share the burden of finding a solution. These issues will be the subject of a further instalment, but the general principles of Industrial Collaboration<\/b> can be found here<\/a>.<\/p>\n

___________________________________________________________________________<\/p>\n

Let us help you maximise the business potential\u00a0of your product and its software<\/h5>\n

Email me on\u00a0stuart.jobbins@sofintsys.com<\/a><\/p>\n

Visit our\u00a0website<\/a>,\u00a0or follow us on your preferred Social Media for our latest views. \u00a0 \u00a0\"linkedin\"<\/a>\u00a0\"twitter<\/a>___________________________________________________________________________<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Risk Management is routinely asked for on big projects and it inevitably ends up as a big process of hierarchies of spreadsheets or a database that identifies the risk, the potential impact and ways to mitigate it. I have seen many systems, and also seen many project and programme managers pay lip-service to them, by … Continue reading Programme Management – Risk Management<\/span> →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[13,8],"tags":[],"class_list":["post-59","post","type-post","status-publish","format-standard","hentry","category-planning","category-programme-management"],"_links":{"self":[{"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/posts\/59","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/comments?post=59"}],"version-history":[{"count":3,"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/posts\/59\/revisions"}],"predecessor-version":[{"id":146,"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/posts\/59\/revisions\/146"}],"wp:attachment":[{"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/media?parent=59"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/categories?post=59"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sofintsys.com\/blog\/wp-json\/wp\/v2\/tags?post=59"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}