Agile Program Management: Measurements to See Value and Delivery

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 statuses, and you can’t add them together to understand the program state. But 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. Join Johanna Rothman to learn to use and share quantitative and qualitative program measurements that show everyone the program state. It starts with measuring what you want to see. This simple principle is so effective because it takes your needs into account before you decide on a metric to use. Next, we'll look at the scope. We’ll talk about why you want to measure completed features and how measure at this level can bring clarity to your project. With needs and scope defined, we’ll explore specific quantitative measures such as product backlog burnup, time to releasable deliverable, release frequency, program cumulative flow, and build time. We’ll also spend time on qualitative measures such as obstacle reports and program work in progress. Come discover what you should never measure and learn how to avoid the pitfalls of worthless metrics.