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

Pair programming is a wonderful technique where two developers code together behind one computer. The developer who writes the code is the **driver**. The other, who watches and reviews the code while it’s written, is the **navigator**. They might switch roles at times too.

In terms of time spent, pair programming seems inefficient. Two pair programmers write code faster together than a single developer. Though faster, it’s still not more cost effective. To achieve that, the pair programmers would have to be twice as fast.


We still remember the first time we pair programmed. It was in 1997. We were one of the architects of a popular framework for PowerBuilder. One of the new concepts that we wanted to support was a domain layer. At the same time, we implemented the model-view-controller pattern. It was quite a challenge. We shut ourselves up in a tiny office and for three days, we scourged the keyboard of our laptop. We exchanged ideas and developed the solution quickly and relatively free of error. After three days, white smoke emerged from the room. Without this intensive form of pair programming, we would definitely have needed weeks to achieve the same result.

# Advantages of pair programming

Pair programming provides interesting advantages:

+ **Knowledge sharing**

  If two developers write code
together, they share knowledge about the code. When
regular pair programming is used, with varying pairs,
the knowledge of architecture and technology spreads
quickly across the team.

+ **Finding a solution faster**

  Code writing is a creative
process in which often several alternative solutions are
possible. In pair programming, alternatives are found
quickly and solutions are selected and tested faster.

+ **Unraveling complexity**

  When we develop complex code,
we prefer to do this with one of the other developers. Two
heads know more than one.

+ **Less code**

  Research and experience show that two developers who work together need less code for a solution than individual developers. Less code simply means fewer errors.


Get an overview of how pair programming works 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

Pair Programming

Overview

Advantages of pair programming