To get a decent view on the deadline of a project, we should measure the velocity of the project. We can do this by adding the actual number of hours of all completed stories.

If you have no experience with a certain team of people estimating can be hard, but still it's valuable to think about the expected velocity up front.

So for each iteration we need to fill in an estimated velocity. Currently we fill in a field manhours on the iteration. I would like to change this field to "Estimated Velocity" and store it as an integer which represents story points.

I prefer to interpret a story point as one optimal hour of work, without any interumptions like phone calls, email answering or meetings.

After the iteration is finished the velocity is calculated by adding all initial estimates of the stories that are completed. We should not use the actual hours, but learn from the wrong estimate. This changes the requirements of the workflow. Currently all stories should be completed to be able to close the iteration.