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

## Overview

To perform a project successfully in an Agile way, it’s crucial to determine how the project will be a success. As in any project, an inventory of stakeholders and objectives is indispensable. Who planted the seed? Who’s involved? Who in the organization is affected by which benefits and consequences? How large are these? So, map all the parties involved, including the stakeholders. 

+ **Team:** For people on the project team, such as project managers, architects, domain experts, developers and testers, the work changes immediately when we shift to Agile.

+ **Maintenance:** Agile projects deliver new or changed products. Therefore, the people who are responsible for maintaining the realized software are stakeholders.

+ **Other parties:** Often, a team is dependent on external parties or other projects that work in the traditional way.
+ **Recruitment:** A project can hire people from external suppliers, educated in Agile or not.
+ **Human resources:** Sometimes, it’s better to start rewarding team performance instead of individual performance. We may want to change the way project and team recruitment is organized.
+ **Sales:** There  might be several types of contracts that other organizations adopt to develop products in an Agile way because the products can be delivered in much smaller releases.

+ **Customer:** Last but not the least, Agile has benefits and consequences for the customer, as the recipient of the produced software.

For all these stakeholders, their involvement in an Agile project is more regular and direct than in a traditional project. Take stock of the goals the stakeholders are trying to achieve when implementing Agile. Which expectations do people have where Agile is concerned? How can the success of Agile be measured by quantifying goals?


# Overview

To perform a project successfully in an Agile way, it’s crucial to determine how the project will be a success. As in any project, an inventory of stakeholders and objectives is indispensable. Who planted the seed? Who’s involved? Who in the organization is affected by which benefits and consequences? How large are these? So, map all the parties involved, including the stakeholders. 

+ **Team:** For people on the project team, such as project managers, architects, domain experts, developers and testers, the work changes immediately when we shift to Agile.

+ **Maintenance:** Agile projects deliver new or changed products. Therefore, the people who are responsible for maintaining the realized software are stakeholders.

Learn about the roles of customers as stakeholders in Agile.

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

Stakeholders: Customers

Overview