You know that the sprint goal is not a number: not story points, not a count of features, not a velocity? It's supposed to be an outcome. @mediafinger
It's a symptom of a (so-called) feature mill to mistake the load for the goal.
If ever the sprint goal is "complete all these stories" you know that you've crossed a line, and it's time to retrospect.
If ever the sprint goal is "complete all these stories" you know that you've crossed a line, and it's time to retrospect.
I've seen this most in organizations that don't really have cross-functional teams, but functional or component
It doesn't make sense to have an outcome in mind when you won't be (and can't be) releasing until other pieces/functions finish.
Singh's inevitable avoidance; dropping the important parts of the process which don't fit the current dysfunctions.
Which wouldn't be so bad as a very short term stopgap, but is nonsense if it becomes a permanent feature.. or is believes to be what agile or scrum intended.
No agile method is intended to create a dystopian feature mill. But some DFMs have tried very hard to adapt agile toward that goal.
