Management Training:
Issue Management Classes For Beginners
The aim of this management article is to walk you through everything you need to know about issue management. Once you understand this you should easily be able to embed an issue management framework within whatever project management framework you already use.
Before we can begin to understand the process we need to know what an issue is. An issue can be simply defined as any issue which has occurred and is affecting or about to affect your project. The key thing to remember about issues is that they are already or will definitely impact your project. This is what distinguishes issues from risks: a risk has a probability of occurrence meaning, so unlike an issue, it might not actually occur.
Now that we understand what an issue is let's move straight on to the issue management process. This management process consists of six steps:
Identify
Assign Owner
Analyze
Evaluate
Actions
Monitor
Let's review what each of these steps means in turn.
Identify: First you need to identify your risks. If you are the project manager then this will not be hard, as risks are always being thrown at you from all directions, for example, from team members, stakeholders, or via email.
Assign Owner: You need to give each issue an owner to ensure it gets resolved
Analyze: Now you need to categorize the issue to understand if it's a major or minor issue. The usual way to do this is to classify the issue by impact and urgency
Evaluate: Here you compare the different issues in your list and prioritize in order of their importance.
Actions: Here you write down the action that needs to be undertaken to resolve the issue. It is the owner's responsibility to ensure that the action happens.
Monitor: regularly follow up all issues to see if they have been resolved. If not, repeat the issue management process from the analyze step, to ensure outstanding issues are handled properly.
It is good practice to embed the issue management process into your project so that issues are considered regularly. By doing this it reduces the risk that your project gets out of control, and that you need to find a new job. It's also good practice to understand the total number of issues facing the project via an issue burn down diagram. This enables you to very easily see if your issues, and therefore your project, are getting out of hand. That's it, now all you need to do is embed this process into your projects to create your own project issue management process.
Arval Deco:
link
Subject:
Management Classes
More Management Training Tips