I very much liked this post by J Schwan (here) about the dangers of over-specialization. Some of the comments miss the point — J acknowledges the value of domain knowledge — which is that a role-bound workforce conspires against:
- Understanding how to optimize the whole vs one’s part.
- Remembering why one is doing a project in the first place.
- Accountability for results.
As J notes, it is easy to hide behind a “work to role” facade. But that’s all it is, a facade and a thin, deluded one at that. To be blunt, strictly bounded roles end up becoming jobs that get outsourced or automated. I can’t imagine wanting to working in such an environment anyway.
J paints a picture of a healthier technology workplace:
Sure we all have roles we prefer to play. I love technology architecture work, and if I’m working on a project that’s going to require more than a handful of people, I’ll bring in one of our PM gurus, because frankly, I’m not that great of a project manager. But I do know the difference between a Gant Chart and a Sprint Queue, and when it makes more sense to use one versus the other to manage a project. And I like the fact that our PMs understand the difference between a web server and an application server, and that our BA gurus have no qualms about doing QA work or rolling up there sleeves to fix some simple bugs if that’s what the project needs.