Scrum as mini waterfall isn’t supposed to happen, but it usually does. The idea is everyone can help the people will are currently busy
The problem is test and build can’t do much to help the system analysts; the analysts and testers can’t help build because they don’t usually know how to code, so all that happens is everyone tests when build is done
As an analyst I don’t do any testing because I had a bad team leader in a past job as a function tester which soured me on the job, so it’s pretty much mini waterfall to me
the mini waterfall is kind of the intention of a sprint. The whole idea is to reduce the huge waterfall and its horrible surprises at the end when it is way too late. Have those surprises early by doing small waterfalls. But everybody is splitting it wrong so all the small waterfalls have no outcome until the whole thing is done, just like you do without sprints.
Yeah, great iteration is the feature. But the other side where we’re expected to all help out each other, to keep everyone busy all the time doesn’t work
I agree but that has nothing to do with scrum. It does not say how busy everyone has to be. Things like these are left for the team to decide. If you felt like you had to be more busy, then someone among you probably pushed it.
In fact i prefer a bit of slack time so people can react to incidents better. Imagine a 100% busy highway. Not nice. And then you need to spontaneously deliver something from A to B, using that highway -> there will be a traffic jam and everything works terribly.
Have a bit of slack here and there so the spontaneous delivery does not mess up the flow -> much more effective and everyone is happier too.
Scrum as mini waterfall isn’t supposed to happen, but it usually does. The idea is everyone can help the people will are currently busy
The problem is test and build can’t do much to help the system analysts; the analysts and testers can’t help build because they don’t usually know how to code, so all that happens is everyone tests when build is done
As an analyst I don’t do any testing because I had a bad team leader in a past job as a function tester which soured me on the job, so it’s pretty much mini waterfall to me
the mini waterfall is kind of the intention of a sprint. The whole idea is to reduce the huge waterfall and its horrible surprises at the end when it is way too late. Have those surprises early by doing small waterfalls. But everybody is splitting it wrong so all the small waterfalls have no outcome until the whole thing is done, just like you do without sprints.
Yeah, great iteration is the feature. But the other side where we’re expected to all help out each other, to keep everyone busy all the time doesn’t work
I agree but that has nothing to do with scrum. It does not say how busy everyone has to be. Things like these are left for the team to decide. If you felt like you had to be more busy, then someone among you probably pushed it.
In fact i prefer a bit of slack time so people can react to incidents better. Imagine a 100% busy highway. Not nice. And then you need to spontaneously deliver something from A to B, using that highway -> there will be a traffic jam and everything works terribly. Have a bit of slack here and there so the spontaneous delivery does not mess up the flow -> much more effective and everyone is happier too.