- Over 125,000 students in my courses!
- Over 7,000 5-star reviews in my courses!
Earn PDU's: Students who complete this course are eligible to receive 6.0 PDU's in PMI continuing education credits. Instructions for claiming PDU's are provided with the last lesson in the course.
Money-back Guaranty: Try this course and if you are not satisfied with the value you received from the course, just send an email to Udemy support and they will give you a 100% refund within 30 days.
Intended Audience: The primary audience for this course is Agile/Scrum Product Owners who are responsible for leading Agile Projects from a business perspective. The Product Owner role in Agile is a very demanding role. The Product Owner in Agile is the role primarily responsible for the success or failure of the project from a business perspective and is often known as "The CEO of the project". Many existting courses for Product Owners such as Certified Scrum Product Owner (CSPO) are primarily focused on the basic "mechanics" of how to do Scrum. This course goes well beyond that to provide a much deeper understanding of how to be an effective Agile Product Owner.
In addition to the Product Owner role, this course will also appeal to:
- Business Analysts - who work in an Agile environment and need to optimize their skills to provide a high level of value in that environment
- Business Sponsors - who want to learn more about Agile Project Management in order to provide more effective leadership for the initiatives that they are responsible for
This course is designed to provide a much deeper understanding of how to effectively lead Agile/Scrum projects for anyone in a Product Owner role or in an equivalent level of business responsibility. The Product Owner role in Agile is not well understood and many business managers who are assigned to perform that role are not well-prepared for it. This course includes material on:
- Agile Values and Principles
- Design Thinking, Systems Thinking, and Complex Adaptive Systems
- Kanban and Managing Flow in Agile Projects
- Lean Software Development, Value Stream Analysis, and Value-driven Delivery
- Adaptive Planning and Agile Requirements Definition Practices
- Agile Risk Management, Metrcis, and Stakeholder Management
Overall Agile Business Management Curriculum:
This course is part of an overall curriculum designed for business people to effectively participate and lead in an Agile environment. Agile significantly changes the role of business people in leading and managing projects and requires a much more active business leadership role to guide the direction of projects that are in progress. The overall curriculum consists of three primary courses:
1. Agile BM 101 - Introduction to Agile Business Management
This course povides a solid foundation for the other courses in this overall curriculum and helps all business personnel develop a solid understanding of how to implement a hybrid approach that blends the two approaches in the right proportions to fit any given situation
2. Agile BM 201 - Mastering Agile Business Management (this course)
This course is designed to provide a much deeper understanding of how to effectively lead Agile/Scrum projects for anyone in a Product Owner role or in an equivalent level of business responsibility. The Product Owner role in Agile is not well understood and many business managers who are assigned to perform that role are not well-prepared for it.
3. Agile BM 301 - Enterprise-level Agile Business Management
The final course in this series is focused on advanced topics related to applying Agile to a business at an enterprise level including
- Alignment and Value Disciplines
- Enterprise-level frameworks (SAFe and DAD)
- Enterprise-level Agile Transformations
- Organizational Culture and Change Management
Why Is This Curriculum Important?
In a traditional, plan-driven project management environment,
- A large part of the management of a project can be delegated to a project manager, and
- Once the business requirements for the project are documented and approved by the business, the business role in providing leadership and management of the project can be limited.
In an Agile environment,
- The requirements and the design of the solution evolve and are further refined as the project progresses
- For that reason, it is essential that the business is much more directly involved in providing leadership and direction to the project as it progresses
In order to provide effective leadership and direction to projects, the business people who are either directly or indirectly involved in Agile projects need to fully understand how the process works in order to participate collaboratively in the process with the project teams who are responsible for developing the solution.
Many existing courses for business people in an Agile environment such as Certified Scrum Product Owner (CSPO) are limited to the "mechanics" of how to do Agile and are limited to a pure Agile approach. This course goes into much more depth to give business people a very solid and deeper understanding of both Agile/Scrum as well as traditional plan-driven project management and how to successfully apply it in a business environment.
Important Note: This course is a condensed version of some of the material in our 7-course curriculum for Agile Project Managers and there is no need for anyone to take both sets of courses.
What Students Are Saying About This Course:
- "As a senior project manager that deals with executives and their project management "likes and dislikes" on a daily basis I found this overview spot-on. From lecture 1 through 7 Chuck addresses most of the issues that I quite often experience in getting executive to understand the "symbiotic" relationship between Agile and Plan-driven project management. This course is for project managers and executives alike, and after completion you'll have a clear understanding of how Agile and traditional plan-driven approaches can be complementary rather than competitive."
- "Chuck Cobb's presentation Agile Project Management Overview for Executives was informative. I found the course helped reveal misconceptions and stereotypes regarding Agile Project Management. In his instructional course, he helps break down key differences between agile and waterfall project management. He outlines the benefits of agile project management. He once again clearly and concisely communicates in a way that is easy to follow. I look forward to following additional courses in the future."
"Chuck provides a solid understanding of the potential relationship between diametrically opposed project management/development methodologies, and seeks to convince people that a binary choice of methodology is not necessary."
- "Introducing or integrating Agile within an established enterprise can be challenging on many fronts. This course provides a clear, well organized and engaging discussion of some alternative approaches to integrating Agile, including case studies on what does and does not work!"
Chuck Cobb is the author of the best-selling book "The Project Manager's Guide to Mastering Agile" as well as four other books on Agile Project Management and Business Excellence and he is one of the most popular and well-known instructors in the area of Agile Project Management with over 90,000 students and over 5,000 5-star reviews. He has been a featured speaker at a number of PMI Chapter events, agile groups universities, and PMO workshops throughout the US.
He has a very pragmatic, "real world" approach to Agile that is based on over 20 years of hands-on program/project management experience in a broad range of industries and application areas and he is passionate about helping Project Managers and Business Managers understand the convergence of Agile and traditional project management principles and practices.
He has been an Adjunct Professor at Boston University and many of his courses originated from a graduate-level Agile Project Management curriculum he originally developed for Boston University.
- "Presents business side of agile transformation clearly"
- "Chuck provides a solid understanding of the potential relationship between diametrically opposed project management/development methodologies, and seeks to convince people that a binary choice of methodology is not necessary."