3 ms·
I'm not saying that developers should ideally be drones who have no say on anything. I'm just calling bullshit in the ADHD-fueled development of nowadays where
by lp4vn 3y ago
I'm not saying that developers should ideally be drones who have no say on anything. I'm just calling bullshit in the ADHD-fueled development of nowadays where people are not even sure about what the final product should look like and put on the shoulders of the developers the workload of dealing with the ineptness of the clients and the managers.
Scrum nowadays is essentially a tool for micromanagement, that's why managers love it and developers hate it. Dailys are completely useless and breaking the development of complex projects in 2 weeks sprints is outright harmful.
- elric 3y ago> calling bullshit in the ADHD-fueled development of nowadays where people are not even sure about what the final product should look like Sigh. Of course people aren't sure about what a final product should look like. It's easy enough for something small, but once something gets big, how the hell are people expected to know how everything will work up front? > Scrum nowadays is essentially a tool for micromanagement, that's why managers love it and developers hate it. Dailys are completely useless and breaking the development of complex projects in 2 weeks sprints is outright harmful. Sure, some managers love scrum, and some developers hate it. But it's not a tool for micromanagent. It's a tool for course corrections in the face of reality. I personally find dailies to be very useful, especially in a distributed team. It's an efficient way of figuring out what's up and making sure all noses are pointed in the same direction. No managers are involved in any of my day-to-day scrum ceremonies. If your manager hits you with a hammer, you might want to consider that your manager is an arse instead of blaming the hammer. When a tool doesn't work for you, sometimes it's not the tool that's to blame, but the larger context in which the tool is being used.