Italy is not a huge country, but the weather from the top to the toe of this boot will vary pretty dramatically throughout the year. Plus, with the long coastlines and mountain ranges, the temperature can change in a matter of minutes as you go from town to town.
Velocity can be a really great tool to help in identifying problems with a team as far as blockers, bugs and problems with the practices within the team. Without looking at official definitions here's my definition of what velocity is: Velocity is an abstract measure of a teams productivity towards delivering features over time. We measure velocity by working out an average number of agile points delivered sprint-on-sprint and dividing the total number of agile points delivered over X sprints by the number of sprints it has taken to deliver them. So velocity is: Velocity = Total number of Agile Points Delivered / Number of Sprints. Let's break the velocity statement down. When we refer to velocity as an âabstract measureâ, what do we mean? To answer this question, we need to understand what makes up velocity. We said earlier it's an average of the number of agile points delivered.
A few years ago in Dr. Dobbâs Journal I wrote about estimating on agile development projects. In that article I discussed burndown charts and how to extend them to show an estimation range. The basic observation is that there is really two velocities exhibited by a team, the gross velocity and the net velocity. The gross velocity which is the amount of work they complete in an iteration, which is what a regular burndown chart shows. The net velocity is the change in the amount of work still to do, which is the amount of work completed in an iteration less the added amount of functionality that iteration.