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 pitfalls of traditional big upfront requirements

In Chapter 1, The Software Industry and the Agile Manifesto, we took a look at some of the issues that the software industry faced prior to the Manifesto for Agile Software Development and the formation of the Agile Alliance in 2001.

The main issues we saw were related to attempts to control projects through predictive planning, an approach which requires gathering all requirements up front so that a detailed estimate can be made to determine project costs and timelines.

Business Analysts (BAs) often write traditional requirements documents and carry out the analysis work as well, either simultaneously or as a subsequent phase.

A traditional requirements document might contain the following:

  • Use case diagrams
  • Sequence diagrams describing events and the flow of information
  • Data models detailing data and rules
  • User Experience...