275 CLO courses in Edinburgh

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 Contract Management Skills: In-House Training Contracts are a critical part of most large or strategic projects/programs. As such, it is imperative that Project and Program Managers be well versed on basic implications of a contract as well as best practices in contract management. While not as critical a need, anyone involved in projects that involve external relationships should have a healthy appreciation for the power of good contract management. The overall goal of the course is to provide knowledge to manage complex contracts in a global environment. What You Will Learn After this program, you will be able to: Explain overall project procurement process from a buyer and seller perspective Recognize the importance of key contractual terms and how they affect projects Evaluate and contribute to the pre-contract documents and processes Identify and mitigate common pitfalls throughout the procurement process Utilize techniques to administer contracts Getting Started Introductions Course structure Course goals and objectives Foundation Concepts The Importance of Contract Management Terms and Definitions Contract Management Process Legal Systems Codes of Conduct Planning Business Analysis Procurement Management Plan Procurement Statement of Work (SOW) Common Pitfalls Solicit Contract Market Analysis Bid documents Sellers' Proposals Pitfalls Execute Contract Evaluate and Award Contract Negotiate Contract Execute Contract Common Pitfalls Deliver the Contract Preparing to Deliver Project Plan Risk Management Common Pitfalls Administer Contract Enabling Contract Management Contract Performance Monitoring and Control Change Management Financial Management / Payment Dispute Management & Resolution Contract Completion and Closure

Scrum Product Owner Exam Prep: In-House Training This workshop prepares you for the Scrum.org PSPO™ 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 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 need The Professional Scrum Product Owner™ I (PSPO I) certificate is a Scrum.org credential that enables successful candidates to demonstrate a fundamental level of Scrum mastery. PSPO I credential holders demonstrate an intermediate understanding of the Scrum framework, and how to apply it to maximize the value delivered with a product. They will exhibit a dedication to continued professional development, and a high level of commitment to their field of practice. Scrum.org does not require that you take their own sponsored or any preparatory training. However, training can facilitate your preparation for this credential. And this course is based on IIL's Scrum Product Owner Workshop, which is aligned with The Scrum Guide™. It will provide you with the information you need to pass the exam and IIL will make the arrangements for your online exam. You will be provided with an exam code and instructions, so that you can take the exam at your convenience, any time you are ready after the course. Passwords have no expiration date, but they are valid for one attempt only. See additional exam details on the next page. What you will Learn You'll learn how to: Successfully prepare for the Scrum.org PSPO I exam Identify the characteristics of a successful Product Owner Create a powerful vision statement Apply techniques to understand your customers and the market Manage and engage stakeholders Write effective user stories with acceptance criteria Utilize techniques to visualize and prioritize the Product Backlog Participate in the 5 Scrum events as the Product Owner Understand the Product Owner's role in closing a Scrum project Getting Started Introductions Workshop orientation Exam prep preview Fundamentals Recap Agile Manifesto, values, and mindset Product Owner characteristics Good vs. great Product Owner Product Ownership Product ownership Project vision Understand your customers and market Personas Stakeholder management and engagement The Product Backlog User Stories and Acceptance Criteria Preparing User Stories for a Sprint The Product Backlog Visualizing the Product Backlog Product Backlog Prioritization Technical Debt Sprint Planning and Daily Standups Sprint Planning Planning Poker Team Engagement Daily Standups Sprint Review, Retrospectives, and Closing Sprint Reviews Key Agile Patterns Retrospectives Closing the Project Summary and Next Steps Review of course goals, objectives, and content Exam prep next steps

In this course you will understand what mentoring is about, understand your roles in the process. Gain self-insight into your own interpersonal style and way of relating to others that may affect mentoring interactions.

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

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

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?

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

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

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?