Issue Management in a Variety of Agile Development Environments

Issue management with agile project managementissue information in the platform's repository.
tools will vary, depending upon an organization'sAgile development teams that work in large distributed
software development environment. Agileor highly regulated development environments will need
development teams handling smaller, less complexto go one step further. They will likely need to integrate
development projects don't typically deal with a lot oftheir agile tool with a more powerful platform such as
bugs. Therefore, they may decide to stop using aan application lifecycle management (ALM) platform.
dedicated bug tracking tool and rely entirely upon theirKey capabilities of an ALM platform include the ability
agile project tool for managing issues. Why have twoto handle issue tracking at a very detailed level, and to
lists of things to do? By keeping everything in oneprovide capabilities for change management, custom
force-ranked backlog in the agile project managementworkflow, source code management, task
tool, it is often easier for the product owner to makemanagement, testing, lab management, collaboration,
priorities clear to the team, and it will give teamand reporting and analytics. Best-of-breed ALM
members better visibility into all issues as they arise. Inplatforms also have integrated tracking capabilities that
addition, the team will still be able to see the origin ofenable "traceability"-- the ability to easily associate, or
every issue, who is handling that issue, what changeslink together, objects also referred to as "artifacts,"
have been made, and when the issue is closed orwithin the system. Asssociation simplifies knowledge
completed.sharing and provides traceability of an object
The situation may be completely different forthroughout its lifecycle. So for example if we think of a
development teams that manage large, complexcustomer reported issue" as the object:
development projects and that log hundreds of bug1. the issue is entered into the system,
reports a week. Using an agile project management2. the issue can be linked to
tool alone for tracking issues will not work. Take a• the original report describing the bug or feature
video game company, for example, that may get 200request
bug reports every week for one version of a product• the source code generated to resolve the issue
they are developing. Many of the bug reports they• the release containing the fix
receive are likely duplicate issues. By integrating their• emails and discussions around the issue
agile project management tool with a bug tracking• any other artifacts that need to be associated with
system, they will be able to triage and consolidatethat issue
issues before they wind up in the agile projectThese associations enable development teams to
management tool's product backlog.improve information sharing, capture institutional
The real benefit of combining an agile projectknowledge, and simplify regulatory compliance - which,
management tool and a bug tracking system is that itin turn, translate into building significant business value.
becomes a one-stop shop for tracking all issues, andIn summary, issue tracking in an agile environment will
teams can leverage the best features of bothvary greatly depending upon an organization's
systems. Agile software tools enable teams tosoftware development environment. For some agile
manage issues at a project level and provide reportsteams an agile project management tool will be
and views such as burndown charts and workloadsufficient. But for teams working in large, complex,
balancing that do not typically exist in a bug trackingdistributed or regulated environments, integrating the
platform. The bug tracking system, on the other hand,agile project management tool with either a bug
will allow agile teams to manage issues at a verytracking or ALM platform provides the best solution.
detailed ticket level, customize workflow, and centralize