65656 Courses

5 intensive days of training and learning the fundamental knowledge of hair colour. Students are taken on a colourful and exciting journey of lectures, demonstrations and hands on training with our experienced educators. Students are provided with human hair mannequin heads before completing hair colouring techniques on live models. You will also receive a FREE colour goodie bag so you can get home and start colouring!

Learn everything that you need to know to become a casino croupier then decide whether you want to work on cruise ships or casinos all over the world

PYTHON BOOTCAMP: This 12-week Python Data Analytics Data Boot Camp is designed to give you a complete skill set required by data analysts . You will be fully fluent and confident as a Python data analyst, with full understanding of Python Programming. From Data, databases, datasets, importing, cleaning, transforming, analysing to visualisation and creating awesome dashboards The course is a practical, instructor-lead program.

Scrum Product Owner Exam Prep 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 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

Scrum Product Owner Exam Prep 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

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?

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

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

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

Agile PM vs. Waterfall PM (In-Person) The concept of Agile project management refers to the use of a number of tools and techniques that are based on enabling project teams to deliver products to a predetermined and agreed timeline. The concept of Waterfall project management refers to the use of a number of tools and techniques that are based on enabling project teams to deliver products to a pre-determined and agreed specification. The selection of the most appropriate project management method has, historically, been a choice of 'either/or' when it comes to these two approaches. It is now becoming clear that for many projects, the selection of a single project management method does not satisfy the professionalism of the project team nor does it optimize the return on investment for the sponsoring organization. A radically different approach is needed. This course presents an approach to project management which capitalizes on the most appropriate elements of each method tailored to the specific project being undertaken. In this course, the Waterfall approach will be based on the PRINCE2 model. Each method will be presented to highlight its particular strategy and strengths. The course will then propose project scenarios which will require the project team to use a hybrid method which brings together aspects of both methods. The overall goal of the course is threefold: To introduce the Waterfall approach to product development. To introduce the Agile approach to product development. To explore how a combination of both approaches can bring added value to the sponsoring organization and their customers. What you will Learn You'll learn how to: Identify the strengths that the Waterfall approach brings to project work Identify the strengths that the Agile approach brings to project work Exploit the strengths of each method by combining their practices and protocols to maximize the potential for return on investment Getting Started Introductions Course structure Course goals and objectives Foundation Concepts The purpose and importance of project work The drivers for change The roles associated with projects The parameters of project work The significance of project parameters The problem of meeting all parameters The rationale for ranking the parameters for optimal business return on investment The Waterfall Approach to Parameter Optimization What do we mean by 'Waterfall'? Setting, aligning and managing the parameter priorities The PRINCE2® process model The strengths of Waterfall / PRNCE2® The Agile Approach to Parameter Optimization What do we mean by Agile? Setting, aligning and managing the parameter priorities The Agile PM process model The strengths of Agile / Agile PM Options for Implementing PRINCE2® with Agile PM The available tool set(s) Six options for combining both methods The value each option brings to the project The value each option bring to the sponsoring organization Guidelines for experimenting with these and other creative combinations The Challenges for the 'Combination' Project Management Team The sponsoring organization The decision making body within the project The project manager The delivery team