48 Agile Business Analyst courses in London

Facilitation Skills for Business Analysts: 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™). Business analysts are communicators who bridge the gap between people with business needs and knowledge and the people who will provide solutions. Business analysts are continuously involved in communications with stakeholders and developers as they create the solution to business problems. They participate in information-gathering sessions including interviewing, joint requirements definition, and Joint Application Design (JAD) workshops which are used to streamline information gathering and get immediate validation from user representatives. The business analyst is also involved with negotiating the solution with the stakeholders, upper-level management, and the developers, mediating among the groups when disagreements take place, and influencing the results of decisions during the solution cycle. This course teaches the methods needed to organize and run information-gathering events. It combines the basics of graphic decision making and modeling with facilitation, communication, and meeting management skills. What you will Learn At the end of this program, you will be able to: Identify the major touch points between key BABOK® Guide knowledge areas and business analysis communication Describe the facilitation skills that are most supportive of those intersections Improve your ability to apply these skills in the context of your business analyst functions Foundation Concepts The role of the Business analyst (BA) An Introduction to the BABOK® Guide Business analyst roles and the product / project life cycle (PLC) Facilitation skills for the business analyst The BABOK® Guide and Communication An introduction to the communication process Addressing basic communications challenges Planning business analysis communication Communication and BABOK® Guide tasks Targeted Elicitation Techniques Synergy between communication and targeted elicitation techniques Preparing for elicitation Cornerstone targeted technique: interviews Other targeted elicitation techniques Related general communication skills Group Elicitation Techniques Synergy between requirements communication and group elicitation techniques Cornerstone group elicitation technique - requirements workshops Other group elicitation techniques Related general communication skills - meeting management best practices Related general communication skills - facilitating best practices Process / Model-Based Elicitation Techniques Synergy between requirements communication and process / model-based elicitation techniques Process / model-based elicitation techniques Related interpersonal skills - problem solving and decision making Investigative Elicitation Techniques Synergy between requirements communication and investigative elicitation techniques Cornerstone investigative elicitation technique - document analysis Other investigative elicitation techniques Summary of elicitation techniques by usage in the requirements process Using Presentations, Structured Walkthroughs, and Influencing Structured walkthroughs, presentations, and influencing within BABOK® Guide tasks Cornerstone technique - structured walkthroughs General communication skill - presenting Related interpersonal skill - influencing Special Facilitation Skills - Negotiating and Mediating Negotiating Mediating

Facilitation Skills for Business Analysts 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™). Business analysts are communicators who bridge the gap between people with business needs and knowledge and the people who will provide solutions. Business analysts are continuously involved in communications with stakeholders and developers as they create the solution to business problems. They participate in information-gathering sessions including interviewing, joint requirements definition, and Joint Application Design (JAD) workshops which are used to streamline information gathering and get immediate validation from user representatives. The business analyst is also involved with negotiating the solution with the stakeholders, upper-level management, and the developers, mediating among the groups when disagreements take place, and influencing the results of decisions during the solution cycle. This course teaches the methods needed to organize and run information-gathering events. It combines the basics of graphic decision making and modeling with facilitation, communication, and meeting management skills. What you will Learn At the end of this program, you will be able to: Identify the major touch points between key BABOK® Guide knowledge areas and business analysis communication Describe the facilitation skills that are most supportive of those intersections Improve your ability to apply these skills in the context of your business analyst functions Foundation Concepts The role of the Business analyst (BA) An Introduction to the BABOK® Guide Business analyst roles and the product / project life cycle (PLC) Facilitation skills for the business analyst The BABOK® Guide and Communication An introduction to the communication process Addressing basic communications challenges Planning business analysis communication Communication and BABOK® Guide tasks Targeted Elicitation Techniques Synergy between communication and targeted elicitation techniques Preparing for elicitation Cornerstone targeted technique: interviews Other targeted elicitation techniques Related general communication skills Group Elicitation Techniques Synergy between requirements communication and group elicitation techniques Cornerstone group elicitation technique - requirements workshops Other group elicitation techniques Related general communication skills - meeting management best practices Related general communication skills - facilitating best practices Process / Model-Based Elicitation Techniques Synergy between requirements communication and process / model-based elicitation techniques Process / model-based elicitation techniques Related interpersonal skills - problem solving and decision making Investigative Elicitation Techniques Synergy between requirements communication and investigative elicitation techniques Cornerstone investigative elicitation technique - document analysis Other investigative elicitation techniques Summary of elicitation techniques by usage in the requirements process Using Presentations, Structured Walkthroughs, and Influencing Structured walkthroughs, presentations, and influencing within BABOK® Guide tasks Cornerstone technique - structured walkthroughs General communication skill - presenting Related interpersonal skill - influencing Special Facilitation Skills - Negotiating and Mediating Negotiating Mediating

Agile Sprint Planning The goal of the course is to provide you and your team with the ability to develop effective and realistic Sprint plans. Without effective Sprint Plans, iterations are set up for failure. But Sprint Planning cannot be improved on its own, in isolation. The Scrum processes are highly intertwined and influence each other. The surrounding artifacts, events, and roles must be examined closely, and enhanced, in order to improve Sprint Planning. This course will remind you of the theory to reinforce the principles, but will concentrate on next-level skills, so that you and the team are able to create realistic and usable Sprint Plans. This course is not introductory. You are already aware of the Scrum framework and have been implementing Scrum on your projects. Now is the time to improve efficiency and effectiveness, to facilitate successful Agile projects. What you will Learn You'll learn how to: Identify and correlate the key symptoms and root causes of ineffective sprint plans Improve key Product Backlog elements Evaluate Agile roles in sprint planning Appraise key product practices Enhance project transparency The Product Backlog User stories Acceptance Criteria Backlog Refinement Supporting Roles Product Owner (the Backlog) Development Team Stakeholders and SMEs Supporting Product Practices Roadmaps and release plans and story maps Definition of Done Technical Debt Transparency Daily Scrums Information radiators Retrospectives Sprint Planning Capacity and Velocity Sprint Planning Meetings The Sprint Backlog Summary What did we learn, and how can we implement this in our work environments?

AgileSHIFT® AgileSHIFT® is the change your organization needs: the business landscape is changing and transformation is necessary. But it is also hard. This program is aimed to drive transformational change throughout an organization. This new enterprise agility guidance empowers individuals to use a lightweight tailorable framework to understand, engage with, and champion change by embracing agile and lean ways of working. Taking a holistic view of an organization, AgileSHIFT® will create and support the champions of change your business needs in order to thrive in an increasingly competitive and disruptive workplace. What You Will Learn At the end of this program you will be able to: Identify why organizations need to create a culture of enterprise agility in response to a changing context Recognize how to think and work differently to enable change Explore agile and lean thinking concepts and how they relate to running and changing your organization Utilize key concepts of the AgileSHIFT® framework Describe the AgileSHIFT® delivery approach Getting Started A changing context Enterprise agility The Purpose of AgileSHIFT® The AgileSHIFT® Framework AgileSHIFT® principles AgileSHIFT® practices AgileSHIFT® roles AgileSHIFT® workflow Benefits of AXELOS.com Summary and Next Steps

AgileSHIFT®: In-House Training AgileSHIFT® is the change your organization needs: the business landscape is changing and transformation is necessary. But it is also hard. This program is aimed to drive transformational change throughout an organization. This new enterprise agility guidance empowers individuals to use a lightweight tailorable framework to understand, engage with, and champion change by embracing agile and lean ways of working. Taking a holistic view of an organization, AgileSHIFT® will create and support the champions of change your business needs in order to thrive in an increasingly competitive and disruptive workplace. What You Will Learn At the end of this program you will be able to: Identify why organizations need to create a culture of enterprise agility in response to a changing context Recognize how to think and work differently to enable change Explore agile and lean thinking concepts and how they relate to running and changing your organization Utilize key concepts of the AgileSHIFT® framework Describe the AgileSHIFT® delivery approach Getting Started A changing context Enterprise agility The Purpose of AgileSHIFT® The AgileSHIFT® Framework AgileSHIFT® principles AgileSHIFT® practices AgileSHIFT® roles AgileSHIFT® workflow Benefits of AXELOS.com Summary and Next Steps

Developing the Business Case 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

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

Agile Sprint Planning: In-House Training The goal of the course is to provide you and your team with the ability to develop effective and realistic Sprint plans. Without effective Sprint Plans, iterations are set up for failure. But Sprint Planning cannot be improved on its own, in isolation. The Scrum processes are highly intertwined and influence each other. The surrounding artifacts, events, and roles must be examined closely, and enhanced, in order to improve Sprint Planning. This course will remind you of the theory to reinforce the principles, but will concentrate on next-level skills, so that you and the team are able to create realistic and usable Sprint Plans. This course is not introductory. You are already aware of the Scrum framework and have been implementing Scrum on your projects. Now is the time to improve efficiency and effectiveness, to facilitate successful Agile projects. What you will Learn You'll learn how to: Identify and correlate the key symptoms and root causes of ineffective sprint plans Improve key Product Backlog elements Evaluate Agile roles in sprint planning Appraise key product practices Enhance project transparency The Product Backlog User stories Acceptance Criteria Backlog Refinement Supporting Roles Product Owner (the Backlog) Development Team Stakeholders and SMEs Supporting Product Practices Roadmaps and release plans and story maps Definition of Done Technical Debt Transparency Daily Scrums Information radiators Retrospectives Sprint Planning Capacity and Velocity Sprint Planning Meetings The Sprint Backlog Summary What did we learn, and how can we implement this in our work environments?

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?