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

## Steps to switch to Agile

Implementing Agile in an organization isn’t an easy feat. Its difficulty is often underestimated. The decision to switch to Agile is often met with skepticism or opposition in the workplace. Sometimes, Agile conflicts with the prevailing culture in an organization. Sometimes it’s better to implement Agile in an agile way, or bit by bit:

+ **Set the stakeholders and objectives:** It isn’t always clear why an organization would choose Agile. It’s then crucial to determine how Agile can be a success.
+ **Outline a method:** Create a rough sketch of the method for the first Agile project. Start with an approach like Scrum or Smart. Adjust gradually where needed.
+ **Select a unit of work:** Identify the unit of work that best fits the first project.
+ **Choose a promising pilot:** Always choose a promising project as the first Agile project. Don’t choose a project that has been restarted three times or that’s politically sensitive. Success in a first project is necessary to convince the skeptics.
+ **Coach the project:** Find an experienced Agile coach for this project. A coach with proven experience, not someone who just has a certificate.
+ **Compose the team:**
Ask people to be part of the team who already have experience with Agile or are open to try something new.
+ **Train the team:** Introduce the method chosen to the whole team, including customers and users. Explain very clearly what’s expected of everyone.
+ **Organize a kickoff:** Organize the kick-off for the project, preferably following the training.
+ **Improve by measuring:** Start by measuring productivity as soon as the project starts. Having historical figures early on in the project is one of the biggest advantages of Agile. Show what has been achieved and what this means for the duration of the project to everyone involved as soon as possible.
+ **Positive Energy:** Let the positive energy of the first Agile project spread through the organization. Contagious energy is the main method by which Agile spreads. Ventilate the achievements, and make them visible within the organization. That success is contagious. Soon, other projects and teams will take on elements of the first Agile project.

# Steps to switch to Agile

Implementing Agile in an organization isn’t an easy feat. Its difficulty is often underestimated. The decision to switch to Agile is often met with skepticism or opposition in the workplace. Sometimes, Agile conflicts with the prevailing culture in an organization. Sometimes it’s better to implement Agile in an agile way, or bit by bit:

+ **Set the stakeholders and objectives:** It isn’t always clear why an organization would choose Agile. It’s then crucial to determine how Agile can be a success.
+ **Outline a method:** Create a rough sketch of the method for the first Agile project. Start with an approach like Scrum or Smart. Adjust gradually where needed.
+ **Select a unit of work:** Identify the unit of work that best fits the first project.
+ **Choose a promising pilot:** Always choose a promising project as the first Agile project. Don’t choose a project that has been restarted three times or that’s politically sensitive. Success in a first project is necessary to convince the skeptics.
+ **Coach the project:** Find an experienced Agile coach for this project. A coach with proven experience, not someone who just has a certificate.
+ **Compose the team:**
Ask people to be part of the team who already have experience with Agile or are open to try something new.
+ **Train the team:** Introduce the method chosen to the whole team, including customers and users. Explain very clearly what’s expected of everyone.
+ **Organize a kickoff:** Organize the kick-off for the project, preferably following the training.
+ **Improve by measuring:** Start by measuring productivity as soon as the project starts. Having historical figures early on in the project is one of the biggest advantages of Agile. Show what has been achieved and what this means for the duration of the project to everyone involved as soon as possible.
+ **Positive Energy:** Let the positive energy of the first Agile project spread through the organization. Contagious energy is the main method by which Agile spreads. Ventilate the achievements, and make them visible within the organization. That success is contagious. Soon, other projects and teams will take on elements of the first Agile project.

Learn how organizations should switch to Agile step by step.

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

How to Switch to Agile

Steps to switch to Agile