Room
Track 4
Audience
Any software engineers who are interested in keeping code/product quality habitually with low costs.
Key-Learnings
- What Broken Window Theory means and why it matters
- Historical viewpoints and studies of the theory in software development
- How to deal with the Broken Window for the team starting to cultivate a good quality culture
Revisit the basic theory as you may or may not know
In this session, we will explore what “Broken Window Theory” is and why it matters in our work. “Broken Window” is not a big issue, but should not be missed unintentionally, because it may cause more serious problems in the future. As the real example, it will be shown first how my scrum team defines “Broken Window” and deals with it. Yes, you can define and customize the term for your situation. Based on the example, we will dive deeper what is the theory originally and how to have been utilized and discussed in software development.
By the end of this session, attendees will have a better understanding of how to apply the “Broken Window Theory” to their own team practices and develop a good quality culture.