Venue: GOTOcon BerlinFred George talks with Eberhard about “Developer Anarchy” – a development approach Fred has been using very successfully in different organizations. Developer Anarchy is a manager-less process. All team members write code. There are no stories. Instead developers figure out how to reach specific business goals. Besides writing code some team members have additional responsibilities: Ambassadors communicate with other teams, lead developers mentor the team and concierges solve issues like getting required hard- or software. The teams decides who has those roles. The approach is very successful in fuzzy environments such as web advertising. It is important to try out new ideas quickly in those environments – therefore Developer Anarchy is often combined with microservices to allow for quick and easy deployment.
SE Radio 253: Fred George on Developer Anarchy
Join the discussion
You must be logged in to post a comment.
4 comments
More from this show
Tim McNamara, a well-known Rust educator, author of Rust in Action (Manning), and a recipient of a Rust Foundation Fellowship in 2023...
Simon Wijckmans, founder of c/side — a company that focuses on monitoring, securing, and optimizing third-party JavaScript —...
Catherine Nelson, author of the new O’Reilly book, Software Engineering for Data Scientists, discusses the collaboration between data...
How do you hire for developers who work well this way?
[…] latest episode of Software Engineering Radio contains an interesting discussion about a project management technique known as Developer Anarchy. […]
[…] A very great podcast on developer anarchy: http://www.se-radio.net/2016/03/se-radio-episode-253-fred-george-on-developer-anarchy/ […]
More relevant then ever before. Great concept, great explanation.