23 Business Case Development courses

What’s the real impact of EVs and infrastructure? This hands-on session uses gameplay to explore life cycle trade-offs and build shared understanding.

Gain insights into hydrogen technology, economics, and business cases with EnergyEdge's virtual instructor-led training course. Register now to secure your spot!

Better Business Cases™ Foundation Better Business Cases™ is based on the Five Case Model - which is the UK government's best practice approach to structuring spending proposals and making effective business decisions. Using this best practice approach will allow organizations to reduce unnecessary spending and improve the decision-making process which gives you a greater chance of securing necessary funding and support for initiatives. The goal of the foundation course is to enable participants to work effectively with a team to develop a strong business case in their work environment. What You Will Learn At the end of this program, you will be able to: Describe the philosophy and the underlying rationale of the Five Case Model Identify different types of business case, their purpose, who is responsible for them Recognize when the different types are required in the development of a spending proposal Develop the business case in relation to other recognized and recommended best practices for programme and project management Overview of the Five Case Model Five key components of a business case and the order in which they are presented Three key stages in the development of a spending proposal Definition of a programme / project and the key differences between programmes and projects Purpose of a Business Justification Case (BJC) and in what circumstances it should be considered Purpose of a Strategic Outline Case (SOC) Purpose of an Outline Business Case (OBC) Purpose of a Full Business Case (FBC) Relationship between policies, strategies, programmes, and projects and their deliverables Developing the Strategic Case Purpose and core content of a Strategic Case Purpose of SMART robust spending objectives and the key objectives for spend: economy, efficiency, effectiveness, re-procurement, and statutory or regulatory compliance Four main categories of benefits criteria and the parties involved in their development Three key categories of risk Purpose of identifying constraints and dependencies Difference between direct and indirect benefits Developing the Economic Case Purpose and core content of an Economic Case Purpose of critical success factors and the key critical success factors based upon the Five Case Model Purpose of the long list options and how to generate options and undertake SWOT analysis Minimum of four short-list options, how they are derived, and what they should include (Reference Project / Public Sector Comparator [PSC]) Difference between the preferred way forward and the preferred option Purpose, objectives, key participants, and outputs of Workshop Stage 2 - identifying and assessing the options Rules that should be followed for the treatment of costs and benefits Key differences between economic appraisals and financial appraisals Factors considered when selecting the preferred option Developing the Commercial Case Purpose and core content of a Commercial Case Guiding principles when apportioning risk between the contractual parties Purpose of payment mechanisms Purpose of Step 9 in the development framework: Contracting for the deal Developing the Financial Case Purpose and core content of a Financial Case The financial statements required for all projects The possible impacts to consider Developing the Management Case Purpose and core content of a Management Case Purpose of a programme / project management strategy, framework, and plan Purpose of a change management strategy, framework, and plan Purpose of a benefits realization strategy, framework, and register / plan Purpose of a risk management strategy, framework and register / plan Purpose of a post programme / project evaluation strategy, framework, and plan

Better Business Cases™ Foundation: In-House Training: In-House Training Better Business Cases™ is based on the Five Case Model - which is the UK government's best practice approach to structuring spending proposals and making effective business decisions. Using this best practice approach will allow organizations to reduce unnecessary spending and improve the decision-making process which gives you a greater chance of securing necessary funding and support for initiatives. The goal of the foundation course is to enable participants to work effectively with a team to develop a strong business case in their work environment. What You Will Learn At the end of this program, you will be able to: Describe the philosophy and the underlying rationale of the Five Case Model Identify different types of business case, their purpose, who is responsible for them Recognize when the different types are required in the development of a spending proposal Develop the business case in relation to other recognized and recommended best practices for programme and project management Overview of the Five Case Model Five key components of a business case and the order in which they are presented Three key stages in the development of a spending proposal Definition of a programme / project and the key differences between programmes and projects Purpose of a Business Justification Case (BJC) and in what circumstances it should be considered Purpose of a Strategic Outline Case (SOC) Purpose of an Outline Business Case (OBC) Purpose of a Full Business Case (FBC) Relationship between policies, strategies, programmes, and projects and their deliverables Developing the Strategic Case Purpose and core content of a Strategic Case Purpose of SMART robust spending objectives and the key objectives for spend: economy, efficiency, effectiveness, re-procurement, and statutory or regulatory compliance Four main categories of benefits criteria and the parties involved in their development Three key categories of risk Purpose of identifying constraints and dependencies Difference between direct and indirect benefits Developing the Economic Case Purpose and core content of an Economic Case Purpose of critical success factors and the key critical success factors based upon the Five Case Model Purpose of the long list options and how to generate options and undertake SWOT analysis Minimum of four short-list options, how they are derived, and what they should include (Reference Project / Public Sector Comparator [PSC]) Difference between the preferred way forward and the preferred option Purpose, objectives, key participants, and outputs of Workshop Stage 2 - identifying and assessing the options Rules that should be followed for the treatment of costs and benefits Key differences between economic appraisals and financial appraisals Factors considered when selecting the preferred option Developing the Commercial Case Purpose and core content of a Commercial Case Guiding principles when apportioning risk between the contractual parties Purpose of payment mechanisms Purpose of Step 9 in the development framework: Contracting for the deal Developing the Financial Case Purpose and core content of a Financial Case The financial statements required for all projects The possible impacts to consider Developing the Management Case Purpose and core content of a Management Case Purpose of a programme / project management strategy, framework, and plan Purpose of a change management strategy, framework, and plan Purpose of a benefits realization strategy, framework, and register / plan Purpose of a risk management strategy, framework and register / plan Purpose of a post programme / project evaluation strategy, framework, and plan

Use Cases for Business Analysis The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?

Use Cases for Business Analysis: In-House Training The use case is a method for documenting the interactions between the user of a system and the system itself. Use cases have been in the software development lexicon for over twenty years, ever since it was introduced by Ivar Jacobson in the late 1980s. They were originally intended as aids to software design in object-oriented approaches. However, the method is now used throughout the Solution Development Life Cycle from elicitation through to specifying test cases, and is even applied to software development that is not object oriented. This course identifies how business analysts can apply use cases to the processes of defining the problem domain through elicitation, analyzing the problem, defining the solution, and confirming the validity and usability of the solution. What you will Learn You'll learn how to: Apply the use case method to define the problem domain and discover the conditions that need improvement in a business process Employ use cases in the analysis of requirements and information to create a solution to the business problem Translate use cases into requirements Getting Started Introductions Course structure Course goals and objectives Foundation Concepts Overview of use case modeling What is a use case model? The 'how and why' of use cases When to perform use case modeling Where use cases fit into the solution life cycle Use cases in the problem domain Use cases in the solution domain Use case strengths and weaknesses Use case variations Use case driven development Use case lexicon Use cases Actors and roles Associations Goals Boundaries Use cases though the life cycle Use cases in the life cycle Managing requirements with use cases The life cycle is use case driven Elicitation with Use Cases Overview of the basic mechanics and vocabulary of use cases Apply methods of use case elicitation to define the problem domain, or 'as is' process Use case diagrams Why diagram? Partitioning the domain Use case diagramming guidelines How to employ use case diagrams in elicitation Guidelines for use case elicitation sessions Eliciting the problem domain Use case descriptions Use case generic description template Alternative templates Elements Pre and post conditions Main Success Scenario The conversation Alternate paths Exception paths Writing good use case descriptions Eliciting the detailed workflow with use case descriptions Additional information about use cases Analyzing Requirements with Use Cases Use case analysis on existing requirements Confirming and validating requirements with use cases Confirming and validating information with use cases Defining the actors and use cases in a set of requirements Creating the scenarios Essential (requirements) use case Use case level of detail Use Case Analysis Techniques Generalization and Specialization When to use generalization or specialization Generalization and specialization of actors Generalization and specialization of use cases Examples Associating generalizations Subtleties and guidelines Use Case Extensions The <> association The <> association Applying the extensions Incorporating extension points into use case descriptions Why use these extensions? Extensions or separate use cases Guidelines for extensions Applying use case extensions Patterns and anomalies o Redundant actors Linking hierarchies Granularity issues Non-user interface use cases Quality considerations Use case modeling errors to avoid Evaluating use case descriptions Use case quality checklist Relationship between Use Cases and Business Requirements Creating a Requirements Specification from Use Cases Flowing the conversation into requirements Mapping to functional specifications Adding non-functional requirements Relating use cases to other artifacts Wire diagrams and user interface specifications Tying use cases to test cases and scenarios Project plans and project schedules Relationship between Use Cases and Functional Specifications System use cases Reviewing business use cases Balancing use cases Use case realizations Expanding and explaining complexity Activity diagrams State Machine diagrams Sequence diagrams Activity Diagrams Applying what we know Extension points Use case chaining Identifying decision points Use Case Good Practices The documentation trail for use cases Use case re-use Use case checklist Summary What did we learn, and how can we implement this in our work environment?

Develop your Project Management skills and fully understand the entire project lifecycle and key activities that need to be done to deliver a successful project outcome. Course overview Duration: 2 days (13 hours) The ability to run a successful project professionally is a valuable transferrable life skill that can enhance your career and opportunities in any industry. Our Principles of Project Management course takes a pragmatic approach to managing a project successfully. It looks at the entire project lifecycle and key activities that must be done to give a successful project outcome. This course is suitable for anyone who is involved in or about to run a project – either as a full-time project leader/manager or as a part of their role. Objectives  By the end of the course you will be able to: Identify 10 key principles for managing a project successfully Apply a common sense project lifecycle to a project regardless of its size or magnitude Develop robust project documentation throughout the lifecycle whilst keeping the documents to a minimum Identify the expectations of key stakeholders and develop a clear communication plan to engage with them Apply a range of planning and scheduling techniques to help manage the project timeline Produce realistic estimates to help monitor and control the project costs Manage key risks and issues associated throughout the project lifecycle Manage changes through a robust change control process Manage the Project team through the use of clearly defined Work Packages Identify and manage key areas of conflict throughout the lifecycle Content Introduction Key characteristics of projects v Business as Usual Definition of Programmes and Portfolios Project Lifecycles – A structured approach using phases Reasons why projects fail 10 principles of successful project management The Concept (Feasibility) Phase Analysing the project context / environment Stakeholder needs and requirements Content of a Business Case Differences between Benefits, Success Criteria, Success Factors and Key Performance Indicators (KPI’s) Purpose of the Project Brief The Definition (Planning) Phase Defining the Scope of a project Assigning Project roles and responsibilities Product Breakdown structures and Work Breakdown Structures Approaches to estimating Detailed planning using Gantt charts Critical path analysis Using project management software – an overview Constructing a realistic project budgets Resource allocation and optimisation Producing a Communication Plan The Implementing (Execution) Phase Delegating using a Work Package Project tracking and reporting Managing contractors Controlling changes to the project Risk and Issues management Managing conflict between stakeholders The Handover / Closure Phase Measuring project success Capturing Lessons Post project review and evaluation Benefits Realisation Transferring the deliverable into Business as Usual

When managers have too many decisions to make, it can have a serious impact on the speed and efficiency of the organisation. When those decisions are commercial ones, the results can wreak havoc with the bottom line. Often the problem arises when those below them or in operational areas of the organisation aren't equipped or allowed to make a decision for themselves. Issues get passed back up and that wastes time. This programme provides a solution, giving your entire team the skills to: And most importantly, they'll be able to do this in line with the broader aims and commercial objectives of the business. By the end of the programme participants will be able to: Fully appreciate the importance of effective decision-making in business Use the five-step 'Stop, Think, Act!' decision-making process Stop leaping to conclusions Really understand the situations and decisions they are dealing with Identify good options Evaluate those options Make decisions and then put them into action Apply these tools and techniques to all their decisions in future 1 Understanding the business we work in What are the critical factors in our business? What is the SWOT analysis for our business? 2 Understanding what decision-making is 3 Background Culture of 'having to be doing' To change things we have to think about it! We are paid to make decisions! 4 Recognise the opportunity to make a decision 5 The 'Stop, Think, Act!' technique 6 STOP! Recognise the opportunity to make a decision Don't leap to conclusions Get ready to think Initial questions:Is this my decision? (Do I have the authority?)Who is this going to affect? (Do they need to be included?)When do I need to make the decision? (What's the timeline?) 7 THINK! The 3 Cs - making sure we understand the decisions we have to make What is the context of this decision?What is the overall situation?Why is this decision important?What do we need to achieve?What will success look like? Do I have clarity about the decision I need to make?Can I write it down?Can I express it clearly in two sentences? What are the criteria?What are the critical commercial factors that we will use to select our options?What will we use to measure the business success? 8 ACT! Identifying options What data do I need to collect?Issues with today's overloadIdentifying what will help you Select optionsHow many options?Must match your criteriaMust achieve success'Decision compass' exercise Analyse optionsTabular methodRisk analysis (likelihood v effect)Head, heart and gut (is there any organisational history/bias that we are up against?) Making your decision Taking it to actionFirst actionsPlanning how to make it happen

Software comes in a variety of guises - application software, firmware, middleware, system software. Increasingly, however, it doesn't necessarily present that way, especially as the boundaries between software, data and source code are becoming more and more blurred. And as software becomes more complex and more difficult to disentangle, so it becomes harder to manage and to value. But as it becomes more integral to every aspect of a business, so it is ever more important to keep on top of the technical, legal and commercial issues that arise, issues such as: To address these issues, organisations need a process for evaluating their current situation from all perspectives and for identifying the key actions they need to take to ensure holistic management of their software. This very practical programme will help set your organisation on the right path. Note: this is an indicative agenda, to be used as a starting point for a conversation between client and consultant, depending on the organisation's specific situation and requirements. This programme is designed to give you a deeper understanding of: The technical, legal and commercial risks associated with software development, procurement, use and commercial exploitation The most appropriate processes and responsibilities for managing those risks Note: this is an indicative agenda, to be used as a starting point for a conversation between client and consultant, depending on the organisation's specific situation and requirements. 1 Software business model What is the software business model? What options exist? Has the software business model been thoroughly reviewed to ensure its viability? This means fully understanding the market opportunity, the business environment and customer and end-user expectations. 2 Technology What are the technologies? How has the technology selection been validated considering the competitiveness, structure, and potential for future innovation? 3 UI and UX What is the UI and UX? How to best articulate this? Has the user interface and user experience been studied from both a subjective and objective view to give insight into customer behaviour? 4 Legal framework / commercial aspects Has the necessary legal framework or commercial aspects that may impact upon use or operation of the software been understood and risks identified and mitigated? 5 Software development What is the software development process? Are both the business management and development team's processes resilient in order to improve the company's capability and the maturity of the software? 6 Software quality What is quality? What are the metrics around software quality? What is the maturity level, based around a qualitative and quantitative assessment? 7 Intellectual property associated What IP should be considered when it comes to software? Does the company understand both the intellectual property risks and potential opportunities associated with this software? 8 Security What does software security mean in this context? How is it being addressed? 9 An holistic approach Review of roles and responsibilities to ensure appropriate management and protection

Businesses that don't control their costs don't stay in business. How well are you doing? Is everyone in your organisation sufficiently aware of costs, managing them effectively and maximising opportunities to reduce them? If there is scope for improvement, this course will help get you back on track. It will demonstrate that cost reduction is so much more than cost control and cost cutting. True cost management is about being aware of costs, seeking to reduce them through good design and efficient operating practices whilst taking continuing action on overspending. This course will develop the participants' skills in: Being aware of costs at all times Seeking cost reduction from the start (including life-cycle costing) Appraising projects / production to identify and take out risk Understanding real budgeting Using techniques such as ZBB and ABC where appropriate Ensuring cost reports lead to action Managing a cost reduction process that delivers Benefits to the organisation will include: Identification of cost reduction and business improvement opportunities Better reporting and ownership of costs Greater awareness and control of everyday costs 1 Introduction - the cost management process The risks of poor cost control Capital and revenue costs The importance of cost awareness The importance of cost reduction Cost management - the key aspects How to build a cost management and control process checklist for your areas of responsibility 2 Cost removal - taking out costs Cost awareness Costs of poor design / poor processes Value engineering Removing redundant costs 3 The need for commercial, technical and financial appraisals Understand the problems before cash is committed and costs incurred Making the effort to identify commercial and technical risk The time value of money - DCF techniques for long term projects Cost models for production processes and projects Costing models - project appraisals The use of spreadsheets to identify sensitivity and risk How to focus on risk management 4 Budgeting - proper budgeting challenges costs The philosophy of the business - are costs an issue? The importance of having the right culture The need for detailed business objectives Budgetary control measures Designing budget reports - for action 5 Zero-based budgeting (ZBB) - the principles Much more than starting with a clean sheet of paper What ZBB can achieve The concept of decision packages - to challenge business methods and costs Only necessary costs should be incurred A review of an operating budget - demonstrating what ZBB challenges and the costs it may lead to being taken out 6 Awareness of overheads and other costs Definitions of cost - direct and indirect Dealing with overheads - what is meant by allocation, absorption or apportionment? The apparent and real problems with overheads Different ways of dealing with overheads Review of overhead allocation methods and accounting and reporting issues 7 Overheads and product costing Activity-based costing (ABC) - the principles Where and how the ABC approach may be helpful Know the 'true' cost of a product or a project Should you be in business? Will you stay in business? Identifying weaknesses in a traditional overhead allocation How ABC will help improve product or service costing Identifying which products and activities should be developed and which abandoned 8 Cost reduction culture The need for cost reports What measures can be used to identify over-spends as early as possible Cost control performance measures and ratios 9 Design of cost control reports Reports should lead to action and deliver Selecting cost control measures which can be acted upon Practice in designing action reports 10 Course summary - developing your own cost action plan Group and individual action plans will be prepared with a view to participants identifying their cost risks areas and the techniques which can be immediately applied to improve costing and reduce costs