search

software-project / scrum-pm

Scrum PM is a plugin for Redmine ticket management system. It adds Scrum items like backlog, dashboard and others.
www.software-project.eu/EN/scrumpm
126 stars 47 forks source link

Points linked to issue estimated time #48

Closed bondsbw closed 14 years ago

bondsbw commented 14 years ago

I think it's more useful to have story points linked to the sum of estimated time in contained tasks. Now, they are separate things and a story can easily have 1 point but 50 hours worth of tasks, or 50 points and 1 hour worth of tasks.

bureku commented 14 years ago

It would be easy if it's 1SP is equivalent to 1 hour. In cases where 1SP is not 1 hour, it would be difficult to implement. Unless somehow you can define the settings for each project.

bondsbw commented 14 years ago

Yes, I obviously did not understand the point of SPs.

But with that said, two issues come to mind: 1) I don't see a good way to add velocity, or to relate that to actual time. 2) SPs and issue time estimates do not work together. Maybe this is not a bad thing, I really don't know.

michalhryncewicz commented 14 years ago

As far as I know SP's and time estimation are two different things.

software-project commented 14 years ago

I disagree. Story points are one of the basic things in Scrum. First of all the name: Story Point, not story time, hours or such. That are abstract values that relates to each other. It is because our time estimates are crapy and I have never met a develper who estimates correctly. So when we estimate abstract values its easier for us. There is no preasure to do something in exactly 2 hours or other way: it has 5h estimation I've done it in 2h so I have 3h of free time. After a sprint you can do velocity planing and that will give you some kind of time representation of SP. Check out Scrum and XP for trenches on infoq