Summary
In this chapter, you learned how to measure the business outcomes of software development activities. First, you learned about the importance of feedback and how this helps to understand customer needs and whether those needs are actually being met. Then, numerous approaches to asking for feedback were introduced, both direct and indirect.
Finally, you learned about hypothesis-driven development and how a mindset of experimentation can help to cut down waste.
With this knowledge, you can now choose and implement feedback mechanisms that allow you to learn what the user sentiment regarding your application is. You are now able to implement an experiment-based approach to creating software, focusing on value-adding features and ignoring or even removing features that do not add value.
In the next chapters, you will learn all about containers. Containers are rapidly changing the way software is delivered and are often used for applying DevOps principles to both existing...
