team sprint velocity

The "number of story points that a team can complete in a sprint(2 weeks)" will treat as a Team's Sprint Velocity .

Thanks
Siva

Hi Mayan,

Velocity - Velocity is a measure of the amount of work a Team can tackle during a single Sprint and is the key metric in Scrum. Velocity is calculated at the end of the Sprint by totaling the Points for all fully completed User Stories. Upon completion you will: Know how Velocity is calculated.

For additional info please go through this link.

www.scruminc.com/.../

There are multiple ways to determine this. I will give you what we have done in past. We followed SAFe Agile and it recommends us to have a base line story which needs 1 day of dev/ test effort as 1 point story (This can change based on your skill set and knowledge you have on Appian and the application you are planning to do). Since we have 10 working days for sprint, We used to take 8 points of work for each developer/tester in our team. We used to groming a week in advance so we never counted points for BA. As i said this is one way. It always depends on team composition and complexity of things you ae doing.we used to keep points for uncertainity of stories too.

Hi,

Sprint velocity is the amount of work that can be handle by the team during a single sprint.
It will be calculated at the end of each sprint by adding all the points of totally completed US's.
This is will be tracked using Burn down charts throughout the Sprint.

You can start my pointing stories and seeing how many your team gets through in 1-2 sprints. Once you see how the team works together, you will be able to average the past completions and have a good estimate of future velocity.

The important factor is to point stories based on complexity. A common pitfall is associating some sort of mapping of time to points (e.g. 3 pts = 1 day, 5 pts = 2, etc.). This defeats the whole purpose of story pointing.

Your first sprint will most likely be a calibration period. You'll point user stories and make a estimate of how much can be done in Sprint 1. Usually you will be over or under what was estimated. For Sprint 2, so long as you story point the same way as you did for Sprint 1, you can then make a calibration to project your velocity based on Sprint 1's performance.

For example, let's say you story pointed all of your user stories and made a conservative guess for Sprint 1 that your team can complete 45 pts. Let's say at the end of Sprint 1, your team performed really well and ended up pulling additional stories in and got you to 60 pts of total work complete. For Sprint 2 you can update your team velocity to 60 and pull in 60 points worth of work. You then take a look at the outcome of Sprint 2 and calibrate your velocity estimate as needed for Sprint 3. Eventually, if your team remains consistent and points consistently, your velocity number will stabilize and you can build more confidence in determining your team's velocity for future sprints.