Management Information |
Issue Management Methodology for Tracking Project Issues
1. What is an Issue? An issue is an incident, circumstance, problem or inquiry that affects or potentially affects the timely delivery of the project, product or service, it may also impact the quality of deliverables and the cost of production. Some projects are ongoing and the definition of an issue is a little different. A help desk defines an issue as a request for help that requires a response. A service department keeps track of service requests as issues. A software maintenance group tracks reports of software bugs and enhancement requests as issues. Because of the impact issues have on a project, product development or ongoing service, issue management is an important aspect in any management methodology. This issue management methodology promises to make the handling of issues a seamless part of your larger scoped methodologies rather than a process separate from them. It is usually not hard for team members to identify issues, but it is still worth having a working definition of an issue. Remember that the more ambitious your project the more issues will arise. Action item: The project team must be made aware of what issues are, provide some examples, and ask other team members to provide some examples. 2. Requirements A central repository of issue information easily accessible to all team members, because it is good for team morale and productivity to know that their issues are being addressed. An automated central repository like Issue Tracker is desirable because it make the issue management and reporting much easier. Action item: Choose a central repository for your issues. An issue manager is the person chosen to oversee all issues. It can be the project manager, team leader or another person in a responsible leadership position. The issue manager is responsible for making sure that there is consistent, disciplined and continuous progress made on all issues. The issue manager is accountable to upper management for the progress made on all issues. The issue manager communicates issue progress to the team, upper management and all stakeholders. Action item: Appoint an Issue Manager and notify the issue manager of their role and responsibilities. This issue management methodology represents best practice for managing issues. However, the goal is to have a successful project, product development or service, the goal is not to follow a methodology fanatically. Action item: Adapt the methodology so your project's success is maximized. 3. Steps 3.1 Discovery Issues can arise at any time. When an issue is discovered it is recorded in the central repository. It is important to allow issues to be recorded by a broad group of people including team members, upper management, users, customers, stakeholders, vendors and contractors. It is important because if there are barriers to reporting an issue then there is an increased chance that the issue will go unrecorded. You cannot address issues that you do not know about. It is not necessary that everyone has access to central repository, but the more you can allow the better. Action item: Set up access to the central repository for those people that need it. 3.2 Recording Training people to identify issues is often unnecessary, however getting people to record the issue in the central repository will take some training and encouragement. For example, a team member may mention an unrecorded issue to the project manager during a coffee break or other informal occasion, this team member needs some encouragement to record such issues in the central repository. For all kinds of issues, prevention is better than correction. Also, issues tend to be less severe if they are addressed earlier rather than later. This means that every effort should be made to report issues as soon as they are discovered, instead of waiting for the issue to become "serious enough" before recording it. Do not be afraid of duplicating an issue or overlapping with existing issues, it is better than missing an issue. A complete description of the cause of the issue should be recorded in the central repository. Resist the temptation to describe the issue in terms of a solution. Any implication of the issue should be recorded. Attach any supporting documentation, screenshots, report output, faxes, error messages and other media that describes the issue. The person who is recording the issue can make a recommendation for a solution, if they have one. This personshould also assign the issue if possible, even if it is only assigned to the issue manager for re-assignment. When an issue is initially recorded it should be recorded in the central repository with a status code that reflects the fact that it is new issue and has not been reviewed. An attempt should also be made to categorize and rank the severity of the issue. The date and who created the issue should be recorded in the central repository. This is done automatically for you in systems like Issue Tracker. Many teams describe issues in terms of the desired solution, leaving others to deduce the actual issue. This is not best practice since it limits the scope of possible creative solutions. As an example a badly worded issue: "We need more people." There is no indication in this example of what the issue actually is, so finding alternative solutions is impossible. If the example issue had been worded as "The shipping department has swamped us with product, there is a possibility of spoilage if we cannot get the product delivered." With the issue worded this way perhaps the shipping department can become aware of how there actions are causing issues down the line and adapt their actions. 3.3 Initial Review The initial review is a triage of new issues. It is usually performed by the issue manager or deputies who are familiar with the scope and priorities of the project. If the team is small the entire team can meet for the review. For each new issue the status, category and severity are reviewed and the issue assigned to someone for action and optionally an owner is identified as follows. Sometimes the same person who records the issue may be doing the initial review, so these two steps can be fused into one in this situation. 3.3.1 Issue Status A decision is made about the next state of the issue. (The previous state was "new".) The next status of the issue reflects the nature and timing of the action to address the issue. It is one of the following:
3.3.2 Categorize the issue A first attempt at categorizing the issue was made when it was first recorded. But, now during the initial review the category can be refined. The proper issue category is helpful when prioritizing the resources required to address issues. It is especially useful for reporting purposes. Action item: Discuss with the team how best to categorize the issues you expect to get, and document the categories that will be used. 3.3.3 Rank the issue severity The severity reflects the importance of getting the issue resolved. Obviously, you want to direct resources at the most important issues before the lesser ones. Action item: Choose a small set of severity codes that have a clear ranking. For example: Trivial, Standard, Important, Critical. Some people prefer: Low, Medium, High, Very High. 3.3.4 Assignment From the start, the next person to take action on the issue must be assigned to the issue and notified. Issue Tracker will automatically notify the person assigned to the issue via email. If the issue description is incomplete, the issue can be assigned to the appropriate party to gather the information necessary to make the issue description clear. Assign a person and not a group. Experience has shown that assigning issues to individuals leads to greater accountability than assigning issues to groups. An individual can be confronted about lack of progress, it is much harder to confront a group of people. A group can be represented by a group leader, so you can assign an issue to the group leader who will take action to reassign the issue to correct group member who will actually address the issue. 3.3.5 Ownership It should be possible to decide which stakeholder is the owner of the issue. Having an issue owner is a way of recording who is accountable for the issue's resolution. Owners must review the issues they own for progress to resolution. If the progress is not sufficient the issue manager should be told so that the situation can be remedied. 3.4 Taking Action The process to address an issue iterates over the following sub-steps until the issue is resolved.
Notice that the action taken may involve reassigning the issue, changing status, refining the issue description, changing the category of the issue. All of these changes should be recorded in the central repository. Changing of status, category and severity are automatically logged for you in an automated system like Issue Tracker. 3.5 Ongoing Oversight Consistent and continuous evaluation of issues by the issue manager and the team must take place to bring the issues to resolution. This can take place through a periodic review of all active issues in the central repository with the team and a separate review with the stakeholders. Escalate issues as needed by re-assigning or by changing issue ownership. Report and communicate progress on all issues to upper management and to the team, subscriptions can be used by upper management and the team to follow progress on individual issues. This reporting can be integrated into project status reporting. Analyze issue progress and adapt actions. The central repository should be able to provide feedback on how efficiently the issues are proceeding from creation to resolution. If it is taking too long to resolve important issues, then the issue manager must find ways to improve the turn-around time. 4. Finally The following are a few further action items Action item: Distribute copies of this issue management methodology to team members and stakeholders so that everyone knows how and why issues are managed. Action item: Adapt and scale this issue management methodology to suit you project's scale and quirks. Action item: Create your central repository, and get started today. This issue management methodology has evolved over many years. It evolved from experience on projects with budgets from $500,000 to $50,000,000 which had a total number of issues ranging from a few hundred issues to many thousands. In half the cases the project team was physically dispersed in several countries. Grant Murray is project manager and enterprise application architect specializing in technical project leadership strategy. Email Grant Murray for questions or comments regarding this article, or if you require project management consulting.
MORE RESOURCES: Unable to open RSS Feed $XMLfilename with error HTTP ERROR: 404, exiting |
RELATED ARTICLES
Lawyers With 2 Hands And Everything Else I heard this back a few years ago. The boss yelled, "Get me a good lawyer but not the one with two hands!""Huh?" secretary was puzzled. Dont Take New Hires for Granted Hiring good people is only half the battle. The other half is keeping them, especially in a relatively strong economy where quality people are difficult to attract. Knowledge Mapping This module focuses on the basics of Knowledge Mapping, its importance, principles, and methodologies.Key QuestionsWhat is K-map?What does the K-map show, and what do we map?Why is K-mapping so important?What are some of the key principles, methodologies, and questions for K-mapping?How do we create K-map?BackgroundEach of the past centuries has been dominated by single technology. How to Create a Trusting Manager-Employee Relationship BUILDING TRUST AS A MANAGER: 1. Be reliable. Problem Solving When problem solving, you may recognize that you were working on a symptom instead of the problem. An analysis of the more clearly defined problem may require an alteration to the objectives or the ideal solution. How to Delegate Effectively ACCOUNTABILITY: Delegation is not complete unless subordinates are held accountable for their work. They should be accountable to only one person-usually their immediate manager-and must understand what criteria will be used in judging their performance. Project Heroes Project heroes. We've all heard of them. Dividing The Loot It is when the going gets better, that the going gets tough. This enigmatic sentence bears explanation: when a firm is in dire straits, in the throes of a crisis, or is a loss maker - conflicts between the shareholders (partners) are rare. Business Innovation - Organizational Structure Creativity can be defined as problem identification and idea generation whilst innovation can be defined as idea selection, development and commercialisation.There are other useful definitions in this field, for example, creativity can be defined as consisting of a number of ideas, a number of diverse ideas and a number of novel ideas. Document management : A dream of paperless office What is document management: When we think about "Document Management" we usually see a picture of paperless office. It is not an easy task to make an office paperless due to several existing problems based on Industrial needs. Organizational Culture and Creative Blocks - the Similarities Few Decision makers see the link between between creativity and innovation management, as performed by MBA's in firms, and creative endeavours such as screenwriting. In fact, there are very strong linkages. The Seven Cs: Partnership Danger Signs - The 4th C: Cumulative Money Problems A series of articles exploring the seven critical areas that can indicate a partnership is in trouble.The 4th C: CUMULATIVE MONEY PROBLEMSConflicts over money are very high on the list of reasons that 70% of business partnerships fail. Innovation Management: The Hype Cycle Creativity can be defined as problem identification and idea generation whilst innovation can be defined as idea selection, development and commercialisation.There are distinct processes that enhance problem identification and idea generation and, similarly, distinct processes that enhance idea selection, development and commercialisation. Problem-Solving Success Tip: Look For Sponsors And Solution Owners Look for sponsors and solution owners rather than problem owners.Everyone participating in the situation owns the problem, like it or not-and nobody likes it. How to Get Your Procedures Project Done Wouldn't it be nice for business owners and executives to be finished with their policies and procedures project already? They know they need to get it done, but maybe it's taking too long. Or perhaps their people are staring at a blank piece of paper, and they don't know where to begin. Measuring Creativity, DIY style Creativity measurement is often required in order to benchmark existing competencies, monitor improvement, increase output and generally provide tangible and useable processes and structures for clients.Individuals can measure their own creativity, the creativity levels of their group, department or organisation. Focus on Outcomes to Keep Your Business On-Course Did you know that an airplane in flight is off course nearly 98% of the time? No flight is completed in a straight line from Point A to Point B. Gravity, side winds, updrafts, and downdrafts are continually moving the plane off course. Structure Your Payment Offers to Sell More Products The way you structure your payment offers can increase your sales. I'm not talking about the way people pay like credit cards, digital payments, checks, and cash options. Innovation Management - some ideas are better than others Creativity can be defined as problem identification and idea generation whilst innovation can be defined as idea selection, development and commercialisation.There are distinct processes that enhance problem identification and idea generation and, similarly, distinct processes that enhance idea selection, development and commercialisation. Is Busyness Affecting Your Business? I'm too busy; I'd love to but I'm very busy; I'll get round to that when I'm not so busy.How often have you said any of those phrases? How many times a week do you hear someone else say those phrases? They're very common and busyness seems to have become a way of life for many people. |
home | site map | contact us |