TOP METRICS FOR AGILE              AGILENCR 2011                                       -Priyank                email: priy...
ABOUT US
MeasureMetrics
DEFINITIONS   Effort – the actual hours required to write the software.   Defect – the unaccepted functionality, hopeful...
METRICS FOR AGILE-   Efforts ,Top-Line, Velocity, Burn-Down,-   Cost-   Schedule, Time to market , Cycle time-   Defects- ...
MANIFESTO FOR AGILE        © Agile Alliance http://agilemanifesto.org
AGILE IS VALUE DRIVEN & ADAPTIVEConstraints       Requirement           Cost        Schedule                              ...
TOP-LINE, RELEASE BURN-UP                            Base Measure –                            • Total Number of Story    ...
VELOCITY   Velocity is relative measure of progress. It can be measured by Feature delivered in    an iteration   & It i...
BURN DOWN   Burn-down chart shows the estimated number of hours required to complete    the tasks of the Sprint.   And s...
BURN UP   Burn-up chart shows the amount of Accepted work (that work which has been    completed, tested and met acceptan...
SCHEDULE & COST METRICSMetrics can be derived from this –   Actual percent complete (APC)        = Complete Story Point/T...
VALUE REALIZATION (VELOCITY)   In the given example -   Budget = 100 $   Total SP = 120   Total Sprint = 12   After 4...
DEFECTS   Defect Removal Efficiency (DRE) is a base measure which we can tailor for    Scrum   DRE = E / ( E + D )     ...
TECHNICAL DEBTQuality can be best view through code ….Referencehttp://nemo.sonarsource.orgCopyrighthttp://sonarsource.org
FEW MORE BASICS QUALITY METRICS Technical debt Test case, Bugs Complexity Cyclomatic Complexity Violations Class, Me...
QUALITY METRICS -Referencehttp://nemo.sonarsource.orgCopyrighthttp://sonarsource.org
REFERENCES -   http://www.mountaingoatsoftware.com   http://www.agilemodeling.com   http://jamesshore.com/Agile-Book/as...
cdis.in
Top metrics for Agile by Priyank
Top metrics for Agile by Priyank
Upcoming SlideShare
Loading in...5
×

Top metrics for Agile by Priyank

2,530

Published on

Published in: Technology
1 Comment
3 Likes
Statistics
Notes
No Downloads
Views
Total Views
2,530
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
195
Comments
1
Likes
3
Embeds 0
No embeds

No notes for slide

Transcript of "Top metrics for Agile by Priyank"

  1. 1. TOP METRICS FOR AGILE AGILENCR 2011 -Priyank email: priyankdk@gmail.com © Cybercom Datamatics Information Solutions.
  2. 2. ABOUT US
  3. 3. MeasureMetrics
  4. 4. DEFINITIONS Effort – the actual hours required to write the software. Defect – the unaccepted functionality, hopefully identified by test case… through web search - A flaw in a component or system that can cause the component or system to fail to perform its required function. Schedule/Duration –the calendar time to get something done Cost – strongly correlated with effort, but duration also plays a role Size – something that can be counted/measured. Hopefully it is representative of effort. Plan/Estimated – our educated guess, is a probability. Actual – measured result. Quality – A delight
  5. 5. METRICS FOR AGILE- Efforts ,Top-Line, Velocity, Burn-Down,- Cost- Schedule, Time to market , Cycle time- Defects- Technical debt NEED OF THESE METRICS  Can help you  Understand about scrum performance  Drawing scrum progress, productivity, predictability  Analyze quality and value  Pain points, Improvement areas  Motivation & Performance  Simple Scrum (Time Boxed Continuous Iterations & Release)
  6. 6. MANIFESTO FOR AGILE © Agile Alliance http://agilemanifesto.org
  7. 7. AGILE IS VALUE DRIVEN & ADAPTIVEConstraints Requirement Cost Schedule Value Driven Plan DrivenEstimates Schedule Cost Features Predictive Agile - Adaptive
  8. 8. TOP-LINE, RELEASE BURN-UP Base Measure – • Total Number of Story Points • Total Number of Sprints Planned • Story Points planned at each sprint • Story Points completed in each sprint
  9. 9. VELOCITY Velocity is relative measure of progress. It can be measured by Feature delivered in an iteration & It is a measure of how much Product Backlog the team can complete in a given amount of time. Feature are usually initial stories and some times are set of feature with some non features.
  10. 10. BURN DOWN Burn-down chart shows the estimated number of hours required to complete the tasks of the Sprint. And similar to earned-value chart if you count the delivered functionality over time – Accepted work. It shows both the status and rate of progress (“velocity”) in a way that is both clear and easy to discuss.
  11. 11. BURN UP Burn-up chart shows the amount of Accepted work (that work which has been completed, tested and met acceptance criteria) And is shows the Scope - how much work is in the project as whole.
  12. 12. SCHEDULE & COST METRICSMetrics can be derived from this – Actual percent complete (APC) = Complete Story Point/Total Story Points Expected Percent Complete(EPC) = Number of completed iterations /number of planned iteration Base Measure – Planned Value (PV)= EPC x Budget • Budget Allocated for the project • Total Number of Story Points AC =Actual Cost in $ or soft-cost in Hrs spent • Total Number of Sprints Planned EV(Earned Value)=APC x Budget • Story Points planned at each sprint • Story Points completed in each sprint Schedule Performance Index (SPI) • Release variance – plan vs. actual = EV/PV, greater than 1 is good (ahead of schedule) Cost Performance Index (CPI) = EV/ AC, greater than 1 is good (under budget) Cost variance (CV) = EV – AC, greater than 0 is good (under budget) Schedule variance (SV)= EV –PV, greater than 0 is good (ahead of schedule) Value realization or Velocity.
  13. 13. VALUE REALIZATION (VELOCITY) In the given example - Budget = 100 $ Total SP = 120 Total Sprint = 12 After 4th Sprint where in First Sprint SP Accepted 9 out of 10, in Second Sprint 10 out of 10, in Third 10 : 10 & in Fourth 10:10 APC = 39/120 which is 0.325 , in % 32.5 EPC = 4/12 = 0.33 , in % 33.33 PV = 0.33 x 100 = 33 EV = 0.325 x 100 = 32.5 Lets assume is AC = 40 $ (or 400 Hrs, where 10 Hrs = 1 $) SPI = 32.5/33 = 0.98 CPI = 32.5/40 = 0.81
  14. 14. DEFECTS Defect Removal Efficiency (DRE) is a base measure which we can tailor for Scrum DRE = E / ( E + D )  Where E = No. of Errors found before delivery of the software and  D = No. of Errors found after delivery of the software @Scrum  E = No. of Errors found before delivery of the software in any iteration (@ during sprint execution )and  D = No. of Errors found after delivery of the software (@ Production ) Ideal DRE = 1. DRE less than 1 needs RCA
  15. 15. TECHNICAL DEBTQuality can be best view through code ….Referencehttp://nemo.sonarsource.orgCopyrighthttp://sonarsource.org
  16. 16. FEW MORE BASICS QUALITY METRICS Technical debt Test case, Bugs Complexity Cyclomatic Complexity Violations Class, Methods, Duplication, Comments etc..
  17. 17. QUALITY METRICS -Referencehttp://nemo.sonarsource.orgCopyrighthttp://sonarsource.org
  18. 18. REFERENCES - http://www.mountaingoatsoftware.com http://www.agilemodeling.com http://jamesshore.com/Agile-Book/assess_your_agility.html http://java.net/projects/hudson/ http://www.sonarsource.org/ http://docs.codehaus.org/display/SONAR/Metric+definitions https://wiki.rallydev.com http://www.infoq.com/
  19. 19. cdis.in
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×