Skip to main content

Issue Management

Logging support issues and tracking their resolution.

Also Known As

  • Backlog
  • Bug Tracking
  • Issue Tracking
  • Maintenance (in Waterfall Development)
  • Risk Management
  • Sprint Backlog (in Scrum)
  • Support
  • Ticket Logging

Related

Addresses / Mitigates

  • Implementation Risk: Tracks and manages defects and issues, ensuring they are resolved.
  • Operational Risk: Provides a systematic approach to managing and addressing operational issues.
  • Communication Risk: Facilitates communication about issues and their status among team members.
  • Trust and Belief Risk: Tracking and fixing bugs improves software reputation.
  • Security Risk: Addresses and resolves security incidents to protect the organization.

Attendant Risks

  • Complexity Risk: Managing a large number of logged issues can add complexity.
  • Process Risk: Creates dependency on issue tracking tools and their accuracy.
  • Schedule Risk: Managing and resolving logged issues can impact project timelines.

Used By

  • Scrum: Issues are logged and tracked through tools like JIRA to ensure they are resolved promptly.
  • Waterfall Development: The maintenance phase in Waterfall involves managing issues and bugs that arise post-deployment and making necessary updates and improvements.

Description

"Issue tracking systems are used to manage and maintain lists of issues, as needed by an organization." - Issue tracking system, Wikipedia

Issue Management / Issue Logging in software development involves recording and tracking issues, bugs, and tasks. This practice helps in managing and resolving defects systematically, ensuring that all problems are addressed in a timely manner and improving the overall quality of the software.

"Issue