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)

Estimating Agile user requirements

We briefly introduced the concept of relative sizing in Chapter 3, Introducing Scrum to Your Software Team, in the activity Using estimate buckets to size User Stories. This particular technique is useful for sizing a bunch of User Stories at once. It also makes the concept of relative sizing slightly more obvious because we're comparing User Stories to one another. Relative sizing in this setting is a simple question of "Is it bigger, smaller, or is it the same size?"

You're probably wondering why we use relative sizing for estimating, rather than time-based sizing such as hours, days, or weeks. Take a look at the following skyline, you might recognize it:

Photo credit:

There is an arrow pointing to the tallest building in this picture. Resist the temptation to look this up and have a guess at how...