Presentation: What Does Speed Mean in Software Product Delivery?

Track: High Velocity Dev Teams

Location: Majestic Complex, 6th fl

Duration: 4:10pm - 5:00pm

Day of week: Monday

Level: Intermediate

Persona: Architect, CTO/CIO/Leadership

What You’ll Learn

  • Understand the difference between feeling fast and being fast from an organizational, systemic perspective.
  • Gain insight into how to take risks intelligently so they don’t impact speed.
  • Learn techniques for identifying and measuring speed that you can apply in your context right away.

Abstract

There are two parts to speed in software product delivery:

  1. The human experience of delivery feeling slow or fast
  2. Delivery actually being slow or fast.

Feeling fast is about removing friction; delivering fast is about designing how you deliver. It's possible and necessary to address both of these aspects. It is soul-crushing when delivery feels slow; it is business-crushing when delivery is actually slow. This talk will explore this way of thinking about "high velocity" and specific examples of concepts and practices to try from experiences at ThoughtWorks and Spotify. For example, the friction introduced by something as simple as bad naming and the significant impact of a “divide and conquer” strategy versus “conquer and divide”.

The talk explores this way of thinking about "high velocity" and specific examples of concepts and practices to try from experiences at ThoughtWorks and Spotify. For example, the friction introduced by something as simple as bad naming and the significant impact of a “divide and conquer” strategy versus “conquer and divide”.

Change and innovation: This talk is intended to change both how attendees think about how they work and specific practices at both the detailed day-to-day and broader coordination level.

Expert-Practitioner Driven: The speaker is both involved in these types of activities as well as represents a recognized company in the Agile space (Spotify)

Originality: There is a Medium post this talk is expanding on: https://medium.com/@jchyip/what-does-speed-mean-in-software-product-delivery-9bc95c1c36c3.

Interview

Question: 
QCon: What's the focus of your current role at Spotify?
Answer: 

Jason: My focus right now is helping the organization with the rapid rate of growth. So whatever that means in terms of how to maintain or improve in effectiveness, and that tends to be a random set of problems. Netflix calls it the paved road. We establish a paved road of sorts where you can do what you want to, but if you go off that road, you have certain things that you have to now deliver, because you're no longer on that paved road. The infrastructure, the observability, the different things that are required for a service to be called a service—you've got to do yourself now, because you're off that road. You can do it, but you have to accept the responsibility that you've got to do the additional stuff.

Question: 
QCon: What's the motivation for your talk?
Answer: 

Jason: The idea of how to improve organizational speed is something we've been talking about for at least a year. How can we strategically maintain speed, improve speed, understand the true nature of speed, and know how fast are we. I have noticed that a distinction that many people miss, is that there's a difference between when feeling fast and actually being fast from an organizational, systemic perspective. Those two factors don't always line up. Some people are acting off a feeling, as opposed to taking a deeper look and learning what actually makes a difference in their organization. I think it's an important point for any team looking at speed to understand there's this distinction, and then learn the tactics that fall under each umbrella for your particular context.

Question: 
QCon: What do you want someone who comes to talk to walk away with?
Answer: 

Jason: I want to show my concept so when people come to addressing the question of how to be faster, they understand the distinctions and the specific techniques or tools available to them. I'd like people to come away from the talk and have ideas that they can directly apply to their context. I also want to convey that I think it's still important that things don't feel slow—there are methods to help change that feeling. I want to show how people can engage in these sort of efforts more effectively in general.

Question: 
QCon: Are there any specific techniques that you share?
Answer: 

Jason: There will be some simple things like mundane keyboard shortcuts, and then more complicated things like backup options on risky decisions. I’ll talk about how to take risks intelligently, so even if you have to throw it away, you'll know it was still worth the shot.

Question: 
QCon: What is the practice, tool or technique that I should be focused on today?
Answer: 

Jason: From a purely technology perspective I'm generally of the school of “you learn whatever is necessary to deal with the problem you're facing”. So, all technologies and tools are things you use to solve problems. So I’d say adaptability is the strongest thing from a techniques perspective to focus on—which is also related to organizational speed.

Speaker: Jason Yip

Agile Coach @Spotify, previously Principal Consultant @ThoughtWorks

First encountered Extreme Programming in 1999 on comp.object, comp.software-eng and c2.com (the original Wiki). Worked at ThoughtWorks from February 2001 just after the dot com bubble burst. Was a committer on CruiseControl, the first Open Source Continuous Integration server. Dropped out of a MSc in Software Engineering. Joined Spotify NYC as an Agile Coach in February 2015.

Find Jason Yip at

Similar Talks

Software Engineer @Agrilyst
Developer Advocate @Couchbase
Principal Software Engineer @ Vistaprint
Cofounder & CTO @Flow.io., previously Co-Founder & CTO @Gilt
Senior Infrastructure Engineer @Heroku

Tracks

Monday, 26 June

Tuesday, 27 June

Wednesday, 28 June