How often do your engineering sprint cycles hit expected release timelines?
Less than 50% of the time23%
50 - 74% of the time60%
75 - 90% of the time12%
Over 90%3%
618 PARTICIPANTS
Content you might like
"Real" errors/defects41%
False positives (issues that aren't defects)51%
False negatives (missed defects)46%
Failures due to fragile/flaky test automation37%
Errors due to environment or setup issues31%
Unhandled user errors18%
None of the above1%
970 PARTICIPANTS
VP of Engineering in Healthcare and Biotech, 11 - 50 employees
I read "vendor" here to mean someone primarily providing a SaaS or PaaS, or even a desktop, web or mobile application, or code library.If that is correct, then it can be extremely hard to price.
Most ...read more
CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.Director of IT in Healthcare and Biotech, 501 - 1,000 employees
Overall fit of the provider's services is key in any recommendation when selecting one of the big 3 clouds for any organization. Multi-cloud is significantly more difficult than most companies realize, and selecting a ...read moreSignificantly10%
Moderately68%
Not particularly18%
Not at all4%
Not sure0%
152 PARTICIPANTS
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.