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)

No more bugs

Back in Chapter 8, Tightening Feedback Loops in the Software Development Life Cycle, we discussed how we tighten feedback loops from a variety of sources for us to ascertain two things:

  • Are we building the right thing?
  • Are we building the thing right?

Bug reports are a form of feedback that we should welcome, as they are the most straightforward problem detection system we could ask for. They cover many facets of our software, from a user requirement not being quite right to a broken API connection, from the user experience not being satisfactory to performance being suboptimal.

Some teams try to argue that a bug isn't, in fact, a bug. For example, they may say it's a case of the business requirement being wrong. Perhaps the user didn't know what they wanted. This is old-school contract thinking, which gets litigious because of the upfront promises...