Abstract: Do you have measurement dysfunction on your program? Are you trying to measure teams and extrapolate each team’s status to the program? That doesn’t work. Teams have personal status, and you can’t add them together to understand the program state. You can use a handful of program measurements that help everyone understand where the program is and where it’s headed.
Instead of trying to “scale” measurements, take a new approach. In this talk, Johanna will share program measurements—qualitative and quantitative—that show everyone the program state.
Learning Outcomes: - 1. Measure what you want to see. Why this principle is so effective.
- 2. Why you want to measure completed features
- 3. Specific quantitative measures: product backlog burnup, time to releasable deliverable, release frequency, program cumulative flow, build time, product measurements
- 4. Specific qualitative measures: obstacle report, program work in progress
- 5. What you should never measure.
Attachments:
