3 ms·
I think this knowledge inversion where the "individual contributors" know more (about the job) than the manager is why many managers do not like agile methodolo
by cpeterso 15y ago
I think this knowledge inversion where the "individual contributors" know more (about the job) than the manager is why many managers do not like agile methodologies like Scrum. Developers are "seizing the means of production". ;)
When developers can work directly with product owners and track their progress, the traditional manager loses. I'm not sure how a developer-driven team might handle HR issues though.
- kls 15y agoI'm not sure how a developer-driven team might handle HR issues though There is a nuance here that is being missed, there is management and there is administration, management is authority and administration is coordination among contributors to keep the production line running. Many organizations mistake the two for the same roles as such they give to many administrators authority and make them managers. When many organizations could flatten their management hierarchy and create more administrative roles. HR is a good example of a business function that can be done via administration and not authority. The funny part is when you make people administrators they see themselves more like contributors and become less threatened by efficiency.
- cpeterso 15y agoThanks for the clarification. Is the administrator role you describe something like a program manager (PM) or scrum master? Would you say a "tech lead" is a manager? They have (technical) authority of the product, but not necessarily hiring/firing of other people.
- kls 15y agoI generally consider leads and architects to be administrators same with project managers, if fact in a good deal of organizations that I have been a part of we did not call them project managers, we called them project coordinators or project liaison which better reflects the role.