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)

What a User Story is and how to use it

User Stories are short but well-formed descriptions of some new feature or functionality told from the perspective of the person who needs it.

We write requirements like this to encourage us to think of the actual people that we're making something for; it helps us focus on the value that we're trying to create for them.

The User Story format

The following figure shows an example User Story that you may recognize from earlier in the book. There are three sections to it, shown as follows:

The basic template we're using for this User Story is:

  • As an <actor> I want <some action> so that I get <some value>

We can either define the actor as an actual person...