2434 Courses in Prestatyn

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?

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?

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

Project Accounting and Finance Skills: In-House Training Do you manage both project schedules and budgets, but do not have insight into how actual results relate to the approved budget? Do you desire to have more clarity about the relationship between your project's performance with the accounting and financial systems in your organization? Do you need to understand financial and accounting terminology to bridge the gap between the 'world of finance' and the 'world of project management? Organizations have a need to manage-by-projects, because projects are the means to deliver on strategic goals and objectives. Therefore, the project manager must have an understanding of the financial world of investments to ensure the organization will realize expected business value. This requires a foundation in the principles of accounting and finance to comprehend how the project's contribution provides an organization with a competitive advantage. Learn what you must do to give your organization the assurance it needs that its investment in your project will realize business value. Learn what you must do to give your organization the assurance it needs to know that its investment in your project will realize business value. What You Will Learn At the end of this program, you will be able to: Explain the aspects of classical corporate accounting and finance effects on managing projects Determine how your project fits into the corporate income statement, balance sheet, and cash flow statement Analyze the financial aspects of managing projects Use earned value management as the basis for decision making throughout the project life Recognize the importance of the project manager's financial responsibilities Focus on what PMs do and should be doing, in support of accounting and finance Use financial information within a project environment to meet financial results Track and analyze the project's financial status and forecast with the goal of realizing benefits Generate work performance data to ensure a project's outcome aligns with financial metrics Foundation Concepts Accounting and Finance Terms and Concepts Accounting and Finance Essentials Financial Terms and Concepts Projects as Financial Investments Overview of 'Two Worlds' Project as Investments Accounting and Finance World: Standards, Principles and Practices Accounting and Finance Standards and Principles Accounting and Finance Practices Capital Budgeting Corporate Budgeting Accounting and Finance World: Economic Project Selection Methods Economic Project Selection Methods Economic Project Selection and the Business Case Project Management World Project Management and Financial Controls Project Management and Work Performance Data Project Management and Earned Value Management Project Management and Work Performance Reporting

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

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

Managing Complex Projects: In-House Training As knowledge and technology expand exponentially, organizations are finding that the tools, processes, and methods used to select, plan, and manage their projects are insufficient for the challenges posed by them. The goal of this course is to provide participants with a working knowledge of project complexities and a framework for managing the ambiguities involved in today's fast-changing, competitive, and technology-based environment As knowledge and technology expand exponentially, organizations are finding that the tools, processes, and methods used to select, plan, and manage their projects are insufficient for the challenges posed by them. Complex projects don't necessarily follow the rules of traditional projects - in many instances the projects' end-products, and the methods by which they will be produced, are not easily defined. Stakeholder diversity and geographical dispersion contribute to the difficulties project managers face in their efforts to gain acceptance of project goals, objectives, and changes. Additionally, hierarchic leadership styles, traditional lifecycle approaches, and traditional project manager competencies may no longer maximize the efficiencies that need to be realized on complex projects. The goal of this course is to provide participants with a working knowledge of project complexities and a framework for managing the ambiguities involved in today's fast-changing, competitive, and technology-based environments. What you Will Learn The learning objectives of this workshop are to enable participants to: Appreciate complexity and its impact on the management of projects Describe the differences among traditional, complicated, and complex projects Explain the effects of complexity on the PMBOK® Guide's process groups Apply a high-level model in the management of real- world projects Complexity and Projects Some characteristics of complex systems Important models/characteristics of complex projects Major players in project complexity Landscapes and project typologies A supplemental framework for complex projects Framing Framing overview Potential pitfalls in framing complex projects Possible solutions Inception Centrality of risk management PM competencies, selection Stakeholder identification, analysis Blueprint Collaborative planning Stakeholder engagements Alternative methodologies/life cycles Collaborative scheduling Procurement management Oversight, Navigation, and Adjustment Leadership and the project team Stakeholder management Networks Close and Continuous Improvement Transition/support Post-project evaluations Rewards/Recognition

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

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