Software Development Life Cycle (SDLC)
Active Ambassadors in This Topic
Community Posts
For orgs that are trying to mature their DevOps model, what do you think the most common gaps or pitfalls are?
Does your software team often have to go back and forth with other departments to clarify their feature requests or bug reports? Any advice for simplifying that process so new requests are easier to understand from the start?
No automated tests, and no intention to ever write them5%
No automated tests, but have an intention to write them in the future30%
Writing automated tests after big feature releases26%
Writing automated tests after several sprints20%
Writing automated tests at the end of the sprint5%
Writing automated tests at the end of each user story4%
Ensuring each commit has automated tests3%
Test Driven Development4%
Other (please comment)
Has GitOps helped your software and I&O teams work together? Have you noticed any measurable benefits since implementing it?
How do you encourage your software team to work collaboratively on security — both within the team and with other departments?
If you’re trying to cut costs, where in the SDLC would you reduce performance testing? Have you ever had to eliminate testing due to lack of budget?
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%