Slide 1

Slide 1 text

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

Slide 2

Slide 2 text

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

Slide 3

Slide 3 text

jgs Previously …

Slide 4

Slide 4 text

jgs 516 00010000 Deliverables § Source Code § Document (PB, review retrospective, Burndown chart) § Class Diagram § Structural Metrics § Velocity § Self-Evaluation. What I did in this project? § Peer-evaluation – confidential

Slide 5

Slide 5 text

jgs Stan : Structure Analysis For Java Final Project (Part B)

Slide 6

Slide 6 text

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

Slide 7

Slide 7 text

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? }

Slide 8

Slide 8 text

jgs 516 00010000 Metrics § Tangled § Abstractness § Instability § Cout aka Ce (efferent) § Cin aka Ca (afferent) § Distance

Slide 9

Slide 9 text

jgs 516 00010000 Example of Violations Report

Slide 10

Slide 10 text

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 !

Slide 11

Slide 11 text

jgs 516 00010000 Common Problems § Big Fat Models § Spaghetti Controllers § Uninjected Views (Dependency injection)

Slide 12

Slide 12 text

jgs Velocity Final Project (Part C)

Slide 13

Slide 13 text

jgs 516 00010000 Estimation and Velocity Estimation hours Planner Poker (story points) Velocity Story points Sprints =

Slide 14

Slide 14 text

jgs 516 00010000 Estimation and Velocity Estimation hours Planner Poker (story points) Velocity Story points Sprints =

Slide 15

Slide 15 text

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.

Slide 16

Slide 16 text

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.

Slide 17

Slide 17 text

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?

Slide 18

Slide 18 text

jgs 516 00010000 Questions

Slide 19

Slide 19 text

jgs 516 00010000 Reference § Agile Software Development: Principles, Patterns, and Practices. Robert C. Martin. Prentice Hall. 2006. Chapter 30. § Essential Scrum – Chapter 7.

Slide 20

Slide 20 text

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.