DevOps West 2018

"Move fast and break things” tells quite a story of the relationship between speed and agile. Speed has been a driver in our industry before it was even an industry. Books promise that certain frameworks can deliver twice as much in half the time, yet teams still struggle delivering what's expected of them. This session describes a six-month case study of a multi-team transformation. The orders were to make the teams deliver faster, but they were consistently missing deadlines. Frustration was on the rise.

Retrospectives empower teams to learn and improve. But many teams fail to reach their true learning potential. Ryan was part of a team that held retrospectives for a year and a half to fix one line of code. Through the story of this team, he will show you how they turned their retrospectives from a meeting with meaningless action items to one that accomplished a meaningful improvement. Ryan will explore the resistance that was met and how it was overcome.

Defining, understanding, and agreeing on the scope of work to be done is often an area of discomfort for product managers, business analysts, developers, and quality assurance experts alike. The origin of many items living in our defect tracking systems can be traced to the difficulties encountered while performing these initial requirements activities.

Do your Retrospectives feel like a repeat of the last one? Are they moan and groan sessions? Want to try something new to give your team a boost? When design principles are applied to strategy and innovation, the success rate for innovation dramatically improves. Great design has that “wow” factor that makes products more desirable and services more appealing to users. Why not try using known design principles during your retrospectives to get that "wow" factor for your teams!