Slide 1

Slide 1 text

Mastering Broken Windows Theory in Software Development Masanori Kawarada (Mark Ward), 2023-11-16, 
 25 min talk for "Conf in a Conf Session" in Agile Testing Days 2023 Revisit the Basic Theory as You May or May Not Know @mkwrd

Slide 2

Slide 2 text

Masanori Kawarada 
 (Mark Ward) @mkwrd •QA Brain ‣ Software Engineering Journeyman with 10+ Years Experience ‣ Quality, Agile Development, and Culture ‣ Developer in Scrum, Quality Advisor, Global Quality Evangelist, 
 Conference Speaker, Translator, Writer, and Organizer of Markin' Quality •MBA Certi fi ed in GLOBIS University, 2022 ‣ Considering how QA Engineer as the Bridge between Business and Technology •International Conference Lover 💖 From Japan 🇯🇵

Slide 3

Slide 3 text

Broken Windows Theory @mkwrd • https://en.wikipedia.org/wiki/Broken_windows_theory

Slide 4

Slide 4 text

Quiz: Next Broken Windows Which Area Will You Find Next Broken Windows in? Area A Area B @mkwrd

Slide 5

Slide 5 text

Quiz: Next Broken Windows Yeah, Excellent!! But Why? Area B @mkwrd

Slide 6

Slide 6 text

•Devastation Spreading to Its Surroundings If Left Unchecked ‣ One broken window lowers the moral and causes community disorder. ‣ To prevent, they have to crack down on every breach of order. •Studies in Criminology ‣ Philip Zimbardo, 1969 ‣ George L. Kelling and James Q. Wilson, 1982 ‣ George L. Kelling and Catharine Coles, 1996 Broken Windows Theory @mkwrd

Slide 7

Slide 7 text

•The United States: Zero-Tolerance Policing ‣ Reducing Violent Crimes Drastically in New York (Critised as It's too Excessive) •Japan's Police Agency: Enforce Parking Violations ‣ Reducing Crimes by 15% over Two Years in An Area of Sapporo City •Tokyo Disney Resort: Environmental Maintenance ‣ Improving Employee and Visitor Etiquette by thorough 
 environmental maintenance like cleanliness and repairing Applied in Real Life @mkwrd

Slide 8

Slide 8 text

@mkwrd How about the Broken Windows Theory 
 Applied in Software Development? 🤔 Although it's interesting theory, but ...

Slide 9

Slide 9 text

•Software Entropy: Nature's Tendency toward Disorder ‣ "When disorder increases in software, programmers call it 'software rot.'" ‣ Technical Debt won't be paid back, can spread uncontrollably, told in 2019 ver. •"Tip 4: Don't Live with Broken Windows" ‣ "Bad designs, wrong decisions, or poor code" ... ‣ Any Disorder should be fi xed as soon as possible. ‣ "Tip 5" in 2019 ver. "The Pragmatic Programmer" (1999) @mkwrd • You should read "20th Anniversary Edition" (2019 ver.) • This session is based on the 1st edition (1999 ver.)

Slide 10

Slide 10 text

•William Levén et al. (2021) ‣ Investigating the causal relationship between the Technical Debt density of a system and the propensity of developers to introduce new Technical Debt during the extension of that system •Terese Besker et al. (2022) ‣ With at least 95% credible intervals, signi fi cant effects of Technical Debt level on the subjects’ tendency to re-produce and introduce other code smells Other Recent Studies @mkwrd Technical Debts Reproduce Technical Debts

Slide 11

Slide 11 text

"OESFX)VOUBOE%BWJE5IPNBT +VTUUFMMZPVSTFMG /PCSPLFOXJOEPXT l @mkwrd

Slide 12

Slide 12 text

@mkwrd How Can Be Done Practically? 
 It's IMPOSSIBLE to Go without Broken Windows. 🤔 Although the principle says so ...

Slide 13

Slide 13 text

•Discussion about a few Broken Windows in real projects 
 to fi nd out how to fi x them Challenges in The Book @mkwrd • You should read "20th Anniversary Edition" (2019 ver.) • This session is based on the 1st edition (1999 ver.) •Consideration how to fi nd when a window fi rst gets broken, how to react, and what should be done if the result is caused by someone else's decision or a management edict First Step: Find a Broken Window Sooner

Slide 14

Slide 14 text

•De fi ning Broken Windows as Unrecognised Errors in Production ‣ Can't be Perfectly Avoided "Technical Debt" or Other Broken Windows Things ‣ Focused on "All Errors Identi fi ed" •30 Mins Meeting to Watch Errors Every Week ‣ Sentry, the Error Monitoring Platform, Collecting All Errors in Production ‣ Lead by QA Team at First, but Held by Scrum Teams Now ‣ Feeling Effective to Expand Scrum Teams in Other Domains "No More Broken Windows" Activity @mkwrd

Slide 15

Slide 15 text

•Pros ‣ Minimum Habit of Coping Errors in Each Scrum Team ‣ Cultivating Mindset to See What Happens in Production •Cons ‣ Some Members Unable to Participate Every Week ‣ Losing The Way Sometimes due to Not All Errors Resolvable Takeaways of The Activity in 3 Months @mkwrd Iceberg Model • https://www.change-agent.jp/en/systemsthinking/approach/the_iceberg_model.html

Slide 16

Slide 16 text

•Broken Windows Theory Basics ‣ Versatile, Proven Theory from Criminology •Broken Windows Theory in Software Development ‣ Fruitful Learnings from the Classic, "The Pragmatic Programmer" •Real Example with Pros and Cons ‣ De fi ning Your "Broken Windows" for Practical Measures ‣ Identifying Pros and Cons to Improve the Activity Summary @mkwrd

Slide 17

Slide 17 text

Mastering Broken Windows Theory in Software Development Masanori Kawarada (Mark Ward), 2023-11-16, 
 25 min talk for "Conf in a Conf Session" in Agile Testing Days 2023 Revisit the Basic Theory as You May or May Not Know @mkwrd