Become the Leading Example - Innovate Your Quality with Compassion Presentatie: Kay Korper & Jacob Vesterlund, Spotify (QA Lead & Technical Tester) 31 mei 2016, Nyenrode Business Universiteit "Rules are a good start, but break them when needed”. Dit is wat Spotify heeft geleerd door naar haar eigen organisatie te kijken. Hierdoor veranderde de rol van Scrum Master naar Agile coach en de gehele cultuur binnen Spotify. Dit alles heeft ervoor gezorgd dat projecten sneller opgeleverd worden, medewerkers meer gemotiveerd werken en mede daardoor de kwaliteit van proces en product van hoog niveau is. Op dit moment wordt Spotify -wereldwijd- gezien als leading example op het gebied van efficiënt software ontwikkelen. Inmiddels volgen vele bedrijven dit voorbeeld (of delen ervan). Benieuwd wat u hiervan kan toepassen in uw eigen organisatie? En wilt u leading example worden binnen uw sector? http://www.nyenrode.nl/Education/MBA/Modular-Executive-MBA/Pages/Seminar-Become-the-Leading-Example.aspx

1. Become the
leading example
Kay Korper
Jacob Vesterlund

2. How do you become
the leading example?
Continuous Improvement
Organisation
Quality

3. Today’s Playlist
1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality

4. “The right music for every moment”

5. 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

12. Today’s Playlist
1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality

13. Continuous Improvement

14. Continuous Improvement
‣Improving the individual
‣Improving as a company

17. Performance Development
1:1’s
Continuous
Feedback

20. Squad set up
for learning

21. Learning on the job
continuous feedback loop through:
stand-ups, retro’s, right challenges, peer feedback etc.

23. Hack days / Hackweek

24. “It’s ok to fail“

25. Create an environment where innovative and
passionate people can be their best.

26. “ How does such an environment look like?”

27. Today’s Playlist
1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality

28. Alliance

29. Squad

30. “Small agile team designed
to feel like a start-up”
•Cross-functional (most of them)
•Own mission
•Daily work
•Autonomous

35. Alliance

36. Today’s Playlist
1. Spotify and our values
2. Continuous Improvement
3. Engineering Organisation
4. Quality

37. 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?

39. 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.

40. QA = Quality Assistance
Instead of acting as quality gatekeeper we want to help
the team to deliver the software with the best possible
quality.

41. 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.

43. 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/

44. Stage 2 : Continuous Delivery
‣ Shorten release cycles.
‣ Automated deployments.
‣ Have the squads handle deployment and
operations of their own code.

46. 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.

47. 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.

48. Stage 3 : Experimentation
‣Showing early prototypes to users.
‣A/B Testing.

50. “ 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.

51. Thank you.
Jacob Vesterlund
jacves@spotify.com
Kay Korper
kay@spotify.com