What are the Systemically Neglected Development Tasks that result in Chaos? Study asked Engineers: “Top Neglected Practices that Result in Chaos?” 
Participants were asked to identify “Top 3 Neglected Practices that resulted in Chaos”
Participant were then asked to “Vote 1 Down” that wasn’t as responsible for chaos
Results consisted of software engineers from US, AUS & Asia, 41-of-48 votes landed in top 5 answers selected from crowd-sourced list of 20 commonly neglected practices.
Results: Engineers strongly agreed that neglecting Exception Handling, Health Metrics, Load and Performance Testing often resulted in chaos, support calls and escalations. . Engineers Mostly Agree on Top Causes of Software Chaos. ©2019 iiSM.ORG, All Rights Reserved. Click slide to see in context of slide deck
Click to enter the site

Our mission is to strengthen the careers of software leaders by sharing as much software management theory, research and knowledge as humanly possible. We encourage you to join the mission by using our materials for personal growth, sharing among friends, and mentoring within your company; however, commercial training use must be licensed.

Our Funding model is to: provide certification and live training services as desired and requested by our community. We do this so that our staff can buy pop tarts, pay their bills, and produce more career boosting content, research and tools.

We require that our copyright notices are left in place.