In this book, I show the agile patterns that I have observed via the narrative of Mike, a programmer who has struggled to deliver working software. After a major issue with a new deployment—that costs his company lots of money—leadership decides to rehire an employee named Tim. Tim is tasked with delivering new features while simultaneously installing agile. Along the way, both Mike and Tim are met with skeptics, difficult conversations, challenging software problems, and their own flaws, as they attempt to live out the values that are core to Extreme Programming.

Chapter Outline

Here is a list of the chapters only those marked draft have been started

A stumble (draft): The new subscription feature breaks in production

Warming up (draft 2): Tim is rehired, and shares the XP values

Joining a team (draft): Tim joins without changing their course

Reflecting (draft): The team assesses what isn't working by refocusing their retrospective on improvement

The Demo: stakeholders are given visibility into progress via a demo

The Starting line: The team is asked to rebuild the subscription feature

Planning the next lap: slicing stories, estimation, and setting a milestone

First steps: team starts on their project but makes little progress

Getting winded: The team rushes but discovers there are lots of defects

Setting a pace (draft): the team adds tests as a safety net

Finishing a lap: the team hits their milestone early

Resetting: planning for the next milestone

Losing the path (draft): after John leaves the team the team begins to pair

The finish line never arrives: the team ships an MVP of the subscription feature and learns that the race keeps going

As this book is in development feedback is vital, if you want to be part of that process then checkout the forum here: https://groups.google.com/forum/#!forum/agilesoftwarebook

Thank you for your interest in this book and happy reading

Steve