6 ms·
Do we need a Scrum Master forever?
- jedberg 5y agoDoes anyone still use Scrum? It seems like a fad that sort of died out 10 years ago.
- rybosworld 5y agoA lot of companies have scrum-masters but practice something other than scrum (agile). They also may be called agile-leads, but in my experience they are identical roles.
- ekster 5y agoThe way I have seen the role these days is Agile coach, who teaches the principles of lean and agile as needed and helps teams diagnose problems they are too close to to solve, which is a valuable service. There’s usually one per few hundred people at a company, rather than one per five or so for the scrum master.
- tkojames 5y agoI had job where we had an agile coach. First job at of college.. I thought it was the dumbest thing ever and pointless. Then they fire the person and replaced them. It was a complete 180. The new person was so good at just coming in sitting down and just listening. Then give some quick advice and things to try. Then leave and then follow back up after a bit and check in. Not everything they suggested worked. But it was extremely helpful.
- salt-thrower 5y agoHuge enterprises love it. At least the ones I've worked at do. It took about the last 10 years for them to get on board, but now it's entrenched.
- postfacto 5y agoScrum allows for granular micro-tracking of developers at a daily level while sanctifying the ideas of developers as interchangeable cogs and that leaderships should be able to move the goalposts at the last minute. What’s for an enterprise exec not to love?
- salt-thrower 5y agoWell said. It's funny how Scrum was sold to developers as a way to "empower" dev teams, but more often than not it simply encourages micromanagement and poor planning.
- chaoz_ 5y agoI think most of the teams adopt it’s main activities without strictly following the rules. This way, it’s easy to start using, but teams never truly master it and usually start inventing their own heuristics for planning/reviews. Some large companies, actually invest their time in agile training and contribute to SE process research. From large companies, I can call Ericsson and Spotify (good scrum at scale examples).
- spaetzleesser 5y agoI think the problem is that in most companies agile is viewed as something for the developers while the management structures and processes basically remain unchanged.
- greggturkington 5y agoFacebook, Apple, Google, Yahoo, Spotify, many major enterprises, presumably many readers of this article. Why do you think it was a fad that died out 10 years ago?
- robjan 5y agoScrum and agile are often conflated but are two different things. Agile is more a set of general principles whereas Scrum(tm) is a specific framework
- deleted 5y ago[deleted]
- jedberg 5y ago> Why do you think it was a fad that died out 10 years ago? Because the last time I heard anyone in my circle of friends (which includes people who work at Facebook, Apple, Google, Yahoo, Spotify, etc) mention scrum was more than a decade ago. I've seen people using some Agile methodologies, but not the Scrum framework.
- greggturkington 5y agoOh, so you're going based on a few anecdotes. Well, not even anecdotes, just a lack of mentions. Its easy to find official blog posts of these companies and other major enterprises describing how they use Scrum, that are much more recent than 10 years ago. I'm shocked you've never heard of the "Spotify Model" which has been compared to Scrum@Scale. Ask your friend!
- chrisoverzero 5y agoThe Spotify model is about how people are arranged. It has nothing to do with development methodology or work tracking. From the whitepaper introducing the Spotify model (https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScaling.pdf https://blog.crisp.se/wp-content/uploads/2012/11/SpotifyScal...): > [Squads] are a self-organizing team and decide their own way of working – some use Scrum sprints, some use Kanban, some use a mix of these approaches.
- ekster 5y agoDid anyone actually need a scrum master, ever?
- SippinLean 5y agoHot take, but if you're doing Scrum you sure do. A good Scrum master can make meetings much more productive.
- mberning 5y agoI have never seen a good scrum master in 20 years then.
- maxk42 5y agoI've seen one in 20+ years. The others were all worthless. The net impact of scrum masters on all teams I've been a part of has been negative.
- ekster 5y agoAlternatively, agree to have an agenda for every meeting and then skip the scrum master.
- RaketenStadt 5y agoYour dev team needs meetings? Sounds pretty disorganized. Our team is productive, manages their time well, and communicates without meetings. Did anyone actually need a meeting, ever?
- monkeybutton 5y agoMy srcum master seems to think so.
- nipponese 5y agoOn a perfect team, where everyone is great at time management, honest about productivity, has superb communication skills, and is enthusiastic/loves their tasks, yes, scrum is dumb. For but for the rest of us, the scrum master handles all the unpleasant organizational crap for the team, and thank god for them.
- spaetzleesser 5y agoI don’t think many companies including where I work do real scrum but some weird micromanaged thing that has a lot of artifacts of scrum without really understanding what agile should be. In any case, when I am scrum master I put a lot of effort into keeping the backlog clean and making sure people or teams don’t block each other. I think that’s a valuable thing to do and can be close to a full time job. The big question is why we still have project managers and line managers who sort of do the same thing. Right now we have Jira to track things for the devs, but project managers use MS project so we have the same information in different tools which causes a lot of overhead to synchronize reporting.
- trutannus 5y agoA few places I've seen who do agile basically just practice standing in a circle and giving vague updates about progress ('stand ups') which nobody really listens to. If we disposed of all the scrum stuff around it, this would be effective as a way to handle questions that multiple people have an interest in. Which effectively is what it devolves into most times.
- mokarma 5y agoOne of the few places in tech where using the word "master" is cool. It's not entirely clear why.
- jedberg 5y agoBecause it means "mastery of the subject matter" and not "master of other people/things".
- codyb 5y agoScrum trunk doesn't have the same ring to it I suppose.
- mberning 5y agoMasters have slaves. Which is exactly how workplaces implementing scrum view developers. Slave to the business and really the lowest level worker ant.
- rs999gti 5y agomaster/slave for drives? master for main branch?
- buust 5y agoI don't think I have ever witnessed a more efficient way to waste time, meant for solving technical problems, than by doing vanilla scrum (in an major corp ops team). For me following scrum "by the guide" is the pinnacle of pseudowork and by that definition the scrum master is a pseudo role.
- sz4kerto 5y agoThe relevant question: - We choose to do X - Do we need someone being responsible for X? The answer is almost always "yes". If you want Scrum, then having someone who has explicitly been dedicated to it makes sense.
- deleted 5y ago[deleted]
- yellow_lead 5y agoIn my last job, I witnessed the leadership become seduced by the Agile / Scrum industry. It started simply enough, a talk by an agile practitioner. He essentially said that all of our problems could be solved by fully embracing agile. Many such solutions contained circular definitions - i.e what is the "team" in Agile? The team is whatever works best for the organization. Next, the company threw our engineers and other coworkers into two days of remote training - a complete waste of time to say the least. By this time, my company was already hiring these scrum masters. I view the whole thing as a sort of cult/koolaid/consulting industry. The original intentions of the Agile Manifesto may be good, and I admit there are some good ideas in there, but the entire industry that has formed around it is a waste of money IMO.
- ethbr0 5y agoWhat is the problem that Agile attempts to solve? That your organization is too siloed and ignorant of the what colleagues do to write proper requirements. And that your engineers are too ignorant and siloed to speak up when requirements aren't appropriate. And more formality, rote obedience to procedure, and documentation are going to solve this? Tl;dr - If your organizational culture is fucked up and not working, fix your organizational culture. There's not enough agile in the world to build on top of a cracked foundation.
- golemotron 5y ago'Scrum Master' was a clever hack. You couldn't exactly fire the managers in most organizations. The concept of self-directed teams is scary to many people; but you can give managers something else to do.