It is a little world
- Cubed
In the 1960s, the designer Robert Propst worked with the Herman Miller company to produce “The Action Office”, a stylish system of open-plan office furniture that allowed workers to sit, stand, move around and configure the space as they wished.
Propst then watched in horror as his ideas were corrupted into cheap modular dividers, and then to cubicle farms or, as Propst described them, “barren, rathole places”. Managers had squeezed the style and the space out of the action office, but above all they had squeezed the ability of workers to make choices about the place where they spent much of their waking lives.
...It should be easy for the office to provide a vastly superior working environment to the home, because it is designed and equipped with work in mind. Few people can afford the space for a well-designed, well-specified home office. Many are reduced to perching on a bed or coffee table. And yet at home, nobody will rearrange the posters on your wall, and nobody will sneer about your “dog pictures, or whatever”. That seems trivial, but it is not.
The brick is one of those old technologies, like the wheel or paper, that seem to be basically unimprovable. ‘The shapes and sizes of bricks do not differ greatly wherever they are made,’ writes Edward Dobson in the fourteenth edition of his Rudimentary Treatise on the Manufacture of Bricks and Tiles. There’s a simple reason for the size: it has to fit in a human hand. As for the shape, building is much more straightforward if the width is half the length.
The Agile Manifesto is an immune response on the part of programmers to bad management.
I want you to consider instead the possibility that Waterfall came to exist, and continues to exist, for the convenience of managers: people whose methods are inherited from military and civil engineering, and who, more than anything else, need you to promise them something specific, and then deliver exactly what you promised them, when you promised you’d deliver it. There exists many a corner office whose occupant, if forced to choose, will take an absence of surprises over a substantive outcome.
Features don’t work, in the sense that they can be easily gamed. A brittle and perfunctory implementation, done quickly, is going to score more intramural brownie points over a robust and complete one. If the question is "does product
A
have featureX
?" then the answer is yes either way.
We use the term feature factory as a pejorative to designate companies addicted to adding features, while accumulating incalculable so-called technical debt. This situation is driven by management for the convenience of marketing, and I am skeptical that a more faithful application of Agile principles will correct it. Indeed, I suspect Agile processes are constitutionally vulnerable to this kind of compromise.
The presence of a feature can only indicate to a user if a goal is possible, behavior will determine how painful it will be to achieve it.