Greetings! This is my second post in a series I recently started discussing the Software Development Lifecycle we use here at ChannelAdvisor. If you have not yet read my prior posting on this topic, you may want to do so now. It’s a fascinating tale of pirates, danger, monkeys, and death defying software development on the high seas!
Previously I covered the concept of Software as a Service and then delved into the different system “environments” we utilize to deploy our software. In this post I will describe the concept of a “Change Request” and how those are categorized, ticketed and tracked. In upcoming posts I’ll focus on how Change Requests are deployed (”Short Term” and “Long Term” releases), and will delve into our movement towards Agile Development.
Change Requests
Within the company, every time a defect is found in our software (ahem, never), every time someone mentions “wouldn’t it be cool if the product could do X” (ahem, always), and every time a service request is issued to the engineering group, a “Change Request” (CR) ticket is opened to record and track the request. We literally log hundreds and thousands of these requests against ourselves, no matter how large or small in scope.
With all of those tickets opened, the use of Change Management software is critical to providing us order from the chaos. Currently we use a product called Synergy Change from Telelogic. It’s a solid product and serves our needs sufficiently, but could definitely be a little cheaper (just in case someone from Telelogic is reading this heehee).
