Bug Handling

What About "Bugs"?

In technical contexts, a "bug" is an unexpected error or flaw in a software system. While not anticipated, we recognize that bugs can suddenly appear within delivered technical solutions. If a stakeholder needs a bug fixed, they should contact the appropriate case queue and provide details about the circumstances and requirements. The TErpEngage Director, business analysts, and project managers will assess bug status and determine the priority of necessary fixes.

Potential Rankings and prioritization are as follows:

• Critical: Bug fixes to be scheduled immediately
• High: Bug fixes to be scheduled within the same quarter
• Medium: Bug fixes to be scheduled as time permits (possibly within the same quarter or the next)
• Low: Bug fixes to be added to the backlog

​With the current Quarterly Project Planning process, "critical" bugs will be addressed immediately to be resolved within the current sprint, or as soon as possible.  We recognize that these types of bugs may lead to inoperable or unstable systems, and we will do our best to mitigate them promptly. With that, we also recognize that by focusing on critical bugs, other sprint goals, including enhancements and non-urgent project requests, may not be completed within their planned schedules. When this occurs, the TerpEngage Team will communicate those schedule adjustments with stakeholders and continue working as efficiently as possible. 

All other non-critical bugs will be evaluated by the TerpEngage Director and team members for scheduling considerations.