4021 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

Implementing Scrum for Teams Scrum is an iterative, incremental framework for developing products. It allows the team to deliver a potentially shippable set of functionalities for each iteration, providing the agility needed to respond to rapidly changing requirements. These characteristics have led to Scrum becoming the most popular method in the world of Agile projects. This two-day course provides a practical approach to implementing the Scrum method on your projects. You will learn how to initiate a Scrum project, how to build a Product Backlog, containing user stories, and how to plan and estimate releases and iterations. You will learn how to conduct Scrum events, such as the Sprint Planning Meeting, and how to track progress during an iteration. You will apply what you learn in a series of hands-on, team-based activities and simulations that take you through the entire Scrum process. The overall goal of the course is to enable you to successfully apply the Scrum method on appropriate projects in your environment. What you will Learn At the end of this program, you will be able to: Teach-back Agile and Scrum foundation concepts Initiate a Scrum Project Conduct Team Sprint Planning and Sprint Review meetings Develop Release Plans (including effective user stories and priorities) Build a Sprint plan (including effective estimates) Executive a Sprint (including essential Scrum ceremonies) Implement Scrum in your environment Foundation Concepts Agile Mindset, Values, and Tenets Agile Benefits and Methods Scrum Overview Teams: Self-Managing, Self-Organizing, and Self-Improving Initiating a Scrum Project 'Sprint Zero' Activities Defining the Vision The Product Backlog and User Stories Acceptance Criteria Story Map Planning Releases Planning releases Estimating user stories Prioritizing user stories Selecting a Sprint length Estimating velocity Creating a release plan Planning a Sprint The Sprint Planning Meeting Building the Sprint Backlog Creating a Sprint Plan Running a Sprint Conduct a Sprint Burn-down and Burn-up Charts Negotiating Changes During a Sprint The Sprint Review Meeting Sprint Retrospective Releasing into Production Closing the Scrum Project Implementing Scrum Scrum Simulation Exercise Conditions of Success for Implementing Scrum

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

Effecting Business Process Improvement Business analysts facilitate the solution of business problems. The solutions are put into practice as changes to the way people perform in their organizations and the tools they use. The business analyst is a change agent who must understand the basic principles of quality management. This course covers the key role that business analysts play in organizational change management. What you will Learn You will learn how to: Define and document a business process Work with various business modeling techniques Perform an enterprise analysis in preparation for determining requirements Analyze business processes to discern problems Foundation Concepts Overview of business analysis and process improvement Defining the business process Introducing the proactive business analyst Focusing on business process improvement for business analysts Launching a Successful Business Process Improvement Project Overview of the launch phase Understanding and creating organizational strategy Selecting the target process Aligning the business process improvement project's goals and objectives with organizational strategy Defining the Current Process Overview of current process phase Documenting the business process Business modeling options: work-flow models Business modeling options: Unified Modeling Language (UML) model adaptations for business processes Analyzing the Current Process Process analysis overview Evaluation: establishing the control group Opportunity techniques: multi-discipline problem-solving Opportunity techniques: matrices Building and Sustaining a Recommended Process Overview of the recommended process and beyond Impact analysis Recommended process Transition to the business case Return to proactive state

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

Project Estimating and Scheduling Establishing realistic estimates and goals for projects that support business objectives and meet client expectations is one of the most challenging aspects of project planning. Delivering those results within the agreed-upon time, cost, and quality constraints is also challenging. Attempting to meet impossible deadlines with limited budgets often leads to unplanned product shortfalls, causing long-term support and utilization problems. We have all anguished about this recurring problem, but without having the skills or knowledge to take action, we are unable to break the cycle! The goal of this course is for you to be able to support business objectives and meet client expectations by selecting the right planning approach for realistic and cost effective schedules, as well as project budgets. To achieve that, you will focus on gaining the necessary knowledge, skills, and techniques. What You Will Learn At the end of this program, you will be able to: Use the work breakdown structure (WBS) as the basis for effective estimating of project resources Estimate effort and duration using a variety of techniques Develop preliminary schedules using the critical path method Apply a variety of optimization techniques to refine preliminary schedules Establish realistic schedule and cost baselines, with appropriate contingency reserves Explain how earned value management (EVM) contributes to control time and cost performance Foundation Concepts Project management basic definitions and concepts PES Key driver: competing constraints PES Process and success factors Project Definition and the WBS Project definition overview Work Breakdown Structure (WBS) Decomposition: WBS development technique Resource Planning Resource planning overview Identifying resource requirements Identifying and filling resource gaps Applying resource planning tools Effort and Duration Estimating Estimating overview Estimating perspectives and approaches Estimating techniques Effort and duration estimating best practices Project Scheduling Overview of project scheduling Dependencies and the project network diagram Critical path method (CPM) Optimizing the schedule Budget, Risk, and Contingency Planning Overview of budget, risk, and contingency planning Estimating costs Determining the budget Project risk management processes Planning contingency reserves Project Baseline and Control Overview of project baseline Negotiating and the project baseline Earned value management (EVM) Project variances and actions Project control

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?

Risk Management for IT Projects IT projects may have direct bottom-line impact on the organization, cost millions of dollars, cause organizational change and change the way the organization is perceived by clients. Many IT projects are notoriously hard to predict and are filled with risk. IT Risk Management takes a comprehensive look at IT project risk management using PMI's PMBOK® Guide Risk Management Model in the context of IT Project Life Cycle phases. The goal of this course is to arm the practitioner with a rigorous, common-sense approach to addressing uncertainty in projects. This approach includes the ability to influence project outcomes, avoid many potential project risks, and be ready to calmly and efficiently respond to unavoidable challenges. What you will Learn You'll learn how to: Describe the risk management process, using the PMBOK® Guide's standard models and terminology Discuss the potential barriers to managing risk effectively in IT project organizations Develop an effective risk management plan for IT projects Identify project risks using IT-specific, practical tools Analyze individual risk events and overall project risk using IT-specific, practical approaches Plan effective responses to IT-specific risk based on the results of risk analysis and integrate risk responses into project schedules and cost estimates Manage and control risk throughout the IT project life cycle Implement selected elements of IT project risk management on your next project Foundation Concepts Basic concepts and purpose Risk and project constraints Risk and corporate cultures Risk management and IT PLC standards Plan Risk Management for IT Projects Plan Risk management process Plan Risk management activities Design a standard template Assess the project-specific needs Tailor the template Produce a project-specific risk management plan Gain consensus and submit as part of overall project plan A risk management plan of IT projects Identify Risks for IT Projects Identify risk process overview Risk categories and examples Risk identification tools Risk events by project life-cycle phases Perform Risk Analysis for IT Projects Perform qualitative risk analysis overview Core qualitative tools for IT projects Auxiliary qualitative tools for cost and schedule estimates When to use quantitative analysis for IT projects Plan Risk Response for IT Projects Plan risk response overview Active risk response strategies for IT projects (Threat and Opportunity) Acceptance and contingency reserves Contingency planning for IT projects Plan risk responses for IT projects Implement Risk Response for IT Projects Implement Risk Responses Executing Risk Response Plans Techniques and Tools Used Continuous Risk Management Monitor Risks for IT Projects Monitor risks overview Monitor risks tips for IT projects Technical performance measurement systems Risk management implementation for IT projects

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 and Scrum Fundamentals The overall goal of the course is to provide learners with the fundamentals of what Agile and Scrum are, and how to effectively apply Agile methods in your projects. What you will Learn At the end of this program, you will be able to: Describe Agile and Scrum foundation concepts Compare and contrast Agile roles to traditional roles Initiate an Agile project Develop Release Plans Build an Iteration Plan Execute an Iteration Implement Agile in your environment Getting Started Introductions Workshop orientation Expectations Foundation Concepts Project Lifecycles What is Agile? Why Agile? A range of Agile methods Focus on Scrum The People Side of Agile A range of Agile roles Focus on Scrum roles Unique characteristics of Agile Teams Building effective Agile Teams Initiating an Agile Project Conducting Sprint Zero Setting the vision Building the Product Backlog and User Stories Defining Acceptance Criteria Planning Releases Planning releases Estimating user stories Prioritizing user stories Selecting a Sprint length Estimating velocity Creating a release plan Planning an Iteration Conducting the Sprint Planning Meeting Building the Sprint Backlog Creating a Sprint Plan Running an Iteration Executing Sprint activities Using Burn-down and Burn-up Charts Negotiating changes during a Sprint Conducting the Sprint Review Meeting Implementing Agile Conditions of success for implementing Agile and Scrum Implementing Agile Final words