You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
- 54I agree and I personally find the idea of 'committing' in scrum to be inefficient. You are forced to structure your work around an arbitrary timeline in order to make this work. Effectively you end up with a bin packing problem. The only realist way for everyone to finish what they commit every Sprint is to commit to less than what they can accomplish in an average Sprint. I like to use the Sprint schedule for reassessing direction and house-keeping. Nothing more.JimmyJames– JimmyJames2016-03-23 18:56:01 +00:00Commented Mar 23, 2016 at 18:56
- 29Which is why scrum.org changed their terminology from "commitment" to "forecast" in 2011.Steve Jessop– Steve Jessop2016-03-23 23:34:35 +00:00Commented Mar 23, 2016 at 23:34
- 6I like this answer, but I'd add that sprints with a time-based forecast can be a useful way to balance the velocity-based development process with external time-based business needs. If you can maintain a reputation for reasonably reliable time-based forecasts for sprints, you can use that to communicate your plans to business owners and justify the timing and prioritization of tasks based on business priorities. Of course, if your forecast has never been right in 18 months, your reputation is worse than the weatherman. Whether it's worth improving your forecasts or giving up is up to you.Zach Lipton– Zach Lipton2016-03-24 01:58:12 +00:00Commented Mar 24, 2016 at 1:58
- 5I've worked for a company which was succeeding while never completing the planned content of a sprint, and we DID switch to Kanban instead. That made everything a lot smoother.Carson63000– Carson630002016-03-25 02:48:10 +00:00Commented Mar 25, 2016 at 2:48
- 1@SteveJessop, wow, they sure haven't publicized that very well. None of the "scrum masters" I've worked around for the past five years have ever mentioned it. Maybe they intentionally haven't mentioned it.Kyralessa– Kyralessa2016-04-14 18:23:18 +00:00Commented Apr 14, 2016 at 18:23
| Show 4 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you