Editing UNITA Agile Management Guide (section)

== Issues and mitigation measures ==

Risks and issues are different (source pmi.org):  
The key difference is an “issue” already has occurred and a “risk” is a potential issue that may or may not happen and can impact the project positively or negatively. We plan in advance and work out mitigation plans for high-impact risks. For all issues at hand, we need to act immediately to resolve them.

'''Examples of issues that can arise in the project are:'''
* There are disagreements on the interpretation of requirements;
* The WP task force has difficulties achieving the set goals (e.g. in terms of time, resources or quality);
* Non-conformities are identified by the WP task force or by other Stakeholders;
* Risks identified in the Risk Log occur, and thus risks change from potential problems to actual problems;
* External effects that influence the project in a negative way;
* Many other reasons.

=== Issue management ===

Issue management aims to ensure that issues that have a potential impact on project scope, time, cost, quality, risk, or stakeholder satisfaction are assessed and acted upon.  
Issues are logged and followed-up in a Issue Log. In each TT meeting, the team must:
* check and update the status (to do, in progress, done) of previousuly assigned issues
* identify new issues (if any) and the affected area (Schedule, Budget, Resources, Quality, Reputation)
* assess them in terms of priority
* assign them (RASCI) for resolution by specific actions

A priority level score is assigned according to the following list:

{| class="wikitable"
! Level !! Meaning
|-
| Critical || Immediate action required
|-
| High || Significant impact, resolve soon
|-
| Medium || Important but not urgent
|-
| Low || Minor improvement or enhancement
|}

As the following diagram shows, issue management follows the escalation process of decisions previously defined in the guide.