Melissa Greene explores the pitfalls of management.
Alison Lloyd examines some less-than-stellar occurrences in non-software fields, drawing out some ideas that she hopes will make software development a little less painful.
Giannakakis and Dalkitsis present how Shazam releases faster, more predictably and with more features by using BDD and automation testing, without slowing down or hindering the development process.
Big Design Upfront was considered so evil in the early days of Agile that it acquired its own acronym. It’s time we relearned that great products start with asking the right questions.
Dan North describes a model for thinking about the age of code and argues for replaceability as a first class concern, ending up with something that looks a lot like microservices.
Harrold and Redington present a survey of the cults, sects and heresies they’ve encountered while working with people "doing agile", culminating in their formulation of a new "ad-hoc" Agile manifesto.
Ardita Karaj and Jason Little present their company’s journey to Agile using Lean Startup, contractor/internal coaches, culture hacking, ADKAR, Kanban, Innovation Games, and others.
Chris Chedgey explores how “locality of relationship” affects coupling, cohesion, and the width of interfaces, showing structural patterns that increase or decrease complexity.
Stuart Williams shares from experience how his company implemented Kanban, what worked for them in handling maintenance, support and a number of small projects.
Giovanni Asproni shows how to create a software architecture with just the right amount of design that can be incrementally evolved (or changed) as the system grows and changes.
Aaron Quint shares an honest story of a team's journey, taken from his experience as CTO of Paperless Post, an organization which went from 5 to over 100 people and from a dev team of 2 to 40.
Kovas Boguta, David Nolen discuss embracing demand-driven architectures to be able to more flexibly accommodate the rapidly transforming needs of the clients.