Skip to content

Instantly share code, notes, and snippets.

@bleathem

bleathem/Story-point-interpretation.md

Created May 6, 2016 16:47
Show Gist options
  • Save bleathem/dca0d8132a375b9a91501e74151adfcf to your computer and use it in GitHub Desktop.
Save bleathem/dca0d8132a375b9a91501e74151adfcf to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Story-point-interpretation.md
  • 2 : Trivial change (version bump, fix typo etc) No unknowns
  • 3 : Larger trivial change (small documentation update, one-liner code fix etc). No unknowns.
  • 5 : Small code change, very limited in scope across multiple components. No unknowns.
  • 8 : Large code change, limited to 1-2 components. No unknowns.
  • 13 : Large code change, spread across multiple components. No unknowns.
  • 20 : Large code change, not sure about the full scope of the required changes yet. There may be subtasks that I cannot populate yet because I don't know the full scope of the task.
  • 40 : Large code change, potentially very large. Full scope of the task is unknown and the unknowns could be large in the own-right.
  • 100: Potentially huge unknown code changes required. The full scope of the task is not known at all / requirements very unclear. The potential unknowns could be feature-sized.
@lgriffin
Copy link

Really good to see this and have it tangible and somewhat bounded, great job!

My one comment would be as a team to decide our upper bound before splitting e.g. anything above an X could be a candidate to split and breakdown. This link is relevant for helping with a split: http://agileforall.com/wp-content/uploads/2012/01/Story-Splitting-Flowchart.pdf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment