Posted: Fri Feb 23, 2018 11:44 pm Post subject: Problem root cause: missing feature
Problem ticket has been raised after repeated incidents were identified in a system.
The software vendor recorded incident and reported back a development requirement number, also providing an estimated release date.
Some questions I have on this scenario (best / common practice):
- How can problem manager monitor the actual release date from service provider vs the estimated date?
- How can problem manager advocate adoption of a new release and link the problem with a change request number raised to support upgrade to the new released version that is supposed to fix the problem?
- How can problem manager monitor UAT/status of the change to make sure the fix is in place, ultimately demonstrating that the fix is also effective post-release in the system?
- When should the problem get closed?
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum