3 ms·

Who is Scrum for? I would argue it's not for the developers. In that case, whether or not some teams are happy using it doesn't really matter. It's a tool to

Who is Scrum for? I would argue it's not for the developers. In that case, whether or not some teams are happy using it doesn't really matter. It's a tool to give the illusion of metrics and estimation in an situation that is antithetical to it. Someone looked at the Agile manifesto -- specifically that part of "people over processes" -- and decided what was really needed was a strict process and a bunch of ceremonies to go with it! Can developers be happy with this? Absolutely. Are there plenty of developers unhappy with it? Also absolutely. I think that means we should still look at it critically.

theshrike79 2y ago
> Who is Scrum for? I would argue it's not for the developers The point of Agile/Scrum is to give the developers total peace from interruptions for a sprint of development. _Nobody_ can come and tell them to change the plans mid-sprint. If someone tries it's the Scum Master's job to tell them politely yet firmly to leave. If someone insists on changes, the Official Process says that they delete everything from the start of the sprint and start again - this is to give a clear price for interruptions. "You want this door over there instead of here where we designed it a month ago? Cool" burns down the house "Let's start over then". In 99.99% of the cases the request suddenly isn't THAT important and they can wait until the end of the sprint. BUT Scrum can only work if it has the buy-in of the whole company, you can't start it from the bottom down without some really big cojones.
- ath3nd 2y ago
  > The point of Agile/Scrum is to give the developers total peace from interruptions for a sprint of development. That part can be done without scrum. However, you are omitting that scrum also drags: Product Owners, sprint plannings, poker, daily standups, sprint demos. And you know what follows a sprint? Another sprint...And every time you miss that (self imposed, totally arbitrary) deadline, you fail. I simply don't understand why people do this to themselves.
  - theshrike79 2y ago
    If you keep missing "deadlines", you aren't planning properly. You can always take more work for a sprint, don't overcommit. Product Owner is just the one who prioritises the features the team implements, they're the one whose job is to know what the client wants and translate it to more technical terms and individual features. Sprint planning is just... planning what you'll do for the spring? Don't you usually plan your projects or do you just YOLO it? Standups can be just two lines of text in a daily Slack thread, but usually it's handier to just gather around and go through what you did and what you'll be doing. Demos are the best part of Scrum, you get to show what you accomplished to people who understand the client's requirements and you'll get immediate feedback for the next sprint. What kind of project model do you like if Scrum is The Devil Incarnate? Who takes care of customer requirements? Do you plan your time use? How do you teach other people in the company not to bother the team during implementation?
    - ath3nd 2y ago
      > Standups can be just two lines of text in a daily Slack thread, but usually it's handier to just gather around and go through what you did and what you'll be doing. Why? So a middle manager can create a report and submit it to their superiors? What if we omit all these reporting steps (and the middle manager) and gather when there is need to gather only? The team knows what they are doing, they can see it in each other's commits and each other's tickets. Who are you trying to inform/report to here? > What kind of project model do you like if Scrum is The Devil Incarnate? Kanban > Who takes care of customer requirements? Developers. You can also implement a feedback form and read it as a team. > Do you plan your time use Roughly. If we knew exactly what each thing entails to plan it in detail, that'd be waterfall. Or scrum, which is mini waterfalls one after another, never ending. That time you spend on planning, better spend it doing, and without a ceremony master. > How do you teach other people in the company not to bother the team during implementation? We told them once. If you have a problem when business types are barging in all the time and bothering your devs, maybe the business types can get a course in patience and basic manners?
      - theshrike79 2y ago

theshrike79 2y ago

> Who is Scrum for? I would argue it's not for the developers The point of Agile/Scrum is to give the developers total peace from interruptions for a sprint of development. _Nobody_ can come and tell them to change the plans mid-sprint. If someone tries it's the Scum Master's job to tell them politely yet firmly to leave. If someone insists on changes, the Official Process says that they delete everything from the start of the sprint and start again - this is to give a clear price for interruptions. "You want this door over there instead of here where we designed it a month ago? Cool" burns down the house "Let's start over then". In 99.99% of the cases the request suddenly isn't THAT important and they can wait until the end of the sprint. BUT Scrum can only work if it has the buy-in of the whole company, you can't start it from the bottom down without some really big cojones.

ath3nd 2y ago
> The point of Agile/Scrum is to give the developers total peace from interruptions for a sprint of development. That part can be done without scrum. However, you are omitting that scrum also drags: Product Owners, sprint plannings, poker, daily standups, sprint demos. And you know what follows a sprint? Another sprint...And every time you miss that (self imposed, totally arbitrary) deadline, you fail. I simply don't understand why people do this to themselves.
- theshrike79 2y ago
  If you keep missing "deadlines", you aren't planning properly. You can always take more work for a sprint, don't overcommit. Product Owner is just the one who prioritises the features the team implements, they're the one whose job is to know what the client wants and translate it to more technical terms and individual features. Sprint planning is just... planning what you'll do for the spring? Don't you usually plan your projects or do you just YOLO it? Standups can be just two lines of text in a daily Slack thread, but usually it's handier to just gather around and go through what you did and what you'll be doing. Demos are the best part of Scrum, you get to show what you accomplished to people who understand the client's requirements and you'll get immediate feedback for the next sprint. What kind of project model do you like if Scrum is The Devil Incarnate? Who takes care of customer requirements? Do you plan your time use? How do you teach other people in the company not to bother the team during implementation?
  - ath3nd 2y ago
    > Standups can be just two lines of text in a daily Slack thread, but usually it's handier to just gather around and go through what you did and what you'll be doing. Why? So a middle manager can create a report and submit it to their superiors? What if we omit all these reporting steps (and the middle manager) and gather when there is need to gather only? The team knows what they are doing, they can see it in each other's commits and each other's tickets. Who are you trying to inform/report to here? > What kind of project model do you like if Scrum is The Devil Incarnate? Kanban > Who takes care of customer requirements? Developers. You can also implement a feedback form and read it as a team. > Do you plan your time use Roughly. If we knew exactly what each thing entails to plan it in detail, that'd be waterfall. Or scrum, which is mini waterfalls one after another, never ending. That time you spend on planning, better spend it doing, and without a ceremony master. > How do you teach other people in the company not to bother the team during implementation? We told them once. If you have a problem when business types are barging in all the time and bothering your devs, maybe the business types can get a course in patience and basic manners?
    - theshrike79 2y ago