Using failure to successfully deliver software

Failure is feedback and feedback is the breakfast of champions, or in this case software delivery teams. How do software delivery teams “welcome changing requirements, even late in development“ while maintaining "continuous attention to technical excellence"? The answer is simple, through feedback, early and constant feedback. So why is it so hard to accept feedback? If feedback is so important why don’t we welcome it as early as we can and as often as we can? Many times it can be the delivery if you’re not asking for feedback it can come across as negative or as criticism. Fortunately, practices and methodologies such as Agile, Continuous Integration, Continuous Delivery, Shifting Left, and DevOps were created with feedback in mind. They introduce when and how feedback is delivered making feedback welcome throughout the entire lifecycle of the project. Following these practices has drastically improved software development and delivery by shortening feedback loops and increasing transparency. The tighter the feedback loop, the quicker teams can course correct if they are failing to meet customer needs or product quality. Attendees will learn how the evolution of software tools, process, and methodologies have enabled and shortened feedback loops allowing teams to continuously improve as new software development and delivery “bottlenecks” are identified and resolved.