4001 Courses in Ewell

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

Implementing Scrum for Teams: In-House Training 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 Exam Prep This workshop prepares you for the Scrum.org Professional Scrum Master (PSM)™ I certification. A voucher for the exam and the access information you will need to take the exam will be provided to you via email after you have completed the course. NOTE: If you have participated in any of IIL's other Scrum workshops, you can bypass this program and focus on reading/studying the Scrum Guide and taking practice exams from Scrum.org. 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. The Professional Scrum Master™ I (PSM I) certificate is a Scrum.org credential that enables successful candidates to demonstrate a fundamental level of Scrum mastery. PSM I credential holders will grasp Scrum as described inThe Scrum Guide™1 and recognize how those concepts can be applied. They will also share a consistent terminology and approach to Scrum with other certified professionals. What you will Learn You'll learn how to: Successfully prepare for the Scrum.org PSM I exam Comprehend the Agile Manifesto and mindset Explain the fundamental principles of Scrum, including events, artifacts, and roles Guide the Scrum team in their responsibilities Define Ready and Done Write requirements in the form of user stories 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 Getting Started Introductions Workshop orientation Exam prep preview 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 Exam prep next steps

The Agile Project Manager Change isn't coming, it's already here. The project environment is becoming more volatile, uncertain, complex, and ambiguous. Project management and project managers must transform and evolve in order to keep up with these changes. Agile has been a disruptor in the field of project management, having over 20 years of successes and benefits to organizations that have adopted their frameworks. The Agile frameworks have proven themselves to be more adept in dealing with this uncertainty. But Agile isn't just about following a different way of working. What do you need to learn, do, and become in order to continue in the current and future environment? It is a powerful combination of knowledge, competencies, and mindset. In an increasingly complicated project environment, this course provides participants with the knowledge needed to not only survive but thrive. What you will Learn At the end of this program, you will be able to: Evaluate the changing project environment and the needed knowledge, skills, and behaviors Demonstrate innovative project manager competencies of leading change, servant leadership, and focus on value Utilize Lean and Agile principles to maximize value and improve project performance Construct a hybrid Agile model that is unique to your project Assess your role in Business Agility as an Agile Project Manager Getting Started Introductions Workshop orientation Expectations Foundations Recap: What is Agile? A changed project environment The future project manager Agile Project Management Competencies Focusing on value Championing change Servant leadership Coaching / mentorship Facilitation Lean and Agile Principles Optimizing flow Making things small Continuous planning Just-In-Time requirements Visualizing work Hybrid Agile Considerations Considering a Hybrid Approach Examining Strengths and Weaknesses of Each Approach Selecting Waterfall / Agile Roles, Practices, and Techniques Reviewing Three Hybrid Scenarios Constructing the Hybrid Project Implementing Agile Pitfalls and Concerns Agile in the Organization Business Agility

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

Project Management Fundamentals for IT Projects: In-House Training A number of factors impact the new project manager's role within IT - for instance, the need to fully integrate IT into the business improvement process and the advent of distributed technology and Business Process Reengineering. As a result, the range of activities required of a new project manager has greatly increased, as well as the range of people with whom he or she interacts. This workshop enables you to minimize the problems inherent in managing a systems development project. What You Will Learn You'll learn how to: Articulate the benefit of using a project management methodology, processes, and various life cycles for IT projects Articulate on various standards and maturity models that provide benefits to performing organizations that manage IT projects Describe governance, gating, and the processes required for project origination Conduct a stakeholder analysis and describe its benefits throughout the project life cycle Gather good requirements, develop a work breakdown structure (WBS), and establish a baseline project plan Execute against the baseline project plan while managing change and configuration items Monitor and control the project activities using the baseline project plan and earned value management concepts Close the project by conducting scope verification, procurement audits, gathering lessons learned, archiving project records, and releasing resources Getting Started Course goal Course structure Course goals and objectives Foundation Concepts Key definitions and concepts Methodologies, processes, and project life cycles Project success factors and the benefits of standards and models Project Originating and Initiating Originating projects Initiating projects Planning Stakeholder Engagement and Resource Management Planning stakeholder engagement Planning human resources management Developing effective leadership skills Planning Scope and Quality Management Planning project scope Planning project quality Planning Schedule Management Planning project time Identifying schedule activities Sequencing schedule activities Estimating activity resources and time Developing project schedule Optimizing the project schedule Planning Risk and Cost Management Planning for project risks Planning project costs Estimating project costs Developing a project budget Planning Communication and Procurement Management Planning project communications Planning project procurements Project Executing, Monitoring and Controlling, and Closing Project executing Project monitoring and controlling Project closing

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?

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?