jgs SER 516 Software Agility Lecture 24: STAN and Velocity Dr. Javier Gonzalez-Sanchez [email protected] javiergs.engineering.asu.edu | javiergs.com PERALTA 230U Office Hours: By appointment
jgs 516 00010000 Announcements § Final Exam – April 22 during lecture time § Final Project (one more sprint and 3 “extra” activities) – due April 20 § Academic Integrity
jgs 516 00010000 Tools 1. Download and install STAN https://stan4j.com/download/ Stand alone or Eclipse plug-in I need help: http://download.stan4j.com/app/stan-app-help-2.2.pdf
jgs 516 00010000 Tools For your submissions (sprint 1, 2, 3, 4) { § Review your “Robert C. Martin” metrics: § Ca, Ce, I, A, D. § Review “Violations” report § Review “Distance” plot § Review Dependency / Composition Graph § What can be improved? }
jgs 516 00010000 Violations Report around 20 is perfect, up to 50 is still fine, up to 100 is critical, above 150 is really bad, and more than 250 is !
jgs 516 00010000 Estimation § Do not overthink and estimation (Good-enough criteria). § Do not inflate numbers – wasteful and dangerous behavior. § Realistic Estimation Vs Estimate inflation.
jgs 516 00010000 Velocity § Do not include partially completed items § It measure output (size of what was delivered) not outcome (value of what was delivered), i.e., for velocity, complete 1 of size 8, is the same that complete 8 of size 1. § It is planning tool not team diagnostic metric.
jgs 516 00010000 To Do Using your Burndown charts from submissions (sprint 1, 2, 3) { § Calculate your velocity } § Estimate Sprint 4 § Compare Estimation and velocity § Do they match?
jgs SER 516 Software Agility Javier Gonzalez-Sanchez [email protected] Spring 2021 Disclaimer. These slides can only be used as study material for the class SER516 at ASU. They cannot be distributed or used for another purpose.