📌 Need
During the software development process, teams often encounter bugs that, while
important, are not critical enough to be resolved immediately and may slow down the progress of more urgent tasks.
🔍 What is it
A deferred bug is a fault in the software system that has been identified and logged, but for which resolution is postponed to a later time. This decision is usually driven by factors such as the bug's severity, its impact on the system, resources availability, and alignment with the project's priorities.
❓ How
In practice, when a bug is discovered, it is logged into a bug tracking system. The bug is then evaluated based on its severity, the resources required to fix it, and the project's current priorities. If the bug is not critical and does not severely affect the system's functionality, or if resolving it would distract the team from more urgent tasks, it can be deferred. This means the bug's status is set to "deferred", and it is scheduled to be revisited and fixed in a later development cycle. This allows the team to focus on higher priority tasks, optimizing the development process and resource allocation.