How Our Process Worked

We kept making new discoveries about how things really worked, what processes we actually wanted, and how we should communicate the changes to everyone involved. We were constantly in a state of flux for the better. We even found ourselves changing our processes at least once a week.

We wanted to improve our testing and address the imbalance between our development and testing throughput. We looked at test-driven development (TDD) to help us be smarter with manual testing, decrease regression testing overhead, and give us readable code. Our team members came in an hour early for four mornings to attend TDD training workshops. Because the goal of these sessions was to make the team feel confident that they could change ...

Get Real-World Kanban now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.