Designing Autonomous Teams and Services

by Scott Millett, Nick Tune

In high-performing organizations such as Salesforce and Spotify, autonomous product development teams own problems end-to-end—from interacting with customers to delivering engaging digital products. These teams find new ways to solve customer problems by constantly running experiments, using high-speed engineering capabilities to create extremely short customer feedback cycles.
In this report, you’ll explore how leading organizations increase autonomy across teams and services through techniques designed to accelerate product delivery and improve business/IT alignment. With examples and use cases, authors Nick Tune (Salesforce) and Scott Millett demonstrate how autonomous teams leverage continuous discovery and delivery to find the best solutions with the highest business value. This report is ideal for engineering executives, CTOs, software architects, and senior engineers.

Genres: Leadership, Technology, Software

95 pages, Unknown Binding

Published January 1, 2017

Reviews

[Matteo Figus · Rating 4 out of 5]

Pretty interesting overview on DDD and Socio-architectural patterns.
Designing systems and organisations is a hard job and this book presents a couple of good examples and stories to dive into the topic.

One thing I would have liked, is more content around patterns for re-organising teams and systems (the last part) - and (even if I recognise it's a difficult topic to write about) more content around how to evolve from highly coupled systems (especially on a cultural/organisational level) to a more autonomous organisation.

I really recommend everybody to give a read given it's even freely downloadable from the O'Reilly website!

[Jorn · Rating 5 out of 5]

I really believe in the idea of autonomous high performing teams. Scott knows how to express why team and service autonomy should concern you. It's about extreme programming, agile, domain driven design, continuous delivery and the role of organisation design.

It's recommended reading for agile coaches, scrum masters, product owners, developers and managers in software companies.

[Damien · Rating 4 out of 5]

A very nice approach to how reorganize teams in order to minimize dependencies. Would have like some more details on patterns, but I need to read it again because it's quite fast on some notions

[theory · Rating 3 out of 5]

This isn’t a book so much as a brief introduction to the topic, with basic concepts introduced. It’s an annotated bibliography. Use it as a jumping off point to other works.