From value stream mapping to burndown charts, making things visible is a core component of the continuous improvement process. But even with all this visibility, much of the data surrounding how your teams work is either not captured or not understandable. This data represents a great opportunity for insights and improvement. Think about it: Your management team tells you that your velocity is too low. What do you do? First, you need more information. What does “too low” mean? Why was the velocity low? Did the team deliver value? Brandon Carlson will share one team’s surprising insights when they analyzed previously invisible data. He'll also tell you how to discover what the highest risk areas of the system are for enabling the most cost-effective regression test strategy. It's all there, only tucked away where no one can see.
Ambiguity abounds about value streams, so it’s good to clarify what they are, why they matter, and how to exploit them. It's important to help employees understand the organization's definition of value, to provide visibility on how business value is created, and to focus on the fast flow of value through the value streams. If everyone understands which direction to row the boat, they can steer toward it together.
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. He will show how to shift to a hypothesis-driven retrospective that to guides specific improvements and learning goals. His team made significant changes to their retrospectives and were rewarded with a radical improvement. Breaking through their retrospective impediments and finally embracing a learning mindset empower Ryan's team to fix the legacy line of code that had held the team back for over year.
It’s usually easy and inexpensive to set up a continuous integration environment for either an agile or a waterfall project. Perhaps the most obvious benefit of CI is the elimination of the integration phase that existed in traditional waterfall projects, where we typically slip the worst on deadlines. But there are many other benefits to continuous integration that you may not have considered.
DevSecOps is a growing movement to incorporate security into DevOps practices in order to ensure flaws and weaknesses are exposed early on through monitoring, assessment, and analysis, so remediation can be implemented far earlier than traditional efforts. By failing fast with security testing, organizations reduce risk of a security incident and decrease the cost of rework.
Ken Johnston sees today’s software ecosystem in the light of Everything as a Service (EaaS). Operating systems like Windows, Android, and Chrome OS all ship regularly like a service. Browsers automatically update every few weeks, and apps are constantly updating through all the app stores. Although getting a test to pass once and signing off has gone by the wayside for software testing, still we run test cases over and over again. Ken shares how Microsoft took millions of test cases—yes, actually millions—and turned the important ones into measures based on real world telemetry. Massive amounts of data coming in from real devices and real users measure product quality and tie it to key customer satisfaction metrics.
When you have hundreds of applications performing various functions across several environments, it's tough to push all the code when it needs to be. Here are some steps to help your own team develop the internal tooling it requires to deploy thousands of applications if needed, all in a reliable, efficient manner.