Earn PDU's: Students who complete this course are eligible to receive 4.5 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.
Learn how to apply project management practices in an Agile environment!
The concept of Agile Project Management is very rapidly evolving and will have a significant impact on the project management profession; however, we are in the early stages of that transformation and there is a lot of confusion about what impact it has on project managers. This course will help you unravel a lot of the confusion that exists; develop a totally new perspective to see both Agile and traditional project management principles and practices in a new light as complementary to each other rather than competitive; and learn to develop an adaptive approach to project management to blend those principles and practices together in the right proportions to fit any situation.
This course is part of an overall curriculum that is designed around helping students develop the skills required for a high-impact Agile Project Management role. Most students will want to take the complete curriculum rather than individual courses. The complete curriculum should be taken in the following order:
In this lecture, we will do a brief recap of some key points from the "Learn the Truth About Agile versus Waterfall" course that are essential to making further progress in this course and cover some of the key benefits of adopting a more Agile or adaptive project management approach.
Brief review of topics related to the lecture on "Agile versus Waterfall Recap"
Agile has huge potential benefits but it is not a solution to every problem. Learning to choose the right approach to fit a project can be a difficult decision and it is often not a simple, binary either-or decision between Agile and Waterfall. Many times it requires a blend of those two approaches to fit a given situation.
In this lecture, we'll discuss a couple of examples of why an Agile (or adaptive) approach makes the most sense in some situations and a Waterfall (or plan-driven) approach makes more sense in other situations. Many times it is not a binary choice between two extremes and requires blending an approach to fit the situation.
The key point is that rather than force-fitting a project to some kind of canned, “textbook” methodology, a better solution is to go in the other direction and fit the methodology (or combination of methodologies) to the project. It takes more skill to do that – it requires knowledge of a broader range of methodologies and a deeper understanding of the principles behind the methodologies to know how to blend them together to fit a given situation.
This quiz is based on choosing the best approach for some selected project scenarios
In order to develop a new way of thinking about Agile Project Management, it is important to understand some of the popular stereotypes that exist about traditional project management and Agile (some of those stereotypes are either real or imagined). In this lecture, we will discuss what some of those stereotypes are so that we can make a conscious effort to overcome them in developing new ways of thinking.
Brief review of topics related to "Popular Project Management and Agile Stereotypes"
In this lecture, we will discuss some of the fundamental differences in an Agile Project Management role
This quiz provides a brief review of some of the topics related to the "What's Really Different about Agile Project Management" lecture
This lecture consists of a self-evaluation tool for a project manager to use to evaluate to what extent some project management stereotypes apply to themselves and to what extent that behavior is expected of them by their organization.
In this lesson, we’re going to talk about “Kanban” which is another widely used Agile process in addition to Scrum. Where Scrum is used heavily for project and product development efforts that require some level of planning, Kanban as a process is generally more suited for continuous flow kinds of operations. However, the principles associated with flow and Kanban are essential to Scrum.
Where traditional, plan-driven projects focus heavily on structure with Work Breakdown Structures, Pert Charts, etc., Agile projects focus much more heavily on "flow". This lecture discusses the Principles of Product Development Flow and the Theory of Constraints for optimizing the flow of an Agile project.
This quiz is a brief review of topics related to the lecture on Product Development Flow and The Theory of Constraints
Kanban boards are a widely used Agile tool for visualizing the flow of work in an Agile process.
Cumulative Flow Diagrams provide an important visual tool for analyzing process flow and improving the efficiency of flow in an Agile process.
Lean Software Development is based on applying the principles originally developed in Lean Manufacturing to software development. The primary emphasis in Lean Manufacturing is on reducing waste in a manufacturing process to ultimately improve the efficiency of the process and reduce production costs.
The concept of Lean Software Development originated from a popular book by Tom and Mary Poppendieck in which they have showed how to apply the original Lean Manufacturing principles that we have previously discussed to software development.
Lean Software Development is not widely used as a standalone methodology; however, the principles behind it are a foundation for all Agile methodologies including Scrum.
The value stream is the entire collection of activities necessary to produce and deliver a product or service. Value stream analysis separates those activities that contribute to value creation from activities that create waste, and identifies opportunities for improvement.
This topic is very much related to the area of Lean Software Development because you would use a value-stream analysis to go through an entire process and identify the portions that provide value and the portions that do not produce value and could be trimmed or eliminated.
The idea of a value stream analysis originated in a manufacturing environment with Lean Manufacturing and the general concept can also be applied to a software development environment.
This quiz is a brief recap of some of the more important topics related to Lean Software Development and Value Stream Analysis
This lecture provides an overview of what "value-driven delivery" is and why it is important.
This lecture provides an overview of the key principles behind value-driven delivery.
This lecture is part 1 of 4 parts on Customer-value Prioritization. This lecture is focused on providing an overview of what customer-value prioritization is, why it is so difficult, and some of the factors to consider in customer-value prioritization.
This lecture is part 2 of 4 parts on Customer-value Prioritization. This lecture is focused on Pareto Rule, Pareto Analysis, Minimum Viable Product, Minimum Marketable Feature, and MoSCoW prioritization
This lecture is part 3 of 4 parts on Customer-value Prioritization. This lecture is focused on the Kano Model
This lecture is part 4 of 4 parts on Customer-value Prioritization. This lecture is focused on the Relative Weighing Model
This lecture provides an overview of Agile Business Case Development and how it is different from a traditional plan-driven environment.
This quiz is a brief review of topics related to "Value-driven Delivery"
This lecture provides an overview of "Rolling Wave Planning"
This lecture is part 1 of 5 parts on "Agile Planning Practices and Tools". This particular lecture is focused on developing a Product/Project Vision.
This lecture is part 2 of 5 parts on "Agile Planning Practices and Tools". This particcular lecture is focused on developing a Product/Project Vision.
This lecture is part 3 of 5 parts on "Agile Planning Practices and Tools". This particcular lecture is focused on doing an "Exploratory 360 Assessment".
This lecture is part 4 of 5 parts on "Agile Planning Practices and Tools". This particular lecture is focused on "Functional Decomposition".
This lecture is part 5 of 5 parts on "Agile Planning Practices and Tools". This particular lecture is focused on developing a Project Charter for an Agile project.
This lecture provides an overview of how "Progressive Elaboration" and "Multi-level Planning" are implemented in an Agile environment.
This quiz is a brief review of topics from the section on "Adaptive Planning"
This lecture discusses best practices for Agile Requirements
This lecture discusses the normal Business Analysis functions in a typical plan-driven project and the potential roles that aa Business Analyst might play in an Agile environment.
This lecture discusses the concept of "User Personas" in Agile.
This lecture discusses user stories, the characteristics of well-written user stories, and provides some examples of typical Agile user stories.
This lecture is focused on how to develop a very well-organized and hierarchical structure of requirements using epics and themes.
This lecture discusses how a Product Backlog is used to capture requirements in an Agile project and how a Product Backlog Grooming process works to continuously refine and further define the Product Backlog in a typical Agile project as the project is in progress.
This lecture discusses "Story Mapping" and how it can be used to plan and organize project requirements for an Agile project.
This quiz is a brief review of topics related to the Agile Requirements Definition Practices Lecture
This lecture provides an example of a real-world case study that illustrates the value of an Agile Project Management approach.
In this lecture we will provide a wrap-up of the major points that have been covered in this course. We will also discuss some of the resources that are available for further developing and implementing the ideas in this course
Please download the attached document on "Instructions for Claiming PDU's" for instructions on how to claim PDU's for this course.
Chuck Cobb is the author of the recent, 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 instructors on Udemy with over 30,000 students and over 1,500 5-star reviews and 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 understand the convergence of Agile and traditional project management principles and practices.