And the only thing even worse than SCRUM is literally every other option
And I think this video is talking about scrum implemented poorly. But admittedly that's the only way I've seen it done š
I'm able to get the good parts of scrum without all the overhead with kanban. Sprints are worthless, work doesn't align on a 2 week cadence anyway.
Sprints aren't for you, it's for the higher ups to have a digestible view of what's going on in the team by presenting work done over 2-3 weeks, calibrating budgets, etc.
As a dev, yeah, sprints feel restrictive and artificial as fuck lol
I prefer V-cycle for when you have a software with known specs & Kanban for when you don't really know what the client needs/wants. I mean those magic clients you hear about but never sees...
I'm glad my company speaks a different language than English, and can't use all the word soup completely. That said, my company is also wondering why my timesheets never add up to the entire day because always in meetings, scrum, or "can we jump on video chat for a sec because it's easier to explain vocally than in writing"... And that "sec" turns into a 30 minute tutorial I have to give.
We translated the agile word soup to French here :(
Ouch... My company speaks French as well. :( I get to hear the buzzwords in English.
My condolences, friend.
A bottle off rum for the morning standup?
Take a shot anytime the non technical scrum master/product owner wants to āhelpā by trying to get someone else involved the moment you mention any kind of detail/problem/thing youāre working on
Itās funny how accountability is just ignored so that certain folks get to feel good.
Having worked in tech companies for decades, Iāve never once felt comfy with letting computer science majors just take the wheel⦠but Iām sure someone think this hits āhardā.
And the only thing even worse than SCRUM is literally every other option
And I think this video is talking about scrum implemented poorly. But admittedly that's the only way I've seen it done š
I'm able to get the good parts of scrum without all the overhead with kanban. Sprints are worthless, work doesn't align on a 2 week cadence anyway.
Sprints aren't for you, it's for the higher ups to have a digestible view of what's going on in the team by presenting work done over 2-3 weeks, calibrating budgets, etc.
As a dev, yeah, sprints feel restrictive and artificial as fuck lol
I prefer V-cycle for when you have a software with known specs & Kanban for when you don't really know what the client needs/wants. I mean those magic clients you hear about but never sees...