Bite sized training sessions Drivers Objectives To understand

Bite sized training sessions: Drivers

Objectives • To understand – What drivers are – Where they come from – Where they fit in to analysis of requirements – The importance of drivers • To be able to – Find drivers – Document drivers

Chain Of Reasoning: Drivers Stakeholders Drivers Objectives Objectives Change Requirements Stakeholders Change Requirements Change Requirements must be assumed to be wrong until they are proved to be right

The big questions… who are the project killer stakeholders? • There a set of people and organisation units that can kill your project • They may be obvious and they may not • They may not all be killer stakeholders for the same reasons.

project killer stakeholders? Compliance stakeholders e. g. Policy, legal, H&S, Audit, external regulators Rules, requirements, constraints Owner/Manager Stakeholders e. g. Organisation Owner, Process owner, Product or Service owner Performance criteria KPI results, profits, etc Compliance results Requirements Project Resource requests Solution Resource Supplier Stakeholders e. g. people who can allocate buildings, systems, equipment, consumables, spares, sub-contractors NB: ~ 1 person/group can play the role of many stakeholders. ~ Expect all stakeholder interactions to come in pairs: typically a request and response. Customers of The solution stakeholders (internal and/or external depending on project)

The big questions… who are the other stakeholders? • There a set of people and organisation units that are impacted in some way your project • They may be obvious and they may not • They will not all be stakeholders for the same reasons.

Remember RACI? Remember RACI quality checks? Too many R’s Why is this role so responsible. Can they cope. Can they delegate. Are there bottlenecks around this one role. What happens when people are on holiday or absent unexpectedly etc. Every box filled in Why is the person involved in so many activities. Are there bottlenecks around this one role. Can R’s be reduced to C’s, and can C’s be reduced to I’s No R’s or A’s Should this role be eliminated in the process. Could the resources be redeployed. Too many A’s Is there a proper segregation of duties. Should other groups in other areas be accountable for some of the A’s. Are there bottlenecks around this one role

Exercise: Define the project stakeholders • Identify and analyse the reasons for involvement of the stakeholders – especially the killers! • Use the handouts • The business is available to answer questions. • If you need to make assumptions, document them. • Time allowed: 15 minutes • Deliverable: flipchart of stakeholders and reasons for involvement

Drivers • There are reasons why a project exists – something has ‘driven’ the need for it • Drivers have driven the project killer stakeholders to sponsor the project • These drivers tend to be – Problems the stakeholders want fixed AND/OR – Opportunities the stakeholders want to exploit AND/OR – Standards/regulation/legislation the stakeholders want to comply with • Drivers need to be analysed…

The big questions… why does your project exist? • What do the killer stakeholders want from the project? • What would need to be in place for this to happen? • Why isn’t this happening now? • So what are the problems or opportunities that the desires address?

Exercise: Define project killer stakeholders drivers • From the case study try and build a sentence for each driver: – “given the desire to [do something] it follows that [some things are in place] but the reason this isn’t happening now are [problems] and this has resulted in [issues for the organisation]” • • The business are available to answer questions. If you need to make any assumptions, document them. Time allowed: 15 minutes Deliverable: flipchart of drivers and assumptions.

Questions?