Coherence vs. Standardization
It was only a few weeks to the scheduled release date of a new version of the software. Final release testing was running behind because the production-like environment needed had been in use by others. To make up for lost time, everybody was going to test: release testers, testers embedded on the development teams, programmers, analysts, team managers…everybody. Everybody set to organizing the work together.
A small group gathered around a whiteboard planning how to handle the issues that were noticed. They labeled columns for “identified” and “in progress”, then quickly inserted a column for “in triage” between them. They finished with columns for “resolved” and “backlog” for the end states of all issues. It was amazing watching them develop their bug-tracking strategy in under 60 seconds.
The release manager looked up at the board and asked, “Has this been standardized across all the teams?” I chuckled to myself. Of course it hadn’t, having been just now invented. People rushed off to share the Official Standard Triage Board with the other teams…
Allowing experimentation that drives improvements
During the next few days, I noticed that while every team had a board that looked the same, they seemed to be using them in slightly different ways. On some boards, issue
Please login or register below to read the rest of the article.