Agile Software Development

What is Project Management?

And why do we need it?

Traditional Project Management...

• Planned up front
• All features are developed from the start
• Tested at the end
• Shipped to the customer

"Waterfall"

What happens when...

• You only get 80% of that done?
• Something changes?

What if you did this:

• Planned the features that you were working on now
• Built and tested them
• Shipped them to the customer frequently

Agile

What happens when...

• You only get 80% of that done?
• Something changes?

Welcome to Agile

The 12 Principles

Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.

The 12 Principles

Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.

The 12 Principles

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

The 12 Principles

Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.

The 12 Principles

Business people and developers must work together daily throughout the project.

The 12 Principles

Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.

The 12 Principles

The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.

The 12 Principles

Working software is the primary measure of progress.

The 12 Principles

Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.

The 12 Principles

Continuous attention to technical excellence and good design enhances agility.

The 12 Principles

Simplicity--the art of maximizing the amount of work not done--is essential.

The 12 Principles

The best architectures, requirements, and designs emerge from self-organizing teams.

The 12 Principles

The best architectures, requirements, and designs emerge from self-organizing teams.

The 12 Principles

At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.