Agile Software Development (ASD)
Project Velocity & other
Metrics/Measures
Agile Software Design and Development Principles
Prof. Daiwat Vyas
B.TECH SEMESTER 6TH CSE
Project Velocity
• In agile software development, project velocity is a measure of the amount of
work completed by a team over a certain period of time.
• It is calculated by adding up the number of story points completed in each
iteration, or sprint, and dividing by the number of sprints.
Project Velocity
• Let's say that a team is working on a project with a total of 100 story points.
• The team has decided to work in two-week sprints, and in the first sprint they
complete 20 story points.
• In the second sprint, they complete 25 story points. In the third sprint, they
complete 18 story points.
Project Velocity
• To calculate the team's project velocity, we add up the number of story points
completed in each sprint:
• 20 + 25 + 18 = 63
• Then, we divide by the number of sprints:
• 63 / 3 = 21
• So, the team's project velocity is 21 story points per sprint. This means that, on
average, the team can complete 21 story points of work in a two-week sprint.
Project Velocity
• Project velocity is used in agile software development to help teams plan their
work and estimate how much work they can realistically complete in a given time
frame.
• By tracking project velocity over time, teams can also identify trends and make
adjustments to their process to improve their efficiency.
Other Metrics/Measures
• Agile software development approach emphasizes on continuous improvement
and flexibility, it's important to measure project progress and success using
metrics that align with its principles.
• Here are some common metrics to evaluate a project carried out using agile
software development approach:
• Burndown chart: A burndown chart is a visual representation of the progress of
the project during a sprint. It shows the amount of work remaining versus the
time left in the sprint and can be used to adjust the team's approach or resources
if the project is not on track.
• Sprint Retrospective: The sprint retrospective is a meeting held at the end of
each sprint where the team reflects on what went well, what didn't go well, and
what they can do to improve. The results of the retrospective can be used to
adjust the approach in future sprints.
Other Metrics/Measures
• Here are some common metrics to evaluate a project carried out using agile
software development approach:
• Customer satisfaction: Agile software development approach emphasizes on
delivering value to the customer. Measuring customer satisfaction can provide
insights into whether the product being developed is meeting the customer's
needs.
• Team satisfaction: Agile software development approach places importance on
the team's satisfaction and productivity. Measuring the team's satisfaction can
provide insights into whether the team is working well together and is motivated
to achieve the project's goals.
Other Metrics/Measures
• Here are some common metrics to evaluate a project carried out using agile
software development approach:
• Cycle Time: Cycle time measures the time taken from the start of a work item to
its completion. It can be used to track the team's efficiency and identify
bottlenecks in the process.
• Quality: Quality metrics measure the number of defects in the product. Agile
software development approach emphasizes on delivering a high-quality
product, and measuring the number of defects can provide insights into the
effectiveness of the team's processes and practices.
