The team at Sprintly, the makers of a productivity tool for development teams, have shared some interesting data on developer cycle time and it should calm your doubts about just how fast your developers are working.
Sprintly is used to track how long developers spend completing different types of tasks and the sizes of those tasks. Its recently published data reveals that, for the most part, developers are working at a pretty average pace (at least those using Sprintly).
Sprintly ticket data shows that across its user base, cycle times are very similar. 75 percent of all tickets in its system are started and completed in about 175 hours. Sprintly also found that most of the variability occurs before a ticket has been started - when stakeholders are the ones determining specifications and prioritizing work. There also seems to be a lag when transitioning from "done" to "tested and ready to be deployed.
That should put to rest at least some of your concerns that your development team is to blame for the slow pace of development. Sprintly's writeup on the issue delves into what's actually causing slow development, highlighting unclear and changing requirements as some common reasons.
Digital marketing executive with proven experience in all aspects of search engine optimization (SEO), performance-based advertising, consumer-generated/social media, email marketing, lead generation, Web design, usability, and analytics. - 20-year Internet marketing veteran, currently serving as the Digital Marketing Campaign Manager at Antenna Group (formerly Chicago Digital). - Former Editor-In-Chief of Website Magazine, and a regular speaker on Web technology digital marketing strategy - Author of several books on digital marketing Including Web 360: The Fundamentals of Web Success; Affiliate 360: The Fundamentals of Performance Marketing; Domains 360: The Fundamentals of Buying & Selling Domain Names, and SEO 360: The Fundamentals of Search Engine Optimization.