How often do your engineering sprint cycles hit expected release timelines?
Less than 50% of the time20%
50 - 74% of the time62%
75 - 90% of the time13%
Over 90%3%
Please join or sign in to view more content.
727 PARTICIPANTS
3.9k views1 Upvote1 Comment
Content you might like
What have been your experiences with using OData with Java and/or .Net?
243 views2 Upvotes
TCO19%
Pricing26%
Integrations21%
Alignment with Cloud Provider7%
Security10%
Alignment with Existing IT Skills4%
Product / Feature Set7%
Vendor Relationship / Reputation
Other (comment)
Head of Enterprise Architecture MERCK Group in Healthcare and Biotecha year ago
Strategy & ArchitectureWhich aspect of running a software business do you find most challenging?
Acquiring new clients and projects20%
Keeping up with evolving technologies and testing methodologies52%
Building a strong reputation and establishing credibility in the industry53%
Adapting to changing client demands and expectations40%
Ensuring effective communication and collaboration with clients and development teams21%
Developing effective pricing strategies and staying profitable14%
Other (please specify)
1.5k views
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.