1 / 13

Bite sized training sessions: Drivers

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:.

paul2
Télécharger la présentation

Bite sized training sessions: Drivers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Bite sized training sessions:Drivers

  2. 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

  3. Chain Of Reasoning: Change Requirements must be assumed to be wrong until they are provedto be right Stakeholders

  4. The big questions…who are the project killer stakeholders? • There are 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.

  5. project killer stakeholders? Compliance stakeholders e.g. Policy, legal, H&S, Audit, external regulators Rules, requirements, constraints Compliance results Customers of The solution stakeholders (internal and/or external depending on project) Owner/Manager Stakeholders e.g. Organisation Owner, Process owner, Product or Service owner Project Performance criteria Requirements KPI results, profits, etc Solution Resource requests Resource 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.

  6. The big questions…who are the other stakeholders? There are 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. Slide: 6

  7. Remember RACI? Remember RACI quality checks?

  8. 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

  9. 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…

  10. 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?

  11. 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.

  12. Questions?

More Related