April 2015
Beginner
408 pages
10h 1m
English
Content preview from Scrum For Dummies
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,







O’Reilly covers everything we've got, with content to help us build a world-class technology community, upgrade the capabilities and competencies of our teams, and improve overall team performance as well as their engagement.
I wanted to learn C and C++, but it didn't click for me until I picked up an O'Reilly book. When I went on the O’Reilly platform, I was astonished to find all the books there, plus live events and sandboxes so you could play around with the technology.
I’ve been on the O’Reilly platform for more than eight years. I use a couple of learning platforms, but I'm on O'Reilly more than anybody else. When you're there, you start learning. I'm never disappointed.
I'm always learning. So when I got on to O'Reilly, I was like a kid in a candy store. There are playlists. There are answers. There's on-demand training. It's worth its weight in gold, in terms of what it allows me to do.
Chapter 21
Ten Key Metrics for Scrum
In This Chapter
Avoiding traditional and ineffective metrics
Making the most out of the available data
Optimizing the value of scrum
With scrum, metrics can be powerful tools for planning, inspecting, adapting, and understanding progress over time. Rates of success or failure can let a scrum team know whether it needs to make positive changes or keep up its good work. Time and cost numbers can highlight the benefits of agile projects and provide support for an organization’s financial activities. Metrics that quantify people’s satisfaction can help a scrum team identify areas for improvement with customers and with the team itself.
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
Double work agile is the practice of management expecting to see traditional status reports and meetings in addition to scrum artifacts, events, and appropriate metrics. This is one of the top pitfalls of scrum projects. Management is looking for one thing while teams are trying to do another. As a result, decisions are made based on the wrong information, teams burn out from doing double the work, and the benefits of ...