Rules That Were Supposed to Help But Ended up a Big Fail
Credit: freepik
Breaking the Code
I’m a programmer. In a previous job, the developers and teams were measured by the number of feature requests they completed.
We figured out to subdivide everything to blow it up into the maximum number of feature requests possible. A manager might request a new report. We’d set up separate feature tickets for “create button,” “make button blue,” “make button respond when clicked,” “implement business logic,” “display results in a grid,” “allow sorting of the grid,” and so on. We’d subdivide a 1-day task into 20 one-hour tasks.
Management loved it! Our team looked twenty times as productive, despite deliberately slowing ourselves down with red tape.
