Chapter 4: The Business Value of CI/CD
- It is difficult for developers to work on a new feature without having all the requirements up front. It can be a great hindrance for a developers ability to finish assigned work without all the necessary requirements.
- Pain driven development is about improving processes that are causing you pain. The main point being that the pain that you feel will help point you into areas of improvement.
- Developers will eventually ignore messages if they are bombarded with too many alerts. It is best if the alerts are meaningful and not just noise.
- By rotating team members into different teams you help shape their perspective and give a broader understanding of development practices and increase their product knowledge.
- It is beneficial because not all development practices are valuable, it could be that a development practice is being done because something better has not been thought of, sometimes asking why something is done will help bring changes necessary for an organization.
- Metrics and reporting are a great way to convince your stakeholders on the value of CI/CD. Remember that a picture is worth a thousand words sometimes.
- Leadership may not understand what automation means and understand the impact that automation can have on an organization. You may need to educate them by doing a lunch and learn or make a company presentation.
