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

# Why does Waterfall still exist?

The question remains, why is the Waterfall model still used? Some major reasons are as follows:

+ It’s a simple model that’s easy to explain.
+ It gives the illusion of predictability and measurability.
+ Project managers often envisage a Gantt chart in the model to plan their project. 
+ Holding on to what we know, successful or not, is in our nature.




In the end, projects often appear to be successful because the end result is no longer compared to the original objectives and budget.


In fact, the Waterfall model is a copy of similar models in other industries used for repeated production, such as the automotive industry. Software development, however, can hardly be compared with repeated production. Unlike the continual production of the same automobile, software development requires a high degree of creativity.

Decisions are continually being made that influence outcomes, even during software development and testing. The production metaphor doesn’t hold. A better metaphor from such industries would be that of the development of a new type of car.

These disadvantages of the Waterfall are sufficient to conclude that the model doesn’t work. Abundant research supports this conclusion. Project managers who indicate that their Waterfall projects are going well are the proverbial exception to the rule. They usually don’t compare the outcome of the project with the original budget or have adjusted the method to minimize these disadvantages.

# From Waterfall to iterative

Remarkably, Winston Royce already came to the conclusion that Waterfall doesn’t work in 1970. In his paper, he used this model to show how not to organize projects. Royce is in favor of a do it twice approach. The software is analyzed in small increments, designed, developed, tested, and delivered. The developers continuously incorporate feedback from each activity to improve previous milestones. Therefore, if the development process shows that the design should be improved, it’s done immediately.

Learn to move from a Waterfall to an iterative model.

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

From Traditional to Agile Processes

Why does Waterfall still exist?