{"id":1608,"date":"2010-02-11T00:01:51","date_gmt":"2010-02-11T00:01:51","guid":{"rendered":"http:\/\/blog.resellerclub.com\/?p=1608"},"modified":"2025-10-24T13:56:28","modified_gmt":"2025-10-24T13:56:28","slug":"how-feature-requests-are-managed-by-our-development-team","status":"publish","type":"post","link":"https:\/\/www.resellerclub.com\/blog\/how-feature-requests-are-managed-by-our-development-team\/","title":{"rendered":"How Feature-Requests and Updates are Managed by our Development Team"},"content":{"rendered":"

Editors Note – As a leading hosting and web-services company in the industry, it is a constant challenge to fit as many feature requests and updates as possible in every product release. As any online service provider would know, it is not always easy to completely satisfy each and every client with every new release. While not every feature that is desired can be immediately integrated, we want to assure you that each request you make is taken extremely seriously and a final decision is made only after several rounds of internal debate and discussion. We hope that today\u2019s blog acts as a small step towards increasing the signal-to-noise ratio on our support channels since we believe that if you, our Resellers know about our processes, it will help immensely in enhancing your overall Reseller experience.<\/em><\/span><\/p>\n

At ResellerClub, the process of improving our system and incorporating new features involves several key stages. We are active proponents of the Agile Development philosophy and have taken several steps over the years to focus our entire development ethos around this concept. Features that we choose to implement are definitely not picked up at random! Meticulous planning and strict processes are used to govern our selection of task priority. We proactively attempt to keep our entire planning and decision-making process as transparent as possible.<\/span><\/p>\n

Every feature request or bug report received via our various feedback channels is considered and discussed by our Development team. After every request is made, a \u201cTask\u201d ticket is created for our Development team. Every feature so added first goes through an intermediate level, where it is filtered and added to our advanced Project Management system. ResellerClub uses JIRA<\/a>, developed by Atlassian to track and monitor issues. Every issue is added with a neutral priority and is assigned to the relevant development sub-team.<\/span><\/p>\n

Every Wednesday, our entire Development team meets for a town-hall meeting where each feature request is brought forward and intensively debated upon. The Merits and Demerits of each request are considered with those features that have a tangible and immediate positive impact on your business given the highest priority. The Tasks so decided upon are marked with the appropriate priority level until completion. With the process being this lucid, it is easy for us to constantly evaluate the direction we are moving in and acts as have a compass for our growth.<\/span><\/p>\n

After every launch, we occasionally have a few Resellers who ask us why we did not integrate a certain \u201camazing feature\u201d that they wanted. Even though we may have skipped a certain feature, I assure you that the list of features included in every update is a result of careful planning, in sync with our vision of the future. Ultimately, every feature-request added to a release is prioritized keeping in mind the direction we are moving in.<\/span><\/p>\n

Before we explore the process of setting priorities, it is extremely important to understand how we structure our releases. Each release cycle is planned a set period before the current cycle has ended. On a macro level, we define the overall vision of the cycle, the goals that each development sub-team needs to achieve and the time-frame required to achieve these goals. Each sub-team aligns itself to complete a list of tasks which is drawn up from all comments made by you, directly based on your feedback! The selection involves identifying high-priority issues based on parameters such as:<\/span><\/p>\n