...
- Create a new issue in Jira.
Write Capture specifications in the description.
Info Be sure the description includes the complete requirements for the work, tips or guidance that would help someone get started or complete the work, and a clear description of what done and good look like. Update the story points to reflect the value of the work.
Info title Estimating story points Estimating tickets:
The team estimates tickets using the Story point method. If you find that you are unable to estimate a ticket, stop and go evaluate the work involved in the ticket. If you still find that the ticket is larger than 21 story points, then the scope of the ticket is too large. Break the ticket up into pieces that you can estimate.
Here are some articles that can help you understand the methodology:
- https://www.atlassian.com/agile/estimation
- http://www.agilebuddha.com/agile/agile-estimation-8-steps-to-successful-story-point-estimation/
- https://agilevelocity.com/scrum/5-common-story-point-estimation-mistakes/
First Approximation of mapping hours to Story points*
- 1,2,3,5,8,13,21
- 1 point - approx 1 hour
- 2 - 2 hours
- 3 - half a day
- 5 - 1 day
- 8 - 3 days
- 13 - 1 week
- 21 - 2 weeks of work
* This is an approximation only. There is no intention to story point on the basis of hours. That defeats the purpose. This is only here to help describe how more points = more effort.
- Label the issue "proposed". This will queue the issue up for review by the program manager before being released for bounty.
Related articles
...