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

# Effects of mono-disciplinary teams


Most organizations that implement Agile start with a small pilot. Because the team is small, it rarely has more than one or two people in the same discipline, let’s say a domain expert, two developers, and a tester. In this composition, it’s only natural for multidisciplinary collaboration to take place. But, as the Agile implementation proceeds, the Agile project becomes bigger. Suddenly, the team consists of several subteams: two architects, four designers, five .NET developers, four COBOL developers, and four testers. Each has their own stand-ups.

Now, the tendency kicks in to split the team the way they always did, per discipline, especially if the project manager has a traditional background. This has unpleasant side effects. Mono-disciplinary teams have a negative effect on collaboration. Moreover, transfer moments arise again within the team. Like  a designer once said, “You won’t get the design of this transaction until it is completely ready.” The fact that individual disciplines are better able to focus on their work is used as an argument. This may be true, but it also hampers crucial communication and collaboration between the different roles.


Get an idea of how mono-disciplinary teams negatively impact an Agile project.

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

Mono-disciplinary Teams

Effects of mono-disciplinary teams