3 ms·
I think many (middle) managers are afraid of Scrum and other agile development because their role is sidelined. As "individual contributors", engineers are gene
by cpeterso 16y ago
I think many (middle) managers are afraid of Scrum and other agile development because their role is sidelined. As "individual contributors", engineers are generating actual business value. Engineers can self-organize in "quasi-communist" Scrum teams (as they own the means of production ;) and collaborate with product management who work with customers to derive and prioritize product requirements.
In this scenario, what is a "people manager" supposed to do?
- lloeki 16y agoSmooth things out in the event of engineers being on the verge of shooting at each other. That is, manage human beings to let them work at their best, not timelines and general process flow to achieve a financial goal.
- kwis 16y agoI've helped organizations transition from waterfall to agile, and there was absolutely no decrease in the workload for management. You still need some form of functional management to get the right staff, make sure they have what they need to be able to do their jobs, and deal with day to day issues. This might sound trivial, but it really isn't, and somebody who does this job well will enable a lot more success than somebody who treats it as a minor task. And you also still need some form of product and project management to ensure that the work being done is aligned with strategy, marketing, sales, finance, etc, and to serve as an interface with those groups. Failure to do this effectively creates massive inefficiencies. As such, I really don't think any moderately intelligent competent manager is at all concerned by Scrum, Kanban, XP, TDD, Lean, or any other Agile practice.
- deleted 16y ago[deleted]
- segabach 16y agoThe scrum teams don't own the means of production. Individual contributors are human capital. The means of production are owned by the people in control of the finances and business model. If the company were to shift direction and your product discontinued, it's possible the scrum team would be disbanded and the resources that were being used to support them would be reallocated by the "owners" to a new team that aligned with their decision to shift strategy.
- nostrademons 16y agoThe team could also quit en masse and go found a startup to do what they'd been doing before, if they really believed in it. It's happened to more than a few big companies.
- tomjen3 16y agoYes they do - just like lawyer owns his skills and can take them elsewhere and continue his work. A factory worker on the other hand, can't (legally) take the machines with him.
- nostrademons 16y agoThe job of a people manager at Google is generally to keep the engineers happy and make them want to continue working for Google. Somebody has to be the point person for general career-development issues, so that if you get bored and frustrated with your current position, they can say "Here, check out this other group over in this other area of the company, you might enjoy working with them" instead of quitting abruptly. Somebody needs to make the high performers feel valued, and let the low performers know that they need to improve. Somebody needs to be the point person to handle things if a family emergency comes up and you need to take several weeks off, making sure that your responsibilities are covered by other people and all the administrative stuff is done. The good managers are really good at this. The bad managers...well, I don't work in that part of the company.
- tonfa 16y agoBut aren't those manager doing engineering work as well?
- nostrademons 16y agoPeople managers rarely do engineering work as well - it's very hard to both manage people well and contribute significantly to the code for a project. It also sets up a sort of perverse incentive where you want to look good as a coder by taking on the glamorous, high-profile programming tasks, but this can actually demotivate your teammates because they're left with the drudge work. You don't want to be in competition with your reportees. They're often drawn from the pool of former high-ranking engineers, or at least the good ones are. It's a very different skillset though; part of being a good manager is knowing when to step back and let your reports handle things, and the worst managers are those that haven't managed to separate their engineering ego from their team building ego.
- gamble 16y agoVery true. I worked for a startup some years back where the technical cofounder had a nasty habit of reserving all the interesting problems for himself and fobbing the scutwork off on employees. It was intensely frustrating. Yet somehow they never understood why they couldn't retain programmers...