1760 OV courses in London

Developing the Business Case: In-House Training Business analysts must be able to create business case documents that highlight project benefits, costs, and risks. The business case is based on the real business need to be solved. These become parts of proposals, feasibility studies, and other decision support documents. This course teaches the purpose, structure, and content of a business case. It presents the basic techniques for determining financial ROI, non-tangible benefits, and the probability of meeting expectations. What you will Learn At the end of this program, you will be able to: Perform feasibility studies Justify the business investment to solve the business problem Prepare an effective business case document Plan and implement a business case approval process Foundation Concepts The role of the BA An introduction to the BABOK® Guide The business analyst and the product / project life cycle (PLC) The business case deliverable Introducing the Business Case Process The BA and strategy analysis The BA and the business case process (BCP) The BA during the business case process (BCP) The BA after the business case process (BCP) Importance of defining solution performance metrics Defining the Business Need Overview of defining the business need Business needs: problem / opportunity statement Product vision Objectives and constraints Exploring Business Case Solutions Overview of exploring solutions Solution identification for feasibility Solution definition for analysis Assessing project risks Justifying the Business Case Overview of justifying the business case Qualitative justification Quantitative justification Approving the Business Case Overview of business case approval Developing recommendations Preparing the decision package - documents Preparing the decision package - presentations

Writing and Managing Requirements Documents: In-House Training This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals pass the IIBA™ Certification exam to become a Certified Business Analysis Professional (CBAP™). Learn more at www.iil.com/bacp. Once a business analyst has completed the information gathering and analysis to produce the solution to a business problem, the results must be documented for all stakeholders to see and understand. This course will enhance the skill set needed for writing and managing the complex readership that business analysts interact with on a day-to-day basis. What you will Learn Upon completion, participants will be able to: Write an understood requirements document that is approvable and acceptable Validate a requirements document Manage the changes to requirements documents through the SDLC Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide The business analyst and the product/project life cycle The requirements documentation process Planning for Effective Requirements Documentation Overview of requirements planning Planning for validation Planning for verification: well-formed criteria Planning for verification: understood and usable criteria Writing Effective Requirements Documents Overview of writing requirements documents Using a standard structure / template Applying formatting techniques Meeting the challenge of writing non-functional requirements Baselining Requirements Documents Overview of the requirements baseline process Validation Verification Approval Managing Requirements Change through the Product Life Cycle Overview of requirements change management Establishing a formal change management process Tracing requirements through design and development (build, test, and implementation) Following through to post-implementation (transition and early production)

Assuring Quality Through Acceptance Testing It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?

Assuring Quality Through Acceptance Testing: In-House Training It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. It is the business analyst's job to define the business problem to be solved by IT. It is also the business analyst's responsibility to confirm that the resulting solution developed by IT does, in fact, solve the defined problem. This is done first through testing, especially acceptance testing, and then through monitoring of the installed solution in the user community. The business analyst is not only concerned with the testing itself, but also with the management and monitoring of the users doing the acceptance testing, and recording, analyzing, and evaluating the results. What you will Learn Upon completion, participants will be able to: Create a set of acceptance test cases Manage and monitor an acceptance test stage where users perform the testing Work with the development team in the systems testing stage Assess the solution once it is in the business environment Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide BA roles and relationships through the project life cycle Introduction to assuring software quality through acceptance testing The Scope of IT Testing Overview of testing stages The testing process Testing documentation Pre-Acceptance Testing The BA's role in testing Early development testing stages (unit and integration) Late development testing stage (system) The Acceptance Test Stage - Part I (Planning, Design, and Development) Overview of user acceptance testing Acceptance test planning Designing user acceptance tests Developing individual user acceptance test cases Building effective user acceptance test scenarios The Acceptance Test Stage - Part II (Execution and Reporting) Operating guidelines Execution Reporting Post-Acceptance Testing Overview Project implementation Project transition (project closure) Production through retirement Testing Commercial Off-the-Shelf (COTS) Software Overview Selecting the software Implementing the software Summary What did we learn and how can we implement this in our work environments?

Earned Value Management: In-House Training: In-House Training Earned Value Management (EVM) incorporates a set of proven practices appropriate for project or program management methodologies. These include integration of program scope, schedule, and cost objectives, establishment of a baseline plan for accomplishment of program objectives and use of earned value techniques for performance measurement during the execution of a program. Earned Value Management (EVM) incorporates a set of proven practices appropriate for project or program management methodologies. These include integration of program scope, schedule, and cost objectives, establishment of a baseline plan for accomplishment of program objectives and use of earned value techniques for performance measurement during the execution of a program. EVM provides a solid platform for risk identification, corrective actions, and management re-planning as may be required over the life of a project or program. The course emphasis is on the latest EVM principles and concepts in accordance with changes and guidelines for Earned Value Management in The Guide to the Project Management Body of Knowledge (PMBOK® Guide) and The Practice Standard for Earned Value Management published by the Project Management Institute. What you Will Learn You'll learn how to: Develop a project baseline, using an effective WBS Record actual project performance Calculate EVM measures Evaluate project performance based on EVM measures Respond to project variances Integrate EVM and risk management Determine how EVM will add value to your organization Develop an EVM implementation plan for your organization Getting Started Introductions Course structure Course goals and objectives Expectations Foundation Concepts Introduction to Earned Value Management (EVM) Benefits of EVM EVM Process Overview Applications of EVM Creating a Work Breakdown Structure Reviewing WBS concepts Reviewing WBS development process (decomposition) Using a WBS to support EVM Building a Project Baseline Defining a project baseline Developing a project baseline Using a project baseline Recording Actuals Recording actuals overview Collecting data for actual project performance Determining earned value - various methods EVM Performance Measures Using current status measures Using forecasting measures Analyzing EVM measures EVM and Risk Management Integrating EVM and Risk Management Using EVM measures in the risk register Exploring how EVM can facilitate reserves management Drawing down contingency reserves Responding to Variances Introduction to variances Process for responding to variances Response options Reporting Project Performance EVM reporting overview Meeting EVM reporting needs Addressing EVM reporting challenges Implementing an EVMS Defining EVMS requirements EVM for Agile projects Tailoring the EVMS Summary and Next Steps Review of content Review of objectives / expectations Personal action plan

Earned Value Management Earned Value Management (EVM) incorporates a set of proven practices appropriate for project or program management methodologies. These include integration of program scope, schedule, and cost objectives, establishment of a baseline plan for accomplishment of program objectives and use of earned value techniques for performance measurement during the execution of a program. Earned Value Management (EVM) incorporates a set of proven practices appropriate for project or program management methodologies. These include integration of program scope, schedule, and cost objectives, establishment of a baseline plan for accomplishment of program objectives and use of earned value techniques for performance measurement during the execution of a program. EVM provides a solid platform for risk identification, corrective actions, and management re-planning as may be required over the life of a project or program. The course emphasis is on the latest EVM principles and concepts in accordance with changes and guidelines for Earned Value Management in The Guide to the Project Management Body of Knowledge (PMBOK® Guide) and The Practice Standard for Earned Value Management published by the Project Management Institute. What you Will Learn You'll learn how to: Develop a project baseline, using an effective WBS Record actual project performance Calculate EVM measures Evaluate project performance based on EVM measures Respond to project variances Integrate EVM and risk management Determine how EVM will add value to your organization Develop an EVM implementation plan for your organization Getting Started Introductions Course structure Course goals and objectives Expectations Foundation Concepts Introduction to Earned Value Management (EVM) Benefits of EVM EVM Process Overview Applications of EVM Creating a Work Breakdown Structure Reviewing WBS concepts Reviewing WBS development process (decomposition) Using a WBS to support EVM Building a Project Baseline Defining a project baseline Developing a project baseline Using a project baseline Recording Actuals Recording actuals overview Collecting data for actual project performance Determining earned value - various methods EVM Performance Measures Using current status measures Using forecasting measures Analyzing EVM measures EVM and Risk Management Integrating EVM and Risk Management Using EVM measures in the risk register Exploring how EVM can facilitate reserves management Drawing down contingency reserves Responding to Variances Introduction to variances Process for responding to variances Response options Reporting Project Performance EVM reporting overview Meeting EVM reporting needs Addressing EVM reporting challenges Implementing an EVMS Defining EVMS requirements EVM for Agile projects Tailoring the EVMS Summary and Next Steps Review of content Review of objectives / expectations Personal action plan

About this Training Course This intensive 5 full-day has been designed as a separately bookable course comprising 3 days of Well Integrity (Basic) and 2 days of Advanced Well Integrity. The intensive 3 full-day course will equip the participants with a thorough knowledge of well integrity management and risk assessment in producing assets. Based on the regulatory requirements and using real examples and exercises from around the world, this represents best practice integrity management within the oil and gas industry. When to take action with a well is a critical decision, both from a safety and economic perspective. A consistent approach to decision-making provides certainty within the organisation, focusing effort, and spending wisely. The decision-making steps will be set out to ensure all critical aspects are captured consistently. Risk analysis approaches used by different organisations and examples of risk management and risk-ranking methods will be discussed. The 2 full-day course will deepen the participants' knowledge of well integrity management, and skills for designing, operating, and maintaining well equipment. The ultimate goal is to optimise productivity at the lowest Unit Operating Cost (UOC) and to maintain mechanical integrity throughout well life cycle. Well Integrity management is looked at in three distinct stages. The first stage is during the well design which includes material selection, engineering design, cement design, coating and inhibitors and cathodic protection. The second stage is monitoring the well during the life of the well, locating possible leaks and / or loss of metal. The last stage is to manage and control any well integrity issues using specialised products, services and techniques. Training Objectives 1. Well Integrity Training: Upon completion of this course, the participants will be able to: Define the building blocks of a successful well integrity management system Develop an approach to risk management, understand risk analysis and methods applied across the industry How do we 'Make Wells Safer', learn about emerging technologies for well integrity problem diagnosis and new techniques available to 'repair' the issues Execute the basic elements of well integrity management training for field operators Evaluate well design elements that enhance or hinder well integrity status definition during the operating phase of the well life-cycle Gain the demonstrable benefits of well integrity management from field experience Review cases studies and discuss them to enhance knowledge and take on board lessons learned 2. Advanced Well Integrity: Define well integrity well categorization based on compliance to the barrier policy outlined in the regulations and develop an approach to risk management Discuss well-completion design and construction to create a 'integer' well with the lowest life cycle maintenance cost from a WIM perspective Monitoring and surveillance of well integrity, focusing on barrier competence such as cementing and corrosion Investigate and manage well integrity issues, causes & potential solutions Understand repairs needed to address 'Loss of Well Operating Envelope' Gain an overview understanding of Well Suspension & Well Abandonment Discuss further case studies as well as conduct a post course test Target Audience Invaluable for production, operations, and integrity professionals involved in implementing & managing well integrity and seeking to improve performance. It is also essential for those who need to develop and implement such systems, or who have a general need to know and understand more about well integrity management. The course will also provide a fresh approach for senior professionals and managers. Designed for professionals in the oil and gas industry who are involved in the design, construction and operation of wells from the following disciplines: Production Maintenance Production Operations Drilling Engineering Safety engineering Well Intervention Well Integrity Engineering Asset Management Course Level Intermediate Advanced Trainer Gordon Duncan has over 40 years of experience in the Oil & Gas industry. During that time, he has worked exclusively in well intervention and completions. After a number of years working for intervention service companies (completions, slickline & workovers), he joined Shell as a well service supervisor. He was responsible for the day-to-day supervision of all well intervention work on Shell's Persian/Arabian Gulf platforms. This included completion running, coil tubing, e-line, slickline, hydraulic workovers, well testing and stimulation operations. An office-based role as a senior well engineer followed. He was responsible for planning, programming and organising of all the well engineering and intervention work on a number of fields in the Middle East. He had a brief spell as a Site Representative for Santos in Australia before joining Petro-Canada as Completions Superintendent in Syria, then moved to Australia as Completions Operations Superintendent for Santos, before returning to Shell as Field Supervisor Completions and Well Interventions in Iraq where he carried out the first ever formal abandonment of a well in the Majnoon Field. While working on rotation, he regularly taught Completion Practices, Well Intervention, Well Integrity and Reporting & Planning courses all over the world. In 2014, he started to focus 100% on training and became the Technical Director for PetroEDGE. Since commencing delivering training courses in 2008, he has taught over 300 courses in 31 cities in 16 countries to in excess of 3,500 participants. POST TRAINING COACHING SUPPORT (OPTIONAL) To further optimise your learning experience from our courses, we also offer individualized 'One to One' coaching support for 2 hours post training. We can help improve your competence in your chosen area of interest, based on your learning needs and available hours. This is a great opportunity to improve your capability and confidence in a particular area of expertise. It will be delivered over a secure video conference call by one of our senior trainers. They will work with you to create a tailor-made coaching program that will help you achieve your goals faster. Request for further information post training support and fees applicable Accreditions And Affliations

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?

Enhance your venepuncture skills with our comprehensive course. Learn evidence-based techniques, infection prevention measures, patient-centered communication, and ethical considerations to ensure safe and effective practices.