Hi Russel,
they represent an arbitrary metric to evaluate the Effort required by the Team to implement that User Story: shortly, it's part of the stuff that should be required by any Agile Development Process Framework, like the one adopted by Moodle.
HTH,
Matteo
Hi,
It would be good to have it clearly documented in dev docs, for everybody to be able to understand exactly what it means, and/or it's used for.
Some questions examples : Is it better to have 40 than 20? What does it involve?
Séverin
This was more the thrust of the question. It's not used on many bugs I've seen in Moodle, or commonly talked about in the community so I don't know how to read or use it in context of the tracker. It's fine to say it's an agile measure. But to go with that it's important to describe how it fits into the process.
For example 'assigned to' is clear what it is, but the use of it has changed recently with Unassigned being used rather than moodle.com for items not being worked on. I'm trying to suggest that the specific use process is as important to know as the objective item itself.
Try this link https://confluence.atlassian.com/display/GH/Story+Point
if it makes sense let us all know.
Hi, Guys.
We're using Story Points as a way of measuring the relative scale issues we are about to work on in Scrum sprints. This is purely an internal metric so we can estimate how much work a team of developers can take on in a single sprint.
I'll have to look at whether we can avoid bothering people with emails whenever we set the Story Points value.
