Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
sariel84473yFor development, no scrum.
For project management, scrum.
A single feature request may have 12 different stories attributed to it, no reason to weigh down the devs on pomp with weekly or biweekly meetings.
Project management thrives on pomp. Consistent delivery means constant communication about where a feature or project is.
Just my opinion though. -
Root797703yI prefer to be left alone.
Weekly updates at most. Maybe a couple of others ad hoc if it’s important.
In my current company? Weekly planning, biweekly sprint retros, daily standups, and product yells at you if you don’t move whatever ticket you’re currently working on at the moment (multiple a day) to the right column of the pseudo kanban board so they can track it and feel like they’re earning their paycheck.
Yep. Scrummy agile kanban.
I have 11 meetings a week and barely have time to get anything done amongst the planning and status updates and announcements and security meetings and UATing (demos to product) and retros and “show-and-tell”s and pairing and one-on-ones.
Just leave me alone, seriously. -
@Root Same here.
They wanted go make me a Team lead - it means an extra senior dev, with more meetings, and much more back stabbings. Fuck That.
Our "scrum sprints" are set at two weeks, then strech to 5(!) becuase the version(!!!) should always be released at end of sprint.
I had enough. Moved my team to kanban - no planning, retros, or other idiot meetings. Just put the ticket up on the board, and the team will deal with it when we have a minute. -
Yeah I like scrum - drank the coolaide a while back. I love that there is a board where micro managers can see what they need to see and if they bug me I can just say, “well you know what I’m working on, when I started and when I estimated I would finish, by disrupting me all you’re doing is slowing the process down, but that is your prerogative, but it will come up in retrospective and probably become a factor in the next planning phase”
-
Crost40743yThe problem with scrum is that team leaders always think scrum == agile. Scrum literally says nothing about technical quality, and of you read the agile manifesto that sort of thing is in there.. because we are building technical products...
Actually if you look into the first book on scrum from the creator it even says on the cover it is aimed at making agile palatable for managers.
Scrum, Kanban, whatever. I care more about ensuring technical excellence than helping managers do their job. -
It stands and falls with the PM.
If you as a PM fail nothing will work at all.
And the failing PM is the gist of many rants here... -
I'm asking because Scrum in my temp company is annoying. Scrum meeting every 3 hours. Like wtf.
-
sariel84473y@johnmelodyme that's insane.
You should collect a week of calls you take that are related to scrum. Note who's on them, and then bring it up to your supervisor.
They can take it to HR and get a cost analysis done on it.
Who knows, you might even save your company money and score some brownie points at review time. -
@sariel unfortunately it is the superior is the one doing it.
The thing is all of us are work from home. They fe l like we don't do enough job , so Scrum are needed to keep track on what we do.
But we already have JIRA for that... I don't mind Scrum once a week but 3 hours once everyday is a little bit too much .
This cause me distraction and wasting my time. -
sariel84473y@johnmelodyme that's one expensive call.
If that was my team it would be costing the company almost $3000 a week.
Larger teams, larger costs.
Side note, most expensive call I've ever been on was around $1.2 million and lasted for just over 8 hours. -
@johnmelodyme I thought I had the worst scrum team going because we barely do any of the practices but you are at the other end of the spectrum
Do you prefer Scrum or no Scrum?
question