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)

Starting a new Scrum team

A word about time-boxes before we start: all Scrum events are time-boxed. For those that are formally part of the Scrum framework, their time-box recommendations are in the Scrum Guide (

All other activities or events that we introduce, such as Product Backlog refinement, should also be time-boxed. For these time-boxes, the facilitator of the event should estimate how long they think they need. They declare the time-box at the beginning of the event as part of the setup.

If you hit the time-box and you still have work to do, you can ask the team what they would like to do. Should they carry on, and if so, for how long? Should they reconvene at another time, perhaps?

Remember, meeting fatigue is a real thing, and people may have other commitments. Finding out if they can commit more time to extending the time-box is only polite...