No automated tests, and no intention to ever write them4%
No automated tests, but have an intention to write them in the future37%
Writing automated tests after big feature releases23%
Writing automated tests after several sprints18%
Writing automated tests at the end of the sprint4%
Writing automated tests at the end of each user story3%
Ensuring each commit has automated tests3%
Test Driven Development3%
Other (please comment)
Monthly8%
Quarterly40%
Annually18%
On a project-by-project basis12%
As needed in response to specific factors11%
We use different strategies for different projects5%
We’re in the process of creating a software development strategy1%
We don’t follow a strategy1%
Other (I’ll share in a comment)
Problems with tool integration16%
High vendor costs22%
Lack of buy-in from employees44%
Lack of buy-in from executives61%
Limitations of the low-code/no-code software71%
Bugs in the finished code16%
None of these — we’ve adopted low-code/no-code tools3%
Other (I’ll share my barrier in the comments)1%