129 Courses in London

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?

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?

Writing and Managing Requirements Documents 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)

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)

Learn to teach basic life support effectively with our "Promoting Best Practice in Basic Life Support Instruction" course. Ideal for healthcare professionals, educators, and individuals interested in life-saving interventions.

Business Analysis Fundamentals This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals to pass the IIBA® Certification exam to become a Certified Business Analysis Professional (CBAP™). This course teaches participants the overall process of business analysis and where it fits in the bigger picture of the project life cycle and the business context. The course is interactive and combines discussion, active workshops, and demonstrations of techniques. The goal is bottom-line results that cut through the real-world problems facing people seeking to improve the way they operate to develop new and improved systems and products or otherwise deliver results through project performance. What you will Learn At the end of this program, you will be able to: Define the solution scope Work with the development team in the systems testing stage Ensure the solution is usable in the business environment Foundation Concepts Defining the business analyst (BA) function The role of the BA as change agent An introduction to the BABOK® Guide BA roles and relationships through the project life cycle (PLC) Business Analysis Planning and Monitoring Overview of business analysis planning and monitoring (BAP&M) Business analysis planning and monitoring - process and tools Business analysis planning and monitoring - roles and responsibilities Business analysis planning and monitoring - governance, information management, and performance improvement Elicitation and Collaboration Overview of elicitation and collaboration Elicitation and collaboration techniques Requirements Life Cycle Management Overview of requirements life cycle management Requirements life cycle management task details Strategy Analysis Overview of strategy analysis Analyze current state Define future state Assess risks Define change strategy Requirements Analysis and Design Definition Overview of requirements analysis and design definition (RA&DD) The anatomy of requirements RA&DD task descriptions RA&DD techniques Solution Evaluation Overview of solution evaluation Solution evaluation tasks Solution evaluation in development stages Underlying Competencies Overview of underlying competencies (UC) Underlying competencies

Business Analysis Fundamentals: In-House Training This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals to pass the IIBA® Certification exam to become a Certified Business Analysis Professional (CBAP™). This course teaches participants the overall process of business analysis and where it fits in the bigger picture of the project life cycle and the business context. The course is interactive and combines discussion, active workshops, and demonstrations of techniques. The goal is bottom-line results that cut through the real-world problems facing people seeking to improve the way they operate to develop new and improved systems and products or otherwise deliver results through project performance. What you will Learn At the end of this program, you will be able to: Define the solution scope Work with the development team in the systems testing stage Ensure the solution is usable in the business environment Foundation Concepts Defining the business analyst (BA) function The role of the BA as change agent An introduction to the BABOK® Guide BA roles and relationships through the project life cycle (PLC) Business Analysis Planning and Monitoring Overview of business analysis planning and monitoring (BAP&M) Business analysis planning and monitoring - process and tools Business analysis planning and monitoring - roles and responsibilities Business analysis planning and monitoring - governance, information management, and performance improvement Elicitation and Collaboration Overview of elicitation and collaboration Elicitation and collaboration techniques Requirements Life Cycle Management Overview of requirements life cycle management Requirements life cycle management task details Strategy Analysis Overview of strategy analysis Analyze current state Define future state Assess risks Define change strategy Requirements Analysis and Design Definition Overview of requirements analysis and design definition (RA&DD) The anatomy of requirements RA&DD task descriptions RA&DD techniques Solution Evaluation Overview of solution evaluation Solution evaluation tasks Solution evaluation in development stages Underlying Competencies Overview of underlying competencies (UC) Underlying competencies

Project Management Fundamentals: In-House Training Many projects are performed by highly competent and effective people who have little or no project management training. They perform projects like process improvement, marketing campaign development, new product development, event planning and production, and other 'tasks' which are projects. Project Management Fundamentals (PMF) is designed to support those people who need a solid foundation in project management, without being unnecessarily burdened to learn it while on the job. The course offers practical skills, concepts, and principles that can be taken back to the workplace, along with insights needed to adapt them to specific project environments. In today's environment, that means possibly adapting to Agile / Iterative methods. So, we have recently added key Agile concepts to provide a basic understanding of shifting towards agility. Since PMF's course goal is to achieve quality performance by learning effective planning and control, the focus is on a process orientation and an analytical, systems-oriented approach. Together, these frameworks promote project-related problem solving and decision-making skills necessary for real world projects. They honor project needs for collaboration, clear communications among people, and interpersonal and relationship skills. Recognition of these needs are woven throughout PMF, but are highlighted in two specific areas: Module 2 - People and Projects Module 8 - Executing, Communicating, and Developing the Team What You Will Learn At the end of this program, you will be able to: Describe the value of strong project management Identify characteristics of a successful project and project manager Recognize how current agile / adaptive practices fit within project management Explore project management processes, including Initiating, Planning, Execution, Monitoring & Controlling, and Closing Utilize project management processes and tools, based on case studies and real-world situations Create an initial project plan Use standard project management terminology Foundation Concepts Project management and definitions Value and focus of PM Competing constraints and project success Project life cycles People and Projects People and projects overview The project manager The project team People and projects in organizations Initiating and Defining Requirements Initiating the project Developing the project charter Conducting stakeholder assessments Defining requirements Using the Work Breakdown Structure Defining the Work Breakdown Structure (WBS) Developing a usable WBS Using the WBS Managing Project Risk Making the case for risk management Overview to planning for risk Identifying risks Analyzing risks Planning responses to risks Implementing response and monitoring risks Considerations for adaptive environments Estimating Defining an estimate Estimating approaches Estimating practices Estimating cost Validating an estimate Scheduling Defining the scheduling process and related terminology Sequencing and defining dependencies Determining the critical path Considering schedule risks and optimizing the schedule Executing, Communicating, and Developing the Team From baseline to execution Project communications and stakeholder relationships High-performing teams Monitoring and Controlling Defining monitoring and controlling Viewing control through the competing demands lens Variance Analysis and corrective action (Earned Value) Considerations in adaptive environments Closing the Project Closing projects Focusing on project transition Focusing on post-project evaluations

Project Management Fundamentals Many projects are performed by highly competent and effective people who have little or no project management training. They perform projects like process improvement, marketing campaign development, new product development, event planning and production, and other 'tasks' which are projects. Project Management Fundamentals (PMF) is designed to support those people who need a solid foundation in project management, without being unnecessarily burdened to learn it while on the job. The course offers practical skills, concepts, and principles that can be taken back to the workplace, along with insights needed to adapt them to specific project environments. In today's environment, that means possibly adapting to Agile / Iterative methods. So, we have recently added key Agile concepts to provide a basic understanding of shifting towards agility. Since PMF's course goal is to achieve quality performance by learning effective planning and control, the focus is on a process orientation and an analytical, systems-oriented approach. Together, these frameworks promote project-related problem solving and decision-making skills necessary for real world projects. They honor project needs for collaboration, clear communications among people, and interpersonal and relationship skills. Recognition of these needs are woven throughout PMF, but are highlighted in two specific areas: Module 2 - People and Projects Module 8 - Executing, Communicating, and Developing the Team What You Will Learn At the end of this program, you will be able to: Describe the value of strong project management Identify characteristics of a successful project and project manager Recognize how current agile / adaptive practices fit within project management Explore project management processes, including Initiating, Planning, Execution, Monitoring & Controlling, and Closing Utilize project management processes and tools, based on case studies and real-world situations Create an initial project plan Use standard project management terminology Foundation Concepts Project management and definitions Value and focus of PM Competing constraints and project success Project life cycles People and Projects People and projects overview The project manager The project team People and projects in organizations Initiating and Defining Requirements Initiating the project Developing the project charter Conducting stakeholder assessments Defining requirements Using the Work Breakdown Structure Defining the Work Breakdown Structure (WBS) Developing a usable WBS Using the WBS Managing Project Risk Making the case for risk management Overview to planning for risk Identifying risks Analyzing risks Planning responses to risks Implementing response and monitoring risks Considerations for adaptive environments Estimating Defining an estimate Estimating approaches Estimating practices Estimating cost Validating an estimate Scheduling Defining the scheduling process and related terminology Sequencing and defining dependencies Determining the critical path Considering schedule risks and optimizing the schedule Executing, Communicating, and Developing the Team From baseline to execution Project communications and stakeholder relationships High-performing teams Monitoring and Controlling Defining monitoring and controlling Viewing control through the competing demands lens Variance Analysis and corrective action (Earned Value) Considerations in adaptive environments Closing the Project Closing projects Focusing on project transition Focusing on post-project evaluations

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?