Problem/Change Management - Problem only related to 1 change
Just found that a problem can only be related to 1 change which for us becomes and issue. I would have expected that a problem could have multiple changes associated with it.
The example that has highlighted the situation:
Team of 4 have laptops which have filled the internal drives due to the type of applications they need to use for their job.
We have 1 incident reported which we managed and created the problem to determine root cause and final solution. The agreed solution is to bring forward a standard rolling replacement for the team by a number of months.
So I need to create 4 changes, one for each laptop to be swapped out, as each will be scheduled when the person is in the office, and technician available etc.
All I can do is associate 1 change with the problem, and the remaining 3 changes sit unrelated. I know why the other 3 exist but the tech working on the job won't and when the auditors come in it won't be obvious to them why 3 laptops have been changed out of sequence etc. Descriptions can be updated but I'd prefer to have the relationships.
I know I could use 1 change and create tasks on it, but that doesn't ensure the documentation for each laptop, installation/backout etc plans are done.
Regards,
Andy
The example that has highlighted the situation:
Team of 4 have laptops which have filled the internal drives due to the type of applications they need to use for their job.
We have 1 incident reported which we managed and created the problem to determine root cause and final solution. The agreed solution is to bring forward a standard rolling replacement for the team by a number of months.
So I need to create 4 changes, one for each laptop to be swapped out, as each will be scheduled when the person is in the office, and technician available etc.
All I can do is associate 1 change with the problem, and the remaining 3 changes sit unrelated. I know why the other 3 exist but the tech working on the job won't and when the auditors come in it won't be obvious to them why 3 laptops have been changed out of sequence etc. Descriptions can be updated but I'd prefer to have the relationships.
I know I could use 1 change and create tasks on it, but that doesn't ensure the documentation for each laptop, installation/backout etc plans are done.
Regards,
Andy