- Published on
Top 10 reasons for lack of product development velocity
- Author
- Name
- Alex Naydenov
- Title
- Head of Sales at Hygraph
An extended list of top reasons why product and engineering teams are slower that they and their organizations want and need them to be.
Product development velocity is a key KPI for all product and engineering teams - almost as important as actually building the right product with the right features.
Top 10 reasons for lack of velocity
- Technical debt - architecture does not enable the rapid evolution of the product
- Lack of PMs - ex. team of uninspired and uninspiring mercenaries
- Lack of delivery management - does not remove impediments
- Infrequent release cycles - at least every 2 weeks; best is a daily release schedule
- Lack of product vision and strategy
- Not including engineers early enough in product discovery - their input should come early
- Not including product design early
- Changing priorities - Organization shifts direction mid-project
- Consensus culture
- Key personnel leaving