45335 PE courses

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

Microsoft Excel® in Depth (In-Person) This practical course provides a solid background of the features of Excel and a deeper understanding of its features, benefits and uses.This is not a beginner's course in Excel. You will learn some advanced features such as Pivot Tables, Charting, Tables, Sorting, Filtering and Functions. The goal of this course is to provide a deeper understanding of Excel and its intricacies and a new ability to use it efficiently producing the best solutions for your projects. What you will Learn You'll learn how to: Use functions like IF, AVERAGE, SUMIF, SUMIFS, SUMPRODUCT, INDEX, MATCH, CHOOSE, DATE, and many more Create meaningful charts Use pivot tables Use Conditional Formatting, Data Validation Take advantage of using Named ranges, do sorting, filtering, tables

Assuring Quality Through Acceptance Testing 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?

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

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

Recovering Troubled Projects 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

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

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