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 for project planning

In our opinion, a good estimate for a reliable quote or a good one.
The project plan consists of the following four steps:

## Requirements gathering

   Set the preliminary requirements for the project for now because new requirements will emerge and existing requirements will change during the project. Always give an estimate with a margin at the start of a project. Note that the degree of uncertainty, and hence the margin, decreases during the project. There’s actually only one moment when the margin is zero. This is at the end of the project.

## Translate requirements into work items

   Convert the
collected requirements to work items in the selected
unit of estimation. For example, user stories, screens, or
smart use cases.

## Estimate work items

   Together with the intended team,
determine the total size and complexity of these work
items.

## Determine velocity

   Establish the people, hours and
duration of the project.

Once the requirements are converted into work items, the real work remains, estimating the size of work items in hours, or in points. It’s best to do this with the customer. In practice, this isn’t always possible, but when we can, it will provide the customer with a lot more confidence.

Translate the size into people, iterations, and duration. For this, we need the velocity of the intended team. Express this in the number of points per iteration and the number of hours or the price per item.


# Estimating in hours

Estimating work hours is tricky for the following reasons:

Get an idea about giving the best estimates of 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

Estimating in Steps

Steps for project planning

Requirements gathering