How do you manage frequent product release cycles with minimal turmoil?
Sunday, February 21st, 2010This is a quick blog post in response to a question I received on a previous article: Close the gap between R&D and Customer Support. Between my long-winded answer and the fact that this subject deserves a post on its own, I decided to respond here.
I came from Google, search for interface between R&D and CS and apparently I came to the right place. Most of your article is clear to me as we are doing it day to day, more or less. Although I’m in the opposite chair (CS manager), I do understand the pressure on R&D as well as on CS. Question is, in an organization which has a habit of issuing new sub versions and major versions quite often (and of course CS attention for bug solving decreases) what can be done in order to assure timely bug fixes, as well as keep releasing new versions as often as possible.
The question of “how to manage frequent release cycles with minimal turmoil and maximum alignment (R&D, CS, Marketing)” is a good one. I highlighted our processes and best practices that worked well for my team. These should not be a surprise, as they are aligned with the agile development best practices. However, note that implementation and execution of these practices require vigor and disciple for all parties involved. I would love to hear from others’ experiences.





