This section discusses the reasoning, the formation, and the problems Dr. Jeff Sutherland sees before the creation of the Agile Manifesto in 2001, the problem the 17 Agile gurus are trying to solve with the creation of Agile. We also talk about the formation of Scrum, its core design principles and how could we use Scrum to generate work impact. You’ll complete this section with a deep understanding of the Agile movement, Scrum, and its core principles. You’ll be able to identify projects and places where Scrum can be applied

This section discusses the transition from traditional management to Agile Management. We’ll start by exploring the 3 roles defined in Scrum, their design logic, and how the 3 roles collaborate to form a high-performance work system. We’ll use multimedia and a highly interactive learning system to discuss the business value and product creation from the perspective of the stakeholders, Business Owners, and Product Owners. We’ll also explore several key Agile Product creation concepts and important techniques in Scrum Mastering. This section also adds many practical Scrum knowledge for being a good Scrum Master and Product Owner.

This section discusses the changes in the format of communication from traditional PRD to a product backlog, the what, the whys, and the transition process. We begin by understanding the theory and logic behind this transition. We follow by a hands-on workshop on how to create a good product backlog, how to structure its content, and how to do prioritization. Advanced topics from the Product Owner perspective including analyzing business values, projects, and portfolios will be explored. You’ll complete this section with a solid understanding of this process, and will be able to create a good product backlog. You’ll also learn to create a good product from the perspective of the customer journey and will be able to organize the backlog into several releases.

After having a good product backlog, we are able to start the Scrum work cycles. In this section, we discuss the work cycle in detail, including the logic, the design, how it is created, and how to do a good job running it. We will also explore several important “Scrum Patterns” – best practices given a situation – designed by Dr. Jeff Sutherland and the magnificent Jim Coplien after 25 years of implementing Scrum

We could run a Scrum team any way we like. However, if we want to run a good, hyper-productive Scrum team, we need to understand the key Lean concept behind Dr. Jeff Sutherland’s design. We’ll explore Value Stream Mapping, Root Causing Analysis, and the key lean problem-solving techniques Dr. Jeff Sutherland observed at Toyota and is now educating every Scrum Master and team leader of it. At last, we learn about de-scaling. The utmost important concept to master before advancing to a multi-team implementation environment.

What are organizations often good at implementing Scrum in a single team environment but often struggle to deliver the same efficiency in a multiteam environment or at the organizational level? This section summarizes Dr. Jeff Sutherland’s observation and experience at some of the best companies in the world, the impediments and difficulty as he sees it, and introduce the solution Dr. Jeff Sutherland has created to solve this problem. You’ll complete this section with a good understanding of Scaling and the introductory knowledge of the important “Scrum At Scale” framework.