4 ms·
I always liked Allen Ward's take on this. In his view, developers have two[1] forms of value-added work: - Creating schematics for manufacturing[2], and - Cap
by kqr 5y ago
I always liked Allen Ward's take on this. In his view, developers have two[1] forms of value-added work:
- Creating schematics for manufacturing[2], and
- Capturing reusable knowledge.
What's interesting is that these two may be thought of as in opposition. Time spend creating reusable knowledge does not directly benefit the customer -- and time spent obsessing over the customer may easily come at the expense of reusable knowledge.
Any methodology used by developers must take this tension into account. Ward suggests a non-authority project leader (like Toyota's chief engineers) whose job it is to deliver the best products in the world. To help them, functional departments do the actual job. But the functional departments are responsible for creating reusable knowledge, not delivering products.
So there will be a constant creative tension between functional department (who want to further their reusable knowledge) and the project leader (who wants the blueprints now, but cannot order anyone to draw them) and from this creative tension and conflicts great products are woven.
[1]: Actually, he mentions a third in passing: building tools for manufacturing. (I guess the software equivalent is tools for ops, or something.)
[2]: In the software world, read this as creating code that the build system can turn into a useful product.