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.