20160531 become the leading example spotify (kay korper en jacob vesterlund)
TRANSCRIPT
Become the leading example
Kay KorperJacob Vesterlund
How do you become the leading example?
Continuous ImprovementOrganisation
Quality
Today’s Playlist1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality
“The right music for every moment”
Quick facts
‣Over 75 million active users
‣Over 30 million subscribers
‣$3bn in revenue paid to rightsholders
‣Over 30 million songs
‣Over 2 billion playlists
‣Available in 59 markets
Today’s Playlist1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality
Continuous Improvement
Continuous Improvement‣Improving the individual
‣Improving as a company
Performance Development
1:1’sContinuous Feedback
Squad set upfor learning
Learning on the jobcontinuous feedback loop through:stand-ups, retro’s, right challenges, peer feedback etc.
Hack days / Hackweek
“It’s ok to fail“
Create an environment where innovative and passionate people can be their best.
“ How does such an environment look like?”
Today’s Playlist1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality
Alliance
Squad
“Small agile team designed to feel like a start-up”
•Cross-functional (most of them)•Own mission•Daily work•Autonomous
Alliance
Today’s Playlist1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality
Quality‣How do we deliver great quality?
‣How can we make sure we deliver with speed and quality?
‣How can make sure we can learn quickly through experimentation?
Stage 1: Quality work in squads‣The squad as a whole owns quality and the processes
around.
‣The squad decided when something is ready to be released.
‣Everyone participates in testing activities.
QA = Quality Assistance
Instead of acting as quality gatekeeper we want to help the team to deliver the software with the best possible quality.
Quality Assistance role‣Mentor and coach team member about quality at all stages of the
software development process.
‣ Involve the team in activities such as exploratory testing and regression testing.
‣Track and coordinate quality issues.
Continuous Delivery“Continuous Delivery is the ability to get changes of all types—including new features, configuration changes, bug fixes and experiments—into production, or into the hands of users, safely and quickly in a sustainable way.”
http://continuousdelivery.com/
Stage 2 : Continuous Delivery‣ Shorten release cycles.
‣ Automated deployments.
‣ Have the squads handle deployment and operations of their own code.
Test Automation‣ Good set of automated tests instead of doing just manual
testing is a must for continuous delivery.
‣ Have the automated tests run when a developer does a pull request, and when the code is merged instead of on nightly builds.
‣ Good automated tests enables good manual testing instead of repetitive manual regression testing.
Continuous Delivery (Now)Clients.
‣ Nightly builds for all employees.
‣ Two week release cycle for clients. (iOS, Android, Desktop).
‣ Automatic bump of dependencies.
Backend.
‣ Click to Deploy or Continuous Deployment
‣ Cycle time from code done to production servers is less than 23 hours (for 80% of commits)
‣ 90% commits are less than 400 lines.
Stage 3 : Experimentation‣Showing early prototypes to users.
‣A/B Testing.
“ Become the leading example”
1. Focus on learning
2. Create an environment where it safe to fail and fail fast. Failure is the most important step to success.
3. Involve the whole team in working with quality
4. Look at how you deliver your product, not only the product itself.
