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
Project Quality Management: In-House Training In today's environment, quality is the responsibility of everyone. Project success is no longer just the fulfillment of a project on schedule, on budget, and within the scope. Today, projects aren't successful unless the customer's needs are met at the highest level of quality at the lowest cost to the organization. Project Managers must know customer needs, and manage to them throughout the project lifecycle, in order to gain acceptance. Project Quality Management provides an interactive, hands-on environment for participants to practice identification of critical quality requirements (quality planning), fulfillment of those requirements through well-designed processes (Quality Assurance), and statistical awareness of technical specifications of project deliverables (Quality Control). What You Will Learn You'll learn how to: Plan for higher quality project deliverables Measure key performance indicators on projects, processes, and products Turn data into useful project information Take action on analyzed data that will drive down non-value-added costs and drive up customer acceptance and satisfaction Reduce defects and waste in current project management processes Foundation Concepts Quality Defined Customer Focus Financial Focus Quality Management Process Management Cost of Quality Planning for Quality Project Manager Role in Planning Voice of the Customer Quality Management Plan Measurement System Accuracy Data Gathering Data Sampling Manage Quality Process Management Process Mapping Process Analysis Value Stream Mapping Standardization Visual Workplace and 5S Error Proofing (Poka-Yoke) Failure Mode and Effect Analysis Control Quality The Concept of Variation Common Cause Special Cause Standard Business Reports Tracking Key Measurements Control Charts Data Analysis Variation Root Cause Analysis Variance Management Designing for Quality
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
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?
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 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
Recovering Troubled Projects: In-House Training Despite our best intentions, many of the projects that organizations undertake either don't achieve their intended business results or end in complete failure. Most seasoned project managers have had their share of experiences with difficult or troubled projects and unless they are careful, they will encounter more. This workshop does not focus on 'failed' projects but rather on those projects which without appropriate intervention would be headed for failure. Failed projects are those beyond help and which should be terminated. Here we focus on projects that are salvageable. It is an exercise-driven, no-nonsense, professional practice-focused workshop positioning the participant to immediately apply the tools and lessons learned in the classroom. The workshop employs the use of both illustrative and practical/working case studies. Illustrative case studies will examine insights from real-world troubled projects. Participants will be asked to bring descriptions of their own examples of troubled projects on which they're currently working or on which they have worked in the past. A number of these will be used as the basis for the practical/working case studies. The approach builds on and complements the disciplines addressed in Project Management Institute's PMBOK® Guide and also addresses issues that arise when managing projects in a complex environment. What You Will Learn You will learn to: Recognize the value of a structured project recovery process Explain the reasons most projects fail Analyze the causes of a project's troubles Construct a negotiation process to use with key stakeholders Apply an effective strategy to planning the recovery effort Manage, evaluate, and adjust the ongoing recovery effort Foundation Concepts Recognizing a troubled project Defining the project recovery process The Reasons Projects Fail Putting failure in perspective Reviewing management issues Analyzing planning issues Exploring complexity issues Assess the Project Stabilizing the project Determining preliminary Go / No-Go Conducting a detailed recovery assessment Negotiate the Recovery Reviewing the basics of negotiation Setting reasonable expectations Obtaining appropriate PM authority Securing key stakeholder support Plan the Recovery Planning for recoveries Rebuilding the project team Reshaping the project plan Managing parallel activities Planning for change management Implement and Adjust the Project Implementing project recoveries Facilitating change Enabling continuous learning Fostering the project team Sustaining stakeholder engagement
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
Use Cases for Business Analysis: In-House Training 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?
MASTERCLASS 8 CPD POINTS 1 DAY INTENSIVE COURSE ONLINE or IN-CLINIC NOTE! After booking we will contact you for scheduling the exact course date! Courses dates are subject to change due to mentors availability. We will inform you via email if a date becomes available! CLINICAL PRP • Sports medicine • Traumatology • Ophthalmic • Burn trauma • Wound healing –diabetic foot • Skin grafting • Dentistry-sinus lift • Tooth implants. PRP theory & equipment: Training Online Theory will enable you to understand: Anatomy Vascular Supply, Contraindications Patient consultation Complications Management Post treatment advice Dealing with equipment A certification of training will be provided upon completion of the course. Aesthetic PRP • Skin rejuvenation • Hair restoration • Fat grafting in combination PRP • Post laser •Acne & Rosacea •Acne scar •TissueVolumisation alternative of HA fillers •Aesthetic gynecology /urology. Plathelet Rich Plasma We will cover pertinent information including mechanism of action, safety and efficacy issues, management and treatment of complications, dilution guidelines, and more. Hands on practical session – skin rejuvenation and hair loss Extraction, Preparation and Dosage Management Injection techniques – face, neck and head (hair loss); also the use of cannula Upon successful completion of the course, you will receive a certificate and title of PRP Certified Practitioner. MASTER CLASS PRP & PRF During the course we are providing . Taking blood and how to use a Centrifuge . PRP injecting techniques in face neck and décolletage hands. PRP Microneedling using a DERMAPEN. Combination treatment PRP with Mesotherapy. MECHANISM OF ACTION Platelets + Leucocytes form 3D mesh release of GF Chemo attraction and migration of macrophages and stem cells Stem cells proliferates by mitosis Stem cells undergo differentiation process BENEFIT FROM PRP TREATMENT & THERAPYExperience the advantages of PRP treatment and therapy, utilizing autologous blood with natural growth factors for disease-free and hypoallergenic benefits. Boost wound healing by regulating mitosis, proliferation, and differentiation, enhancing tissue with collagen, elastin, and hyaluronic acid. Benefit from improved tissue oxygenation, nutrition flow, and support for procedures like hair transplants, fat transfers, and skin grafts.PRP works effectively in skin rejuvenation, facial resurfacing, microneedling, and combines well with HA, PDO threads, skin boosters, peeling, or CO2 lasers. It also proves beneficial for hair restoration, showing positive results in various protocols for Androgenic alopecia and age-related hair loss.PRP where works .Skin rejuvenation-facial resurfacing.application-injection alone. Microneedling Combination with HA,Combination with PDO threads,Skin boosters , peeling or CO2 lasers Hair restoration, Multiple protocols with positive results Evidence for improvement of: Androgenic alopecia-male and females, “spot hair lost” Improvement of age related hair loss. You need to be medically qualified as a doctor, dentist, nurse, pharmacist or paramedic with full governing body registration and have completed a Foundation Filler Course and to have administered a number of cases. Additional information ATTENDANCE ONLINE (Theory), IN CLINIC (Practice) COURSE LEVEL EXPERT | Masterclass Course
Disciplined Agile Scrum Master (DASM): In-House Training Is your team treading water using waterfall? Do you feel trapped in an agile framework? Would you like to find solutions to the problems you've been wrestling with? Are you looking for ways to enhance your team's agility? Break free from your old ways by choosing a way of working that fits your team's context. Find strategies to improve your processes and strengthen your team with the Disciplined Agile® tool kit. Disciplined Agile Scrum Master is a nine-lesson, instructor-led course that shows you how to use Disciplined Agile (DA™) to improve your team's way of working. In just two days, you will become familiar with foundational agile and lean practices that DA supports, practice using the tool kit to solve problems, and learn how to build high-performance teams. Filled with activities, animations, supplemental reading, and more, this course will prepare you to take the Disciplined Agile Scrum Master (DASM) exam and, equally important, start using Disciplined Agile immediately. #BBD0E0 » What You Will Learn After the completion of this course, you will be able to: Apply foundational agile and lean practices in your own team setting Describe what business agility is and how it is core to value proposition of Disciplined Agile® Describe the significance of the Disciplined Agile mindset Define the DA™ principles, promises, and guidelines and how they set Disciplined Agile apart from other frameworks Explain how people are organized into DA teams Define the primary DA roles and how they each are key to the success of a self-organizing agile team Explain how to help your team work well together using the Lean principle of 'respect people' Analyze your team's context to make better process-related decisions Select the best-fit DA life cycles for your teams Apply the five DA steps of choosing your team's way of working (WoW) Apply the relevant agile and lean techniques to successfully initiate your team Apply the relevant agile and lean techniques to support your team producing business value Apply the relevant agile and lean techniques to support your team releasing their work into production Apply the relevant agile and lean techniques to support your team on an ongoing basis Recognize when to be resilient List and define the principles of Lean Significance of the Disciplined Agile® Mindset Business agility and how it is core to value proposition of Disciplined Agile Eight DA principles and how they are core to what sets Disciplined Agile apart from other agile frameworks Which situations each of the DA™ life cycles is best applied DA Practice of choosing a team's way of working (WoW) Foundations of Agile How people are organized into DA teams Primary DA roles and how they each are key to the success of a self-organizing agile team Help your team work well together (Lean principle 'Respect people') Inception phase and why it is important DA tool kit to tailor your way of working within a select phase according to context Agile techniques and ceremonies relevant to Inception Construction phase and why it is important Agile techniques and ceremonies that take place during Construction Eliminate Waste and Build Quality (Lean principles) Deliver Value Quickly (Lean principle) Transition phase and why it is important Ongoing phase and why it is important Learn Pragmatically (Lean principle) Elements of the process blade (onion) diagram Principles of Lean When to be resilient Benefits of explicit workflow Kaizen loops and PDSA techniques for continuous improvement Options for cross-team learning: "community of practice" and "center of excellence"