Add context for story point ranges #21171
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While I haven't seen this exact story point mapping to expected completion time, it intuitively makes sense from an Agile/iterative dev perspective, and accounts for e.g. longer tasks being disproportionately more uncertain than shorter tasks.
Let me know if I got the rationale correct here, as spelling that rationale out feels like a useful thing to have in the handbook, particularly for engineers coming from environments where story points might've been converted more linearly to expected level of effort.