2519 Courses near Birchington

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

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

Project Risk Management: In-House Training Have you been surprised by unplanned events during your projects? Are you and your project team frequently fighting fires? Well, you are not alone. Uncertainty exists in any project environment. While it's impossible to predict project outcomes with 100% certainty, you can influence the outcome, avoid potential risks, and be ready to respond to challenges that arise. In this course, you'll gain the proper knowledge needed to identify, assess, plan for, and monitor risk in your projects. You'll learn how to set up and implement risk management processes, helping you to minimize uncertainty and achieve more consistent, predictable outcomes as a result. What You Will Learn You'll learn how to: Demonstrate to others how the risk management processes in A Guide to the Project Management Body of Knowledge (PMBOK® Guide) apply to your project's environment, especially for high-risk projects Adapt these processes for a particular high-risk project team's operating principles Explain the importance of using risk management best practices at single and enterprise project levels Lead an initiative to implement risk management best practices in your project environment Foundation Concepts Risk-related definitions The risk management process High-risk projects and project failures Classical failures in implementing risk management Plan Risk Management Project risk management and governance Risk management planning for high-risk projects High-risk variations on a risk management plan Identify Risk Adapting the risk identification process for high-risk projects Recognizing risks spontaneously Confirming and structuring risk events for treatment Wrapping up risk identification for high-risk projects Perform Qualitative Risk Analysis Adapting qualitative risk analysis for high-risk projects Accelerating risk analysis Clearing risk action Wrapping up qualitative risk analysis for the next level Perform Quantitative Risk Analysis Adapting quantitative risk analysis for high-risk projects Ensuring effective risk analyses with data quality assessments Building a foundation for quantitative risk analysis Using discrete quantitative tools Using continuous quantitative tools Wrapping up quantitative risk analysis for high-risk projects Plan Risk Responses Adapting risk response planning for high-risk projects Optimizing active risk response strategies Leveraging contingencies for high project performance Wrapping up risk response planning for high-risk projects Implement Risk Responses Implementing Risk Responses Process Executing Risk Response Plans Tools and Techniques Best Practices Continuous Risk Management Monitor Risks Adapting risk monitoring for high-risk projects Optimizing risk plan maintenance Weaving risk reassessment into the project's progress Maintaining a continuous 'vigil' in high-risk project environments

Effecting Business Process Improvement: In-House Training Business analysts facilitate the solution of business problems. The solutions are put into practice as changes to the way people perform in their organizations and the tools they use. The business analyst is a change agent who must understand the basic principles of quality management. This course covers the key role that business analysts play in organizational change management. What you will Learn You will learn how to: Define and document a business process Work with various business modeling techniques Perform an enterprise analysis in preparation for determining requirements Analyze business processes to discern problems Foundation Concepts Overview of business analysis and process improvement Defining the business process Introducing the proactive business analyst Focusing on business process improvement for business analysts Launching a Successful Business Process Improvement Project Overview of the launch phase Understanding and creating organizational strategy Selecting the target process Aligning the business process improvement project's goals and objectives with organizational strategy Defining the Current Process Overview of current process phase Documenting the business process Business modeling options: work-flow models Business modeling options: Unified Modeling Language (UML) model adaptations for business processes Analyzing the Current Process Process analysis overview Evaluation: establishing the control group Opportunity techniques: multi-discipline problem-solving Opportunity techniques: matrices Building and Sustaining a Recommended Process Overview of the recommended process and beyond Impact analysis Recommended process Transition to the business case Return to proactive state

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

Writing and Managing Requirements Documents: In-House Training This course is part of IIL's Business Analysis Certificate Program (BACP), a program designed to help prepare individuals pass the IIBA™ Certification exam to become a Certified Business Analysis Professional (CBAP™). Learn more at www.iil.com/bacp. Once a business analyst has completed the information gathering and analysis to produce the solution to a business problem, the results must be documented for all stakeholders to see and understand. This course will enhance the skill set needed for writing and managing the complex readership that business analysts interact with on a day-to-day basis. What you will Learn Upon completion, participants will be able to: Write an understood requirements document that is approvable and acceptable Validate a requirements document Manage the changes to requirements documents through the SDLC Foundation Concepts The role of the business analyst An introduction to the BABOK® Guide The business analyst and the product/project life cycle The requirements documentation process Planning for Effective Requirements Documentation Overview of requirements planning Planning for validation Planning for verification: well-formed criteria Planning for verification: understood and usable criteria Writing Effective Requirements Documents Overview of writing requirements documents Using a standard structure / template Applying formatting techniques Meeting the challenge of writing non-functional requirements Baselining Requirements Documents Overview of the requirements baseline process Validation Verification Approval Managing Requirements Change through the Product Life Cycle Overview of requirements change management Establishing a formal change management process Tracing requirements through design and development (build, test, and implementation) Following through to post-implementation (transition and early production)

Agile Release Plans: In-House Training While many Agile frameworks provide guidance on a focus on value and iterative development, many do not explain how that value is delivered to the customer. Release Plans have become an accepted and common practice to bridge the gap between the Product Vision and the Product Backlog (Agile requirements). In this course, you will be provided with an introduction to Agile and to Scrum, the most utilized Agile framework. You will also learn how the Vision, Roadmap, and Charter help to establish the Release Plan. The goal of this course is to equip you with the necessary knowledge, skills, and techniques to build Release Plans to ensure you deliver the most value to your customers. What you will Learn At the end of this program, you will be able to: Recall the Scrum framework elements (roles, events, and artifacts) Examine the benefits of Agile Develop a Product Vision and Roadmap Create an Agile Project Charter Prepare a Release Plan Write user stories to support a Product Backlog Foundation Concepts Introduction to Scrum Scrum Overview Agile Benefits Product Definition Business Goals Product Vision Product Roadmap Agile Project Charter Product Scope Project Risks Release Deadlines Sprint Durations Team Norms Release Planning Release Plan Process Select Stories and a Release Date Product Backlog User stories Building the product backlog Product Backlog Refinement Transitioning to the Scrum Team

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

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?