Metrics-driven development
Formal Metadata
| Title | Metrics-driven development |
|
| Title of Series | |
| Part Number | 66 |
| Number of Parts | 173 |
| Author | |
| License | You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal and non-commercial purpose as long as the work is attributed to the author in the manner specified by the author or licensor and the work or content is shared also in adapted form only under the conditions of this license. |
| Identifiers | |
| Publisher | |
| Release Date | |
| Language | |
| Production Place | Bilbao, Euskadi, Spain |
Content Metadata
| Subject Area | |
| Genre | |
| Abstract | Lynn Root - Metrics-driven development
At Spotify, my team struggled to be awesome. We had a very loose
understanding of what product/service our squad was responsible for,
and even less so of the expectations our internal and external
customers had for those services. Other than “does our Facebook login
work?”, we had no understanding of how our services we’re responsible
for were doing. How many users actually sign up or log in with
Facebook? How many users have connected their Spotify account with
their Uber account? Do folks even use Spotify with Uber?
With a 2-month challenge period, my squad and I focused inward to
establish those unanswered questions and to establish feedback loops
and always-on dashboards. This talk will tell the story of how we
chose which metrics are important for us to focus on, what
technologies we have used and are using, and how we’ve iterated over
our feedback loops to fine-tune what metrics we care about. |
|
| Keywords | |