3 ms·
> Everyone seems to boil down to...simply trust the process In older days business would say what they wanted, engineering would give a time estimate, and then
by Mc91 5y ago
> Everyone seems to boil down to...simply trust the process
In older days business would say what they wanted, engineering would give a time estimate, and then we get to work with a deadline both commit to - the waterfall method.
With scrum, business says what they want when they want (although preferably at the beginning of a quarter), but no real estimates are done and thus no deadlines, work comes in and is prioritized. This entails the micromanagement of daily standups, stories needing to be broken into bite-sized sprint length segments etc.
Except we still wind up with deadlines, sometimes not even communicated until the team is into the work already. So it is the worst of all worlds - engineering gives no estimates, micromanagement of daily standups and features needing to be broken into small sprint length problems, plus, what was supposed to go away but has not - deadlines - not estimated by engineering, but handed down as fiat from somewhere in management. This might not be "real scrum", but it is how it works in more than one company that is supposedly working in the agile/scrum method.
- sodapopcan 5y agoRight, that’s not scrum. That’s picking aspects of it, doing them wrong, and calling it scrum. Just because that’s what many business chose to do doesn’t mean that it has no value of done “right”. For example, standup is not a “prove that you got something done yesterday” meeting, it’s about making a plan for the day. Many businesses treat as such, but that’s just wrong. And toxic.
- gedy 5y agoAgreed. The issue I've frequently run into is business side thinking "we need all this, and by this date". Then trying to apply "agile" on top of this assumption. It never works out with that mindset.