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

## Evaluation in Waterfall vs. Agile

When we explain the differences between Waterfall and Agile, we invariably ask the following question: who attended the final evaluation of your previous project? The final evaluation is an interesting phenomenon.

Besides the celebrations, the final evaluation of the project itself is pointless. The aim of an evaluation is to learn from the project and improve the next time around. However, in this field, we’re very obstinate. Despite final evaluations, we tend to repeat the same mistakes in future projects.


## Benefits of frequent evaluations in Agile

This is different in Agile. In Agile, an evaluation is performed at the end of each iteration. This takes more time, but also has a greater effect. Improvements identified during a second iteration benefit the team from the third iteration. Agile projects are learning projects.

# Evaluation in Waterfall vs. Agile

When we explain the differences between Waterfall and Agile, we invariably ask the following question: who attended the final evaluation of your previous project? The final evaluation is an interesting phenomenon.

Besides the celebrations, the final evaluation of the project itself is pointless. The aim of an evaluation is to learn from the project and improve the next time around. However, in this field, we’re very obstinate. Despite final evaluations, we tend to repeat the same mistakes in future projects.


# Benefits of frequent evaluations in Agile

This is different in Agile. In Agile, an evaluation is performed at the end of each iteration. This takes more time, but also has a greater effect. Improvements identified during a second iteration benefit the team from the third iteration. Agile projects are learning projects.

Get an overview of the evaluation in Agile and Waterfall projects.


The Evaluation of Iteration

Get an overview of the evaluation in Agile and Waterfall projects.

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

The Evaluation of Iteration

Evaluation in Waterfall vs. Agile

Benefits of frequent evaluations in Agile