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

## Collaboration in the Waterfall process model

Besides working in short iterations, there’s something else that differentiates Agile from Waterfall, and that’s the way people in different roles work together.

In Waterfall, roles are linked to phases. Analysts provide requirements. Designers create a functional and technical design. Developers translate this into code. Testers validate that the code implements the requirements. If the application is complete, it’s handed over to the maintenance team. Because all phases are performed only once, resulting in a final product which is called a milestone, it’s characteristic that all roles are performed sequentially. The transition between the different phases occurs when the final product is handed over to the people who perform the role of the next phase.




# Collaboration in the Waterfall process model

Besides working in short iterations, there’s something else that differentiates Agile from Waterfall, and that’s the way people in different roles work together.

In Waterfall, roles are linked to phases. Analysts provide requirements. Designers create a functional and technical design. Developers translate this into code. Testers validate that the code implements the requirements. If the application is complete, it’s handed over to the maintenance team. Because all phases are performed only once, resulting in a final product which is called a milestone, it’s characteristic that all roles are performed sequentially. The transition between the different phases occurs when the final product is handed over to the people who perform the role of the next phase.




Get an overview of collaborations in the Waterfall and Agile process models.


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

Collaborating in Agile Projects

Collaboration in the Waterfall process model