You have great software engineers. They work on autonomous teams that deliver frequently. Your products are doing well. But — there is always a But. Things could be better. Something is frustrating team members or disappointing customers or driving up costs or slowing things down. What is it?
Friction. No matter how well things are going, there will always be friction. Consumers experience friction when using your product. Friction delays a team’s response to a product request. Friction makes the code difficult to change. Differing expectations create friction among team members. Competing goals create friction between teams.
This talk presents the top eight sources of friction in software-intensive systems. It will also discuss how leading organizations address these friction generators.