Engineer, Immigrant, Entrepreneur. Investor, Vegan. Managing Director @ Techstars NYC. Running and yoga. I write about startups and venture: http://alexiskold.net
Sometimes there is new information (e.g. from customer feedback) that shows up and suggests that something we accepted into the sprint should be re-thought. In those cases, it is better to stop and re-asses than to spend time building the wrong thing.
Of course, if this happens every sprint, that seems wrong and you need to improve the decision -making that goes into planning the sprint. But "should not be allowed" seems unnecessarily categorical and plain unrealistic, in my experience.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Love the emphasis on "Once the features are selected they are LOCKED for this sprint. You can’t add new features in the middle of the sprint."
Nothing gets my goat like a sudden scope change in the middle of a sprint.
yeah its ridiculously stressful and should not be allowed.
I agree that would be ideal.
Sometimes there is new information (e.g. from customer feedback) that shows up and suggests that something we accepted into the sprint should be re-thought. In those cases, it is better to stop and re-asses than to spend time building the wrong thing.
Of course, if this happens every sprint, that seems wrong and you need to improve the decision -making that goes into planning the sprint. But "should not be allowed" seems unnecessarily categorical and plain unrealistic, in my experience.