nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Story Points

Aamer Inam: M-3521

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 .

Accepted answers

Ivar

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.

All comments

Nic Brough -Adaptavist-

Start with the docs - https://confluence.atlassian.com/display/AGILE/Story+Point

The rationale for using it is down to whether you want to work that way or not.

Ivar

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.

Aamer Inam: M-3521

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