This lecture is designed to provide an in-depth understanding of how the history of Agile evolved and some of the forces and factors that contributed to that history and led to the evolution of the Agile Manifesto Values in 2001.

This lecture is designed to provide an in-depth discussion of the Agile Manifesto Principles and how they're applied in a typical real world project

This lecture is designed to provide an overview of Scrum as well as an understanding of the responsibilities of the roles in a Scrum project to provide a foundation for understanding the methodology in more detail in the next lecture.

This lecture is designed to provide an in-depth understanding of the Scrum methodology and practices to enable an Agile Project Manager to effectively design and manage highly effective projects based on Scrum.

One of the most important factors in enabling high-performance teams is that everyone on the team commits to a set of values that guide the way they work. This lecture is focused on understanding the values behind Scrum that are essential to enable high-performance teams

One of the most fundamental differences between an Agile approach and a plan-driven approach is the difference between a plan-driven approach is the difference between a defined process control model and an empirical process control model. An understanding of this difference provides a new perspective to objectively understand "Agile versus Waterfall". The difference between a defined process control model and an empirical process control model is very much related to the management of uncertainty and this lesson also includes some material on that topic as well.

The "Iron Triangle" has been a core concept of traditional plan-driven project management practice for as long as I can remember. It is based on managing the scope of a project and the fundamental relationships between cost, schedule, and scope. Those fundamental relationships are still useful to understand but Agile has turned that triangle upside down to put a much higher level of focus on customer value. An understanding o this difference is critical to understand the fundamental differences between an Agile and plan-driven approach.

This lecture is designed to provide an understanding of “Systems Thinking” which is essential to see beyond the “mechanics” of an Agile Project Management process and see how the process fits together and fits with the business environment it is part of

I have to admit that I didn't know much about "Complex Adaptive Systems" until several years ago when I saw a question on the PMI-ACP exam; but once I learned about it, it was an "aha" moment for me. When I understood Complex Adaptive Systems, my reaction was that "these systems have been right in front us since the beginning of time yet we are only beginning to learn how to mimic the simple, yet highly-effective behavior they embody. Complex Adaptive Systems are all around us in the real world in things as simple and commonplace as an anthill and we can learn a lot from the way they operate that is directly applicable to an Agile Project Management approach.

Many of the Agile principles related to quality have their roots in the philosophy of Total Quality Management (TQM). The TQM philosophy originated from the ideas of W. Edwards Deming and others. Dr. Deming was an American statistician who was credited with the rise of Japan as a manufacturing nation. His principles transformed the Japanese automotive industry into developing very high quality products that gained significant market share against American automotive manufacturers in the 1970's and 1980's

Where TQM provides a foundation of how to integrate quality into the design of products, lean manufacturing principles complement and go beyond that by developing a stronger focus on maximizing customer value and providing guidance on how to improve and streamline processes to eliminate wasteful inefficiencies

This lecture is the first in a series of three lectures based on Advanced Agile/Scrum principles as identified by Ken Rubin. This particular lecture will discuss principles related to the areas of “Variability and Uncertainty” and “Prediction and Adaptation”

This lecture is the second in a series of three lectures based on Advanced Agile/Scrum principles as identified by Ken Rubin. This particular lecture will discuss principles related to the areas of “Variability and Uncertainty” and “Prediction and Adaptation”

This lecture is the third in a series of three lectures based on Advanced Agile/Scrum principles as identified by Ken Rubin. This particular lecture will discuss principles related to the areas of “Variability and Uncertainty” and “Prediction and Adaptation”

This is part 1 of a two part lesson on an example Scrum project