Hello , I have created Issues and mapped them in a sprint against a project . while creating Story it asks for Original Estimate and Remaining Estimate which is a manual input . Also there is another field "Story Point" which accepts a numeric value . What does this numeric value indicate ? I want to know what should be the rationale of that numeric value and its use in available gadgets on project start dashboard .I would appreciate kind and prompt response .
I'll add one more: http://scrummethodology.com/scrum-effort-estimation-and-story-points/. Google it and you will find hundreds. Thousands.
Story Points is related to estimation. You should really read up on it before deciding.
We on our part now uses story points for estimation of User Stories, Improvements and bugs (found itside of the sprint). During sprint planning these issues are broken down into sub-tasks and estimated in hours.
Got the idea now and really appreciate prompt response . I would like to rephrase it , that at first I was taking this like a conventional PMBOK based PM where we tag everything in hours . This is way different now as it is more of an abstraction to quanity a story complexity . We could use fibonacci series and once we run multiple sprints we will have an idea how our team gets it done . We can take a sprint as baseline and then can re-iterate and update baseline accordingly . Its more of a planning technique using Story Point . Thanks guys
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs