GroupTrack Development Process
Every two weeks, the development team and management hold a planning meeting. During this time, we review everything that is in our queue for development and make decisions on which opportunities will move into active development for the current 2 week dev cycle.
We make these decisions around several factors, including urgency, severity of impact for our customers, and growth opportunities for the tool. Opportunities that will have the greatest impact for the most customers are prioritized higher than opportunities with low impact or "nice-to-have" new features. The opportunities we decide to implement most urgently generally focus on the following:
- What is the most significant impact for our users?
- Does the development opportunity affect all users or only a few?
- Is there a workaround that users can utilize to still access the tool functions while we program a more efficient fix / solution?
As a note, core functionality breaks that prevent use of the tool and have no workaround options are always prioritized first and do not wait for the 2 week dev cycle before being considered. If you have a bug or break that is entirely preventing the primary functionality of your tool, please reach out to let us know so we can provide you with a temporary workaround or escalate your issue for immediate consideration.