Measuring Velocity, Schemes and Mind Maps of Technology

Download Measuring Velocity and more Schemes and Mind Maps Technology in PDF only on Docsity!

SWEN-610 Foundationsof Software Engineering Department of Software EngineeringRochester Institute of Technology

Measuring Velocity

Velocity is the last piece of the Scrum process.

At this point in the course, you've seen all of theScrum processes, except for measuring velocity.
Velocity is what determines the maximum storypoints to be included in the next sprint.
Recall our Sprint planning lesson: 2 S (5) S (13) S (21) S (3) S (3) ProductBacklog Sprint Backlog S (2) S (13) S (5) The velocity is used to determinehow many (and which) stories toadd to the Sprint Backlog. In thiscase, the team's velocity was 25story points.

Velocity is specific to one team working on oneproject.

This assumes that sprint length and teammembership remain consistent.^ • If either of these two change, then velocitymeasurement must start over with a new runningaverage.
Velocity is only measured for a single project,single team.^ • Story points are level of effort estimates

Story points are determined by the team, for theteam - Thus you cannot compare velocity's between teams
Management cannot set a team's velocity. 4

Velocity is not the same as the team's overallcapacity.

Velocity is only a measure of effort for working onuser stories.^ • It does not include company meetings, emailcommunication, small "outside" tasks

For class, it does not include most pre- and post-class activities
What about these issues?^ • Holidays or vacations - Members given large, outside tasks
Normally these issues can be ignored beingsmoothed out by the averaging process.
In extreme cases, the team can make adjustmentsto the calculated velocity usually by lowering it. 5