Which statement fits with the SAFe Core Value of Built-in Quality?
Which statement fits with the SAFe Core Value of Built-in Quality?
OPTIONS
- Quality should only be worked on during the Innovation and Planning Iteration
- You cannot scale crappy code
- Quality is not part of the SAFe Core Values
- Quality depends on the scale of the project and should be implemented from the top down
Answer:
You cannot scale crappy cod
Explanation:
That’s a common phrase used to emphasize the importance of Built-in Quality as one of the core values of the Scaled Agile Framework (SAFe). The idea behind this phrase is that you can’t simply throw more resources at a software project and expect to scale it effectively if the code is of poor quality.
In SAFe, Built-in Quality is about incorporating quality into the software development process from the start, rather than trying to add it in later. This means that the development teams need to focus on building high-quality code from the beginning, and that they need to have the necessary processes and tools in place to ensure that the code they are delivering is of high quality.
The reason why this is important is because code that is of poor quality is often difficult and time-consuming to maintain and scale, which can have a significant impact on the overall efficiency of the development process. By focusing on Built-in Quality, organizations can ensure that they are delivering software that is scalable, maintainable, and of high quality, which helps to increase the overall efficiency of the development process and ensure that the software being delivered meets the needs of the business and the customer.
So, in conclusion, the phrase “You can’t scale crappy code” is a reminder that quality is an essential part of the development process, and that organizations need to focus on delivering high-quality code from the start in order to be successful in delivering software that meets the needs of the business and the customer.
