How often do your engineering sprint cycles hit expected release timelines?
Less than 50% of the time24%
50 - 74% of the time57%
75 - 90% of the time14%
Over 90%3%
722 PARTICIPANTS
Less than 50% of the time24%
50 - 74% of the time57%
75 - 90% of the time14%
Over 90%3%
CEO23%
CIO53%
CTO37%
Software department leadership 28%
Team leads30%
Software engineers/developers19%
Someone else (comment to share)
N/A — no plans to use AI agents for software engineering5%
Certified Associate in Software Testing (CAST)29%
Certified Software Tester (CSTE)48%
ISTQB Foundation Level32%
ISTQB Agile Tester25%
Certification in a specific automation tool (i.e. Selenium, Ranorex)23%
Other certification5%
None8%
No selling.
No recruiting.
No self promotion.
Rules of EngagementFAQsPrivacy
© 2025 Gartner, Inc. and/or its affiliates. All rights reserved.
This is a sad state of affairs, in my opinion. Though I think the responses do reflect the current state. I still see most organization doing agile rather than being agile.
I consider a good number for my teams to be 105%. I have had teams that have hit this rate for years on end. Where this isn't happening, the focus should almost always be on management rather than on the teams.