595 Concept courses in London

Scrum Product Owner Workshop The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The Product Owner must be knowledgeable, available, and empowered to make decisions quickly in order for an Agile project to be successful. The Product Owner's key accountability is the Product Backlog. Managing, maintaining, and evolving the Product Backlog involves: Establishing a clear Vision that engages the Development Team and stakeholders Clearly expressing Product Backlog items Ordering the items in the Product Backlog to best achieve the Vision and goals Ensuring that the Product Backlog is visible, transparent, and clear to all Working with the Development Team throughout the project to create a product that fits the customer's needs The overall course goal is to support you in becoming an effective Product Owner. What you will Learn You'll learn how to: Differentiate between poor, good, and great Product Owner attributes, and their impact on the team, product, stakeholders, and the organization Engage your stakeholders by knowing your customers and market Develop an effective and value-driven Product Backlog Evaluate the Product Owner's role in Scrum's 5 events and team engagement Foundation Concepts Agile foundation Product owner role Product Ownership Product ownership Project vision Understanding your customers and market Personas Stakeholder management and engagement The Product Backlog Epics and user stories Preparing user stories for a sprint The product backlog Visualizing the product backlog Product backlog prioritization Technical debt Sprint Planning and Delivery Sprint planning The sprint Sprint Reviews, Retrospectives, and Closing Sprint reviews Key agile patterns Retrospectives Closing the project

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)

Scrum Product Owner Workshop: In-House Training The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. The Product Owner must be knowledgeable, available, and empowered to make decisions quickly in order for an Agile project to be successful. The Product Owner's key accountability is the Product Backlog. Managing, maintaining, and evolving the Product Backlog involves: Establishing a clear Vision that engages the Development Team and stakeholders Clearly expressing Product Backlog items Ordering the items in the Product Backlog to best achieve the Vision and goals Ensuring that the Product Backlog is visible, transparent, and clear to all Working with the Development Team throughout the project to create a product that fits the customer's needs The overall course goal is to support you in becoming an effective Product Owner. What you will Learn You'll learn how to: Differentiate between poor, good, and great Product Owner attributes, and their impact on the team, product, stakeholders, and the organization Engage your stakeholders by knowing your customers and market Develop an effective and value-driven Product Backlog Evaluate the Product Owner's role in Scrum's 5 events and team engagement Foundation Concepts Agile foundation Product owner role Product Ownership Product ownership Project vision Understanding your customers and market Personas Stakeholder management and engagement The Product Backlog Epics and user stories Preparing user stories for a sprint The product backlog Visualizing the product backlog Product backlog prioritization Technical debt Sprint Planning and Delivery Sprint planning The sprint Sprint Reviews, Retrospectives, and Closing Sprint reviews Key agile patterns Retrospectives Closing the project

Scrum Master Workshop: In-House Training A Scrum Master helps project teams properly use the Scrum framework, increasing the likelihood of the project's overall success. Scrum Masters understand Scrum values, practices, and applications and provide a level of knowledge and expertise above and beyond that of typical project managers. Scrum Masters act as 'servant leaders', helping the rest of the Scrum Team work together and learn the Scrum framework. Scrum Masters also protect the team from both internal and external distractions. What you will Learn You'll learn how to: Comprehend the Agile Manifesto and mindset Explain the fundamental principles of Scrum Guide the Scrum team in their responsibilities Write requirements in the form of user stories Define Ready and Done Estimate using planning poker and prioritize using MoSCoW Facilitate the team through the 5 Sprint events Fulfill the role of Scrum Master in a Scrum project Create Information Radiators to enable transparency Define the structure of the retrospective Foundation Concepts Agile History, Values, and Mindset Introduction to Scrum Scrum events Scrum artifacts Scrum Roles and Responsibilities Product Owner responsibilities Scrum Master responsibilities The Team responsibilities Cross-functional Teams Building Effective Teams The Product Backlog and User Stories The Product Backlog User Stories Definition of Done Backlog grooming Estimating User Stories Story points, planning poker Prioritizing User Stories The Sprint Team capacity and velocity The Sprint Planning Meeting The Sprint Backlog The Sprint Learning to self-manage, self-organize, self-improve Sprint Review and Retrospective Project Progress and Completion The Daily Scrum The Task Board and The Burndown Chart Information Radiators Closing a Scrum Project Summary and Next Steps Review of course goals, objectives, and content

Scrum Master Workshop A Scrum Master helps project teams properly use the Scrum framework, increasing the likelihood of the project's overall success. Scrum Masters understand Scrum values, practices, and applications and provide a level of knowledge and expertise above and beyond that of typical project managers. Scrum Masters act as 'servant leaders', helping the rest of the Scrum Team work together and learn the Scrum framework. Scrum Masters also protect the team from both internal and external distractions. What you will Learn You'll learn how to: Comprehend the Agile Manifesto and mindset Explain the fundamental principles of Scrum Guide the Scrum team in their responsibilities Write requirements in the form of user stories Define Ready and Done Estimate using planning poker and prioritize using MoSCoW Facilitate the team through the 5 Sprint events Fulfill the role of Scrum Master in a Scrum project Create Information Radiators to enable transparency Define the structure of the retrospective Foundation Concepts Agile History, Values, and Mindset Introduction to Scrum Scrum events Scrum artifacts Scrum Roles and Responsibilities Product Owner responsibilities Scrum Master responsibilities The Team responsibilities Cross-functional Teams Building Effective Teams The Product Backlog and User Stories The Product Backlog User Stories Definition of Done Backlog grooming Estimating User Stories Story points, planning poker Prioritizing User Stories The Sprint Team capacity and velocity The Sprint Planning Meeting The Sprint Backlog The Sprint Learning to self-manage, self-organize, self-improve Sprint Review and Retrospective Project Progress and Completion The Daily Scrum The Task Board and The Burndown Chart Information Radiators Closing a Scrum Project Summary and Next Steps Review of course goals, objectives, and content

Portfolio Management for Stakeholders This course equips and enables project, program, and functional managers (line managers) to support and contribute to starting, restarting or sustaining the implementation and effectiveness of portfolio management in an organization. Emphasis is on improving collaboration and planning between functional business areas and project/program organizations responsible for delivering investments in business change through successful delivery of projects and programs. Good functional, project, and program managers become 'great' when they understand, advocate, and effectively contribute to achieving 'real' business value through portfolio management. What you Will Learn At the end of this program, you will be able to: Outline the benefits of portfolio management State the importance of linking the strategic objectives to the initiatives in the organization Chart the portfolio governance structure Assist in the inventory of ongoing and new initiatives Identify portfolio and sub-portfolio categories Support the PMO in the prioritization of initiatives using Multi-criteria Analysis and other selection tools Collaborate with the PMO in balancing the portfolio based on the optimal use of resources and priorities Participate in resource forecasting and planning Demonstrate thresholds and variance reporting criteria Describe the purpose of Stage Gate Funding Report status against a portfolio delivery plan Present your initiative in Stage Gate Reviews List the benefits that are being realized by the initiative Foundation Concepts Portfolio Life Cycles Portfolio Governance Prioritizing Initiatives Prioritize Foundation Multi-Criteria Analysis Analytical Hierarchy Process (AHP) Strategic Alignment Balancing the Portfolio Resources, Budgets, and Equipment Communicating Decisions Planning the Portfolio Planning Review Cycles Using Stage Gate Funding Setting Thresholds and Variance Reporting Tool Examples Portfolio Delivery 'Cycle' Project and Program Life Cycles Stage Gate Reviews Interaction with the Portfolio Delivery Board Project, Program, and Functional Managers Roles and Responsibilities

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

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?

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?