Delve into Agile methodologies, compare them with Waterfall, explore planning techniques, and discover tools like SCRUM and Kanban. Gain insights into solving common problems with Agile.

This course is designed to help learners build an understanding of Agile’s process model and its different approaches and techniques.

To understand the advantages of implementing Agile techniques, the course begins with a comparison of Agile methods and the traditional Waterfall model. Then, you’ll get to know about different planning approaches to help users effectively adjust deadlines. Next, there’s a discussion on backlogs and different visual techniques, such as burn-down charts and burn-up charts, that help increase the efficiency of projects.

You will also learn Agile methodologies including SCRUM, eXtreme Programming, DSDM, Smart and Kanban, as well as the differences and similarities between these approaches. Finally, you’ll look at some common problems and learn ways to solve them using Agile methodologies.

Learn Agile Methodologies from Scratch

## Overview

Many organizations are moving from Waterfall to Agile for various reasons. That may be to deliver projects on time and within budget, to shorten the time-to-market, to increase productivity ,to be able to scale to larger or distributed projects, or to increase quality. Or, again, simply because the CEO heard someone from Gartner saying that Agile is great.

In all cases, the road will contain some hurdles. Sometimes very difficult ones. Remember that implementing Agile correctly isn’t easy. The organization isn’t always ready and possibly neither are the people in the organization. Although research shows that Agile projects are more likely to succeed than traditional projects, this doesn’t mean that all Agile projects will be successful.

There will also be Agile projects that won’t deliver what’s expected. Unfortunately, however, upon the failure or partial success of the first Agile projects, various organizations tend to move away from Agile very quickly. At one pension fund, we’ve even seen that the first Agile projects were highly successful, but the project managers returned to Waterfall for the next project simply because they were accustomed to it.


# Overview

Many organizations are moving from Waterfall to Agile for various reasons. That may be to deliver projects on time and within budget, to shorten the time-to-market, to increase productivity ,to be able to scale to larger or distributed projects, or to increase quality. Or, again, simply because the CEO heard someone from Gartner saying that Agile is great.

In all cases, the road will contain some hurdles. Sometimes very difficult ones. Remember that implementing Agile correctly isn’t easy. The organization isn’t always ready and possibly neither are the people in the organization. Although research shows that Agile projects are more likely to succeed than traditional projects, this doesn’t mean that all Agile projects will be successful.

There will also be Agile projects that won’t deliver what’s expected. Unfortunately, however, upon the failure or partial success of the first Agile projects, various organizations tend to move away from Agile very quickly. At one pension fund, we’ve even seen that the first Agile projects were highly successful, but the project managers returned to Waterfall for the next project simply because they were accustomed to it.


Let's discuss why to not get rid of Agile because of issues faced during implementing the Agile approach.


Replacing Favorable with Unfavorable

Let's discuss why to not get rid of Agile because of issues faced during implementing the Agile approach.

Getting Started

Why does the Waterfall Process model not work?

What is Agile?

Short Iterations in Agile

Collaboration in Teams

Collaborating Roles

Agile Requirements

Estimating

Planning

Implementing Agile

Issues in Using Agile

Choosing the Most Appropriate Process Model

Conclusion

Replacing Favorable with Unfavorable

Overview