Book Image

The Agile Developer's Handbook

By : Paul Flewelling
Book Image

The Agile Developer's Handbook

By: Paul Flewelling

Overview of this book

This book will help you overcome the common challenges you’ll face when transforming your working practices from waterfall to Agile. Each chapter builds on the last, starting with easy-to-grasp ways to get going with Agile. Next you’ll see how to choose the right Agile framework for your organization. Moving on, you’ll implement systematic product delivery and measure and report progress with visualization. Then you’ll learn how to create high performing teams, develop people in Agile, manage in Agile, and perform distributed Agile and collaborative governance. At the end of the book, you’ll discover how Agile will help your company progressively deliver software to customers, increase customer satisfaction, and improve the level of efficiency in software development teams.
Table of Contents (16 chapters)


The aim of the team liftoff is to launch our team on its mission as quickly as possible. To do this, we first need to have context; we need to understand our product and its purpose and how it fits in with the company's goal.

Knowing this background helps us better understand the business problem we're trying to solve. It means we will be much more able to make better design and implementation decisions. For example, is this a standalone solution, or does it fit into a wider ecosystem?

The second part of the liftoff is deciding how best to solve this problem together. This gives our team an operating manual/system, which includes our team's technical process (definition of done) and social contract (working agreement). Both of these help us remove any assumptions on how we're going to work with each other.

For a team transitioning to Agile, this should...