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

Projects are undertaken to realize customer’s requirements. These are elaborated upon in work items such as user stories, smart use cases, or features. These work items form the project’s backlog.

Just as in traditional projects, Agile requirements go through a number of stages in which different activities are carried out. In both types of projects, thought is given to the analysis, design, development, testing, and acceptance of the requirements. The greatest difference between traditional and Agile approaches is, therefore, not how the requirements are elaborated upon, but when they are elaborated upon.

We’ll compare the effectiveness of both approaches on the basis of a simple calculation.


# Requirements in a traditional project

A traditional project starts with the elaboration of the requirements until they are complete and thorough. Complete means that all requirements are elaborated. Thorough means that all required details have been described. Traditionally, this is done to create a sense of security because the requirements are the basis for estimating the project’s expected costs and duration. This elaborated set of requirements results in the project plan.

In a traditional method such as this, a lot of time is devoted very early in the project to the elaboration of the requirements. Now suppose that, in a given project, there are 100 requirements, and each requires 20 hours for elaboration. In total, the team burns 2,000 hours to elaborate the requirements.


Learn about the process of getting traditional requirements vs. agile requirements.

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

Traditional Requirements vs. Agile Requirements