News for hackers. Stuff that matters.
Re:I wrote, “Scrum is a cancer,” and the Internet had though... by systems on Wednesday August 30, 2023 @01:28PM (#37325666)
I am curious, how did management respond when the progress slowed

did they revert back to the old method, did it deteriorate so fast there was no way to stop it, was the team not very important

what happened ?

Re:I wrote, “Scrum is a cancer,” and the Internet had though... by dylan604 on Wednesday August 30, 2023 @01:44PM (#37325951)
this would be an example to be studied in future classes of business school if this resulted in a change like you would hope for. otherwise, it's business as usual, and no, the changes you seek would not happen.

i'm obviously turning this into a hypothetical

Re:I wrote, “Scrum is a cancer,” and the Internet had though... by palata on Wednesday August 30, 2023 @02:21PM (#37326584)
> how did management respond when the progress slowed

Rule number 1: management is never wrong. The progress did not slow down.

Re:I wrote, “Scrum is a cancer,” and the Internet had though... by CipherThrowaway on Wednesday August 30, 2023 @02:23PM (#37326602)
Standard playbook in this situation is everyone involved saves face by blaming the team who were driven out, then they adjust to the new normal and everyone forgets they were ever able to build and ship software.
Re:I wrote, “Scrum is a cancer,” and the Internet had though... by lpapez on Thursday August 31, 2023 @11:49AM (#37339099)
Their view was that there was no problem, but rather that the new process was an improvement. I am not joking.

They said that we didn't measure the work before, so they had no visibility into how much the team does. But after introducing scrum, they were very happy to see that the team usually delivered around 20 story points per sprint, while the other teams in the company did around 10.

In my view, if we estimated tickets in old process as we did after introducing scrum, we would have been delivering around 60 points in two weeks through old process.