8 ms·
I added up all of the time we were spending in Scrum-related activities at a recent job. The company hired a lot of project and program managers who were pullin
by Aurornis 3y ago
I added up all of the time we were spending in Scrum-related activities at a recent job. The company hired a lot of project and program managers who were pulling everyone into everyone meeting.
I presented the number of hours (meetings multiplied by engineering participants) to our VP and he insisted I must be wrong. He insisted there was no possible way we could be spending that much time doing Scrum things and that I must be exaggerating or lying. He then fell back to a lecture about how Scrum is an industry standard and how it's more efficient than alternatives.
Really opened my eyes to the disconnect between Scrum mythology and Scrum in practice. The amount of time lost to doing Scrum things was so out of control that some people had fewer than 3-4 hours per day to actually work.
Of course, the Scrum proponents will rush in and tell me that we were doing it wrong or that it's not truly Scrum if it's helping more than hurting, but these people were highly trained in the ways of Scrum and Agile and pointed to various Scrum and Agile books and certifications to defend their ways.
OTOH, I have been on very small teams where Scrum was implemented with low overhead, but those teams were filled with efficient people who would have been productive without formal methodologies either way.
- rightbyte 3y agoThe far biggest time sink is not what you logged though, but how you need to pad estimates and delay work to please the Scrum Lords. Like, the burndown chart has to be nice and steadely go to zero. There is no way to do that without decoupling reported hours and estimated hours from actual hours. Or points. It doesn't matter which.
- yieldcrv 3y agoI saw this on my last job! I was already adding time to my work like an extra point or two here and there But then in the grooming session the whole team would guesstimate even more story points! I was dumbfounded! This was beyond all of my levels of tolerance and rationality but it kept happening every sprint until something that was a 0.5 for me was a 5 point and I would have two 5 point tickets for the whole sprint that I would submit to QA one day before the sprint ended, 9-10 business days later and actually doing that made me a star performer, what the hell!?
- flir 3y agoThat kind of inflation corrects for itself. Because you're supposed to look at the previous sprints to judge how many points you'll get through this sprint.
- inanutshellus 3y agoScrum teams are self-managing, and point values are used for gauging your own team-workload. When you point a "0.5" and your team points a "5", stop and discuss the discrepancy until an alignment can me found. Keep doing that, every task, until you a collective meaning of "a point" is found. Personally: * Less than 1 - These are a smell and should not exist. These misalign incentives and encourage "bike shedding". * 1 point tasks - no task that requires 2 people (dev and qa) is a 1-pointer, so this is something that needn't be QA'd. 1 point tasks should be rare items that can't be a subtask of a "real" task. * 3 point tasks - These can be done in a day (depending on the team's opinion, this might be multiple people and still be 3 points). Virtually every task should be a 3. * 5 point tasks - These are tasks that cannot be broken down to be done in a reasonable amount of time. These are generally things that have minor external dependencies. ("not hard but I'll have to get a server spun up by the unix admins.") * 8 point tasks - These are rough tasks that haven't been fully dissected by the team and are the scrum version of a "code smell". The team should break these down and dissect them. * 13 point tasks - "There be dragons here" tasks. Large unknowns and these tasks should not be added to a sprint until they're broken down further.
- ed_elliott_asc 3y agoMeetings are long enough without people spending extra effort doing it right :)
- inanutshellus 3y agoSharpen the saw, man. It's a one-time conversation (per new team configuration) that makes every conversation thereafter fast. My team's pointing sessions are lightning. Even when you do have a new team member that wants to discuss a "0.5-vs-5" point disparity, you explain the above in less time it took to read it and get back to work.
- lowercased 3y ago"POINTS AREN'T TIME! THEY'RE EFFORT AND/OR COMPLEXITY!" I've been routinely told. Yet... low complexity stuff was expected to take less time, even if it was high effort. All 'in my experience' of course. Changing 95 files because someone didn't want to centralize some value in a method call last year (YAGNI!) is now high effort, even if low complexity. Then... "that's too many files in a PR! break it up! no one can review that many files!" It's the same two line change in each file - this shouldn't take that long to 'review'. I've often spent more time arguing about points/effort/estimates than doing the low effort work. But if we don't record it properly, you won't get 'credit' for the work! Slow-paced insanity when taken anywhere near close to its logical conclusions.
- peteradio 3y agoHaha after 5 years our scrumlord finally relented that 1 point was 8 hours for our team because even he was apparently getting tired of the cognitive dissonance.
- candiddevmike 3y agoI love hearing "points aren't time but you can think of them like days"
- ed_elliott_asc 3y agoMy response to estimating is that if you want anything accurate I’ll need time to estimate - roughly 1/4 of the estimated work should be spent estimating. As a rule of thumb, if the work is estimated to be a day then is should take me 1/4 day to estimate. If two days then half a day to estimate. If 4 weeks then 1 week to estimate. We normally continue with guesses that are meaningless.
- bee_rider 3y agoWhat would you do if they actually gave you a week to come up with an estimate? Start drawing Gantt charts? 1/4 seems reasonable for a day or two, but I dunno… it seems like there must be some constant factor?
- robterrell 3y ago> the Scrum proponents will rush in and tell me that we were doing it wrong The "no true scrumsman" fallacy at work.
- denton-scratch 3y agoAnd in fact (if you read to the end) that is exactly what the author is claiming. Which is why the title is clickbait.
- marginalia_nu 3y agoOne of the most reliable indicators I know of a dysfunctional team is on average how many times whether what being proposed is sufficiently agile is put to question per meeting. If this is greater than some epsilon much smaller than 1, then you have trouble. Overall "is that really agile though?" is such a fantastic thought stopper. It's can be thrown out to derail any sort of proceeding. It moves all focus from what's practical and applicable and relevant to the situation at hand, and moves it to an endless discussion about philsophical alignment.
- Cpoll 3y agoIt's not a "no true Scotsman" (scrumsman :)) if the counterexample is in fact not a Scotsman. Whether it is or isn't depends on your feelings on scrum, but it's not a fallacy to try to defend the initial definition before it was co-opted by anyone with an Agile cert. "Hammers suck at driving nails." "You're holding a rubber mallet." "No true Scotsman!"
- robterrell 3y agoYou make a good point! But scrum as we know it today is not Agile: "Individuals and interactions over processes and tools." Processes and tools (i.e. Jira, sprint planning, retrospectives, etc.) dominate all implementations of Scrum I've seen.
- alexjplant 3y agoThis. People love dunking on Scrum because they have colleagues and managers that wield it as a weapon (often in conjunction with JIRA, which, although not an especially simple or well-running piece of software, is really only as bad as you choose to make it). It's actually a very simple process that was designed as the _antithesis_ to a lot of the atrocities committed in its name (based on a reading of this thread). If you have managers/PMs/TMs/HMs/BDFLs that can't see the forest from the trees and a corporate mandate to use Scrum (or Agile generally) then of course they'll pervert it to suit their own ends. Slow-moving organizations with complex incentive structures like the government and Fortune 500s are especially good at this. If you want to be upset with somebody then blame them. I've worked on teams where stand-ups were less than ten minutes long, we delivered every two weeks, and we had properly-specified Scrum Master and Product Manager roles and it worked swimmingly because we _actually did Scrum_, not "Scrum, but...". Scrum is a prescribed process. It is not the performative act of dragging work items into Sprints in JIRA then using various Scrum terms for 5-hour-long weekly meetings.
- hoc 3y agoNo True Scrum Master... should get its own Wikipedia entry at last. (Ah, too late. Guess I should have refreshed)
- JohnMakin 3y agoThe last org I was in realized how much time their engineers were spending in agile-caused meetings, much like what you describe, at least half of the working hours in a week - so they made a company-wide rule that no one could spend more than 4 hours a week in meetings. What happened instead were impromptu "ghost" meetings and a ton of stuff done sloppily over chat instead, where I think the hope was that people would try to become "more efficient" with their meeting time.
- ethbr1 3y agoTo me, RACI charts are a missing component of meetings. Required meeting attendees should consist of the Rs... and only the Rs. As and Cs can be optional, but meetings can conclude without them. Everyone not in the meeting can be updated out of band. "What action is this person taking in this meeting?" should be a brutally honest question. If the answer is only "listening", then it's a waste of their time. And also, related point: what is the termination condition of this meeting? And has that been decided and communicated beforehand? I.e. What outcome are we seeking, that when done everyone agrees the meeting is over? I can't stand agenda-less, "we're meeting to move something forward in some undefined way" meetings.
- wheelinsupial 3y agoAgendas are critical and so is the purpose of the meeting. Is the purpose of the meeting to inform, decide, workshop, or persuade? If it's to inform, it should be an email, but some people do not read them, so you need to sometimes read the email to them in a meeting. If it's to decide, do you have the people that will decide called out in the agenda? Do they have the necessary information or have they done the necessary work to make a decision in the meeting? If it's a workshop, do you have the invitees pared-down to those that will be actively participating? Is there work they need to complete before the meeting, so they can be active participants? If it's to persuade, these should be in smaller formats. Preferably 1-1 to start, so objections and resistance are raised in low(er) stakes meetings. Meetings should end with a summary of decisions, next steps, or some other call to action. Preferably these are recorded somewhere and distributed to the rest of the attendees or a wider audience if needed.
- lacrimacida 3y agoI have a similar experience to yours. My organization even hired a scrum expert who is probably just deadweight, he’s on mute in all our meetings for the past 6-8 months. It’s also true about having little actual work time, in my org we spend so much time in meetings that in the end 3-4 hours of actual work are left on a daily basis. I objected to this but was told everyone should learn everything, end of story. We’re supposed to be repleaceable cogs in a machinery and that goal was reached by now.
- jacobyoder 3y ago"everyone should learn everything" I've been in a couple places where I did know 'everything', or... near enough. The more I got to learn outside my own specific dept, the more cynical and frustrated I became (usually). You start to notice that entire groups of people are often just sitting around for days doing absolutely nothing because they're waiting for one person who's out for the week, etc. Or you learn that people just spent 4 months working on something that was rejected in a meeting 4 months earlier, but... the original team still wanted to do it anyway, and therefore couldn't help your group over the past 4 months.
- onion2k 3y agoThe amount of time lost to doing Scrum things was so out of control that some people had fewer than 3-4 hours per day to actually work. If the aggregate of the sprint planning, backlog refinement, retro and dailies is more than 10% of the total time (eg 1 full day out of a 10 day sprint) for most of the team then something bizarre is going on. If the everyone is losing 50% of their time to agile things then your process is impressively broken.
- calvinmorrison 3y agoUntil you're on 4 teams
- michaelt 3y agoIf a person is in 4 teams, and they're not a full-time 'product owner' where going to meetings is their whole job, I'd say something bizarre is going on.
- kjs3 3y agoI don't think it's that 'bizarre'. My team has been an overlay team for years. We provide services to many teams. Since the glorious transition to agile and product focus, we had to sacrifice someone to be the product owner, so their 'whole job' is overhead management, which they hate. Now, every team wants someone from my team in every standup ("but we'll be blocked if a question for your team comes up and no one is standing in the corner patiently waiting to answer it") and definitely wants someone in every sprint planning. 8-ish person team, dozens of projects, and time disappears very, very fast. I've managed to push back on the 'every standup' nonsense so we don't spend 100% of our time in meetings, and in return the agile folks are using their 'metrics' to basically tut-tut and say we don't do any work. I can see where if your whole job is on a single project where there workstream can be easily decomposed into 'sprint-size' chunks, agile and the rest are probably useful. But that's not every job, and maybe not most jobs, and it sure as hell isn't my job. But like so many other have concurred, and as I see on a routine basis, there will be someone with 'Agile' or 'Coach' or 'Product' in their job title will have an expansive explanation why I'm Doing It WRONG. Capital One seems to have figured it out...maybe there's hope[1]. [1] https://www.reuters.com/technology/capital-one-scraps-1100-tech-positions-source-2023-01-19/ https://www.reuters.com/technology/capital-one-scraps-1100-t...
- CharlieDigital 3y ago> everyone meeting This is one of the things I've added to me repertoire when I interview with teams: I always ask how often they meet and how they structure their meetings. Big red flag is there is a daily all hands (yes, I've seen this in a 16 person startup) I think it's emblematic of a few things about the founder/cofounder/lead: 1) they are an egomaniac and just needs to see everyone reporting in, 2) they don't trust their teams because they need to have daily all-hands status updates, 3) they're not connected to their teams' work; there is no visibility into what's getting shipped, 4) there's a strong correlation with micromanagement. Learned this through a few mistakes joining teams where the founder/lead insisted on frequent all-hands standups (sometimes lasting 45-60 minutes to get through all of the teams reporting in).
- zer00eyz 3y agoI run this meeting often with teams. It should be a literal standing meeting. You dont get to sit and drone on. There is one in every bunch and when they make their peers stand for 10 mins. The team will self correct the person into not being that way. That meeting is a check point. What is every one up to, and everyone else gets to hear. It's a way to get a team to gel (and many aren't)... If someone surfaces a problem in there (and they should be) then there should be some other team member offering to help out - there should be dialog if some dependency is going to get bumped by others being distracted. These meetings are effective up to about 10 people. They work well with cross functional teams, or teams where the members have varying levels of experience.
- eevo 3y agoTime spent with the team ebbs and flows depending on complexity of projects, where in the roadmap you are, seniority of the dev team, and more. The agile manifesto was too abstract in it's original state, and folks who needed a rigid framework created capital A agile in order to adapt it to their cog in the machine role. For my team of 6 in a ~20-25 person (remote) startup, we have a 30 minute dev meeting in the morning, and a 15 minute full team meeting where the agenda rotates daily around departments. I quite like it honestly, remote can be lonely and isolating otherwise. Generally I think it's important to structure team responsibility around who ultimately needs to make the decision (although they need to consult others and get team buy-in). And hire people you trust to make the decisions. Then the meetings become about problem solving and getting through the work, rather than performance art and politics.
- AtNightWeCode 3y agoJust by switching from Scrum to Kanban one can improve progress a lot. For being two very similar pull based systems the difference in effectiveness is just incredible.
- kjs3 3y agoThis is what we've done of late. Massive improvement. Much lower time commitment and we get a good (enough...not perfect) view of the metrics we really need to focus on.
- lars_francke 3y agoAgreed. We use Kanban and are very happy. We used to not do any estimates but have voices from others asking for them to do better planning of marketing and sales activities. I understand where they are coming from but so far it's mostly guessing So: Do you do estimation in Kanban and if so, how?
- skydhash 3y agoYou don’t do estimation without prioritization. As a consultant, my default way of working is kanban, often setup on Trello. Once I deconstructed the project into features, the first thing I do with the client is arrange them by priority and arrange them into sets for releases. If sales and marketing need to do planning, then they need to tell what they want to push back to the backlog so that the feature they want are on time.
- lars_francke 3y agoWe do that already, yeah. But they'd like estimates on a lot of issues so they can prioritize better. I believe it's a waste of time though. There is no good solution for this I believe.
- edgyquant 3y agoI think generally you should be able to break some feature up into a series of very small tasks that can be estimated. So you may not be able to estimate an end to end feature accurately but you should be able to give rough ETAs for when different functionality will start to trickle in
- andrei_says_ 3y agoI really like Dave Thomas’ talk Agile is dead long live agile. Dave’s name is listed as one of the creators of the agile manifesto. Basically, agile is an adjective. Anyone using it as a noun is selling snake oil. Yes, it is that bad - a whole industry built from the ground up to monetize a simple concept by enshittifying it into its very opposite. https://youtu.be/a-BOSpxYJ9M?si=tCvDcHYv7F77XbZ9 https://youtu.be/a-BOSpxYJ9M?si=tCvDcHYv7F77XbZ9 I also like Basecamp’s shape up process which seems to follow the spirit of the manifesto.
- ethbr1 3y agoThere should be a saying, to the effect of: no enterprise idea can survive intact if it doesn't include a space for consultants. Agile probably would have ended a lot better if it had been as designed... plus a requirement that you had to hire an agile specialist to sit in a closet. The agile specialist doesn't do anything but sit in the closet. ... but on the plus side, the agile specialist doesn't do anything but sit in the closet.
- h335ian 3y agoBeen using ShapeUp for nearly a year now in an org of ~50 engineers. Let me start by saying, if you intend to adopt ShapeUp, spend a great deal of time reading and buying into their structure of teams. Aside from SIP/QA & KTLO work, they flatten the “Core Product team” and build ad-hoc teams for a pitch that has won at the betting table - for that cycle. Trying to maintain standing teams with domains of ownership is a very challenging way to adopt this process. In my experience, unless the entire org is drinking the kool-aid - hard - you end up with 6w cycles of waterfall. Pitches morph quickly from “present your idea that we bet against” to “write up a detailed design doc, along with an Epic, backlog and all projected work” - then the org will just do the work they want (betting or no). Now your team is committed to delivering on your pitch - any other work just gets dumped on the wayside - unless you’re on-call of course. As with any other incantation of an agile process, you can bastardize it to confusion, thinking you’re smarter, or “we’re adapting this to fit our org”. Folks, this stuff is a discipline. You have to buy in, you have to learn the principles, you have to practice them - as described - until you attain some degree of mastery that you can adapt. This is not an individuals game, this is at the org level. The individuals must commit with the org to gaining mastery before customizing to your liking. In spirit - there’s nothing fundamentally broken with Scrum or Kanban or ShapeUp or whatever. It’s really how you hold it - and yes you can shoot yourself and others in the face by holding it wrong.
- libraryatnight 3y agoI feel like SCRUM and anything like it is an attempt to formula and process-ify a thing that dies when you do exactly that. At my company we waste a ton of time on this stuff but we also have a ton of people with jobs that really only tie in to it so they will always defend it. Bureaucracy serves itself etc.
- ljm 3y ago> Of course, the Scrum proponents will rush in and tell me that we were doing it wrong I don't think it's helpful in any discussion to try and pre-emptively dismiss people who might disagree. People have been doing that for the decade or so scrum has been mainstream and it just dumbs the discussion down to he-said she-said. That being said, agile as it was originally described in the manifesto was not prescriptive, and scrum, while it was intended to follow in its footsteps, has been a victim of its own success. It's now firmly in the domain of other highly-prescriptive management frameworks thanks to the effort of consultants and managers who adhere strictly to the letter of scrum without paying thought to the essence of it. Most people I know who were fans of scrum back in the day have distanced themselves from it because it's not agile any more. Certainly not with consultants selling SAFe as an agile methodology.
- Aurornis 3y ago> I don't think it's helpful in any discussion to try and pre-emptively dismiss people who might disagree. But that's exactly what the people I'm talking about are doing: They define scrum as something that works, thereby preemptively dismissing any complaints from situations where it didn't work.
- mirchibajji 3y agoJust like "You are not your code", may be we should also have a "You are not your Process Certificate" mantra. It is not the people that are dismissed, but those who insist on The Process at all costs.
- Foobar8568 3y agoI had some coworkers who would spend 6hours in scrum related meeting every Tuesday....In addition to their daily 2h scrum meetings ( multiple teams and role meeting coordination).
- poisonborz 3y agoI don't get your problem. What were you talking about on those meetings. Wasn't it about the project? Is discussion about the project, the features, planning lost time?
- wkrause13 3y agoI recently dealt with the same thing. We had an experienced CTO come in and implement a “big company” style of Agile. In all fairness, there was a lack of process that needed to be addressed, but the pendulum swung very much too far in the other direction. He left the company and I stepped up to fill the gap. First thing I did was quantify the amount of time the team was spending in meetings and it was over 25%. Those meetings weren’t even efficiently grouped, so with context switching it was even worse. Luckily I was in a position to change things and consolidated a lot of the ceremonies. I kept more of the process in place for our offshore partner team because the communication burden was higher. So I guess my two take aways are that time in meetings needs to be evaluated with how meetings are grouped to avoid too much context switching and allow for folks to get into a flow. The other is that how strictly you adhere to “textbook” scrum really depends on the composition of the team. More junior teams or teams that are insolated from the larger business context benefit more from more process imho.
- Scubabear68 3y agoInteresting, I have a very similar story from last year. Existing CTO and head of product acted as if they were writing complex, mission critical software (they weren’t) and instituted processes to match. It went from overly ad hoc to over-the-top scrum. As a result, features took months to develop and everyone was terrified of releases. Teams bloated to massive size. CTO was fired, I came in and evaluated everything, slashed the consulting teams down to the ones clearly performing, and slashed the processes down to boot. Within a month the team velocity was way up and we were releasing to a nice cadence without fear. And this was not because I’m a super man. I’m not. Any competent tech lead or manager could have done the same. The only difficult part was dragging the product folks along, they kicked and screamed the whole way, predicting doom, and were amazed when the sky didn’t fall.
- iLoveOncall 3y agoWe did a planning exercise every sprint at work to see how much time people had to work on features once you removed meetings and other ceremonies, RTO, holidays, oncall, etc. We were tracking that per employee. Everything was fine for a few months and then I added a "total" column next to each row and it became apparent that we were spending close to 60% of our sprint on non-development related tasks. On 45 work-days per sprint we had something like 19 days for features. Needless to say it shocked my manager. He's not against change thankfully but we're still evaluating what could be better alternatives.
- kevinmchugh 3y agoDo I understand correctly that you're doing nine week sprints? That sounds extremely long to me. I have to think you're spending lots of time planning work that won't be done. When you plan a sprint, how often does the work at the end of the sprint actually get completed by end of sprint? Say you plan to start the "add Foo button to Bar page" in week 7, do you actually do that? That would require some really strong estimation skills and a remarkably stable product and business environment. What's the point in the sprint where you're doing more unplanned work than planned? Or how much carry over work do you have? Because if I was trying to plan nine weeks of work, I'd get it drastically wrong, and waste tons of time planning stuff we weren't gonna do. I would make the next few sprints 4 week ones and plan to get down to 2 week sprints after the shorter pace starts to show it's strengths. Or maybe you have 9 people doing 1 week sprints and that's how you got 45 days. In which case, whoops! I have no suggestions!
- iLoveOncall 3y agoOh yeah no I meant 2 weeks sprints with a total of 45 days (ish, removing vacations) for the whole team. Sorry that wasn't clear.
- torginus 3y agoNever in my life have I encountered anyone from the engineering side who spoke positively about scrum. It's always the consultants and scrum masters and their ilk who push the agenda. Never have I ever heard about any story about agile making things better.
- ed_elliott_asc 3y agoI’ve seen it to be very effective but it is rare - especially in enterprises where the old “project office” folk switched to being scrum masters.
- tonyarkles 3y agoI've worked at exactly one company where Scrum worked really well, but it was a somewhat... unique isn't the right word, but a specific set of circumstances: - the team was made up of primarily junior engineers with a small handful of intermediate and seniors - the company's work was split between a product and N consulting projects - the company had standardized on a specific "default" architecture (Spring Boot + Angular) with a bunch of pre-existing components that teams could use to accelerate their projects - the projects (product and consulting) were generally managed by the intermediate engineers with a handful of juniors on each project doing most of the day-to-day work - the seniors were mostly on the product side but had latitude to go help on any of the consulting projects if anyone was stuck Scrum with the daily standups and bi-weekly retros worked great here. The seniors went to all of them. If someone was getting ready to start on something and they weren't aware of existing components that were either available from the library or available to libraryize from a different project, we'd help facilitate that. If someone was getting stuck on either a tricky debugging problem (of which Spring Boot was good at making) or a complex design problem, one of us would stick around and just get it solved with whoever had the problem right away. And on the other side of it, we were sufficiently looped into the various projects that we could use that as input for larger-picture architecture decisions etc.
- The_Colonel 3y agoI'm old enough to have extensive experience from before agile methodologies were in vogue and things are generally better with Scrum / Agile than they were before, ceteris paribus. Sometimes the process worked better, sometimes worse. It depends a lot on the company culture and people. The company I'm currently at has a very good process (SAFe). (I'm an engineer to clarify)
- ajmurmann 3y agoI personally strongly dislike a lot of aspects in SCRUM (individual commitments stick out especially, together with the entire role of Scrum Master), but am not sure I see an alternative for some form of agile (without the TM), that is adjusted to the individual team's needs, for the vast majority of teams. Whenever I read these criticisms, a lot of it rings true, but I fail to understand what the alternatives looks like besides Waterfall or chaos. Whoever does these write-ups always complains about some Agile™ thing, but takes the alternative for granted. What activities and meetings would be dropped or replaces and by what? It's not very meaningful to criticize something when comparing it to nothing.
- kevinmchugh 3y agoThe obvious alternative to scrum for many teams who wish to be agile is something based on kanban.
- deleted 3y ago[deleted]
- ajmurmann 3y agoWhich is another flavor of Agile which is what everyone is always complaining about. I'd take some form of Kanban any day over doing rigid Scrum by the book. Kanban needs a lot very similar meetings though. You still need to fill the backlog, discuss the tickets. If you were to do Kanban by the book as described by the Agile Alliance, you'd still do standups, retro under a different name etc.
- kevinmchugh 3y agoIn my experience people complain about strict processes that books or consultants say must be followed. I've rarely heard someone complain about the content of the agile manifesto. So start with what you've got, and iteratively keep what works and chuck what doesn't, until you have a process that works. I'll add that kanban means much less time filling a backlog, to the point that an individual can own that, and you're eliminating that meeting.
- kurko 3y agoMy hypothesis is that those people I worked with circa 2007-2015 that did Scrum really well (not everyone did), were happy about using Scrum, and delivered good results, ended up progressing/moving into management and lost contact with the day-to-day work. 1. They have an imaginary reality based on what it once was. 2. They don’t accept the evidence. 3. They have incentives to build systems of people to increase their salaries.
- fatherzine 3y ago"people had fewer than 3-4 hours per day to actually work" had the same experience. the unwritten expectation was to pull 8 hour coding days /plus/ all the Scrum overhead. if you don't like it, there's 1000 guys waiting to take your place, partly thanks to remote. a core reason we haven't fire you yet is that it is costly to ramp up new people, but don't try our patience. see also "hire fast fire faster"
- cassianoleal 3y ago> "people had fewer than 3-4 hours per day to actually work" had the same experience. Same. Even worse, spread out in between meetings. Some days I'd have barely started understanding the work to be done and it was time for the next meeting. Rinse and repeat for each "non-meeting" slot throughout the day and the whole day is a write-off.
- aeturnum 3y agoI've had good luck with small teams implementing "scrum" which really came down to: the team finding a minimal coordinating process that uses short units of work. I will say that the part of scrum that I like (and I think most people like) are qualities that it's easy for like minded people to recognize. But if someone doesn't get...why it's good to summarize your progress for the team or break things up or understand what a task does for multiple stakeholders...scrum does not communicate that to them effectively. Imo it feels like a system you can use to teach people how to work effectively, but in general those who haven't seen most of it themselves often get buried under an avalanche of terminology and procedure.
- ranit 3y ago> the Scrum proponents will rush in and tell me that we were doing it wrong or that it's not truly Scrum if it's helping more than hurting Did you worded it like this on purpose, or you wanted to say the opposite? :-)
- BeetleB 3y agoCan't speak to your company, but in my experience all Scrum (done well) is doing is making the overhead explicit and easy to quantify (as you yourself were able to do). Eliminating Scrum doesn't mean you'll save that time and overhead. It will simply be hidden. Of course, that's with Scrum done well. If you're having 30 minute daily meetings, you have a point.
- Viliam1234 3y agoI was trained in Scrum, but the main thing I learned was that it is the opposite of what the "companies using Scrum" do. When I mentioned that in the company I worked at (the one that paid for my training), I was told that "we do Scrum differently here". They paid for my Scrum training just to tell me to shut up and do it the traditional way, only now I was supposed to call it Scrum, and the existing meetings had to be renamed using Scrum terminology. Oh, except for the retrospective (the part where developers provide feedback on everything, including Scrum itself), because retrospectives are a waste of time! So it seems to me that the main reason why "true Scrum has never been tried" is that most companies never intended to actually try it. They just wanted the buzzword.
- stcredzero 3y agoSo it seems to me that the main reason why "true Scrum has never been tried" is that most companies never intended to actually try it. They just wanted the buzzword. Scrum is actually a cultural change. The methodology is just the surface stuff, like the buzzword. It also doesn't actually happen at the company level, unless the company is quite small. It happens at the group level. I just thought of this: The Scrum that can be named, is not the true Scrum. "Practicing" Scrum by following dictums in a book is sort of like practicing marriage by following dictums in a book. Those are just guidelines, and the reality is at a deeper level. EDIT: Come to think of it, that can also be interpreted as: Therefore Scrum is broken as a methodology. It cannot be "followed" at scale. (Much as communism is broken as an economic system.)
- al_borland 3y agoOn the opposite extreme, our teams use Jira, kind of structure it like Scrum, but don’t do any of the actual planning. It’s complete chaos and we have a similar level of meetings, maybe more, with everyone trying to figure out what’s going on and when things will be done. The go-to is a 30-60 minute daily meeting with each individual project manager for each project. Sometimes there are 3 project managers working on different aspects of the same project, so we have 3 hours of meetings (spread throughout the day) to give the same updates 3 times. Of course, there is no update, because all we do is attend meetings to provide updates. Occasionally our Scrum Master will put an actual scrum meeting on the calendar, but then talks about whatever he wants, and it never moves the ball forward from an organizational point of view. A retrospective would go a long way; we’ve never had one of those. I bring that up often, as the 1 meeting we should have, if we only have 1 meeting. I tracked my time meticulously for several years, and when I used it to point out how horrible the current environment is, I was told I was doing too much and should be much my lazy about the tracking, to the point where it becomes meaningless.
- therealdrag0 3y agoIt sounds like you just have poor leadership or poor PMs. Daily meetings should be 15 min with an extended optional “parking lot” to dig into things and everything else should be adhoc meetings with as few engineers as possible, except a weekly and monthly meetings. I’m a team lead (not manager) and I get over 50% if my time is builder time and I haven’t measured but I’d guess my teammates are around 80%.
- ninkendo 3y ago> some people had fewer than 3-4 hours per day to actually work. 3-4 hours per day? That seems like a lot to me! Looking at my calendar, I’m lucky if I get that many hours per week. (It’s not all scrum shit, but let’s just say between sync-ups, status reports, daily standups for multiple projects I’m involved in, architecture reviews, breakouts, etc etc etc, I’m lucky if I get a full work-day’s worth of coding done in a week.)
- brightball 3y agoScrum often has very subtle issues that snowball into chronic issues. I've never seen it done well outside of contract dev shops where they are literally negotiating and selling each sprint to a client. https://news.ycombinator.com/item?id=17154355 https://news.ycombinator.com/item?id=17154355
- koonsolo 3y agoWhy not bring this up in the retrospectives? Why not make your process leaner in the retrospectives? That's what they are for, no? Self-organizing teams is at the core of agile. So I hate to say it, but if you don't self-organize as a team, you're doing it wrong. The fact that you have to go to your VP to present hours says it all, your team is not empowered.