Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· News
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

THE ITIL BOOKS

The five ITIL books can be obtained directly from the publisher's website:
HERE

Or as downloadable PDFs: HERE

Current Membership

Latest: benitact11
New Today: 18
New Yesterday: 34
Overall: 228621

People Online:
Visitors: 130
Members: 0
Total: 130

Login
Nickname

Password

Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Related Resources

Service related resources
Service Level Agreement
Outsourcing

NOTE: ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.


Search



Languages
Select Interface Language:


Advertising
Please contact us via the feedback page to discuss advertising rates.

The Itil Community Forum: Forums

ITIL :: View topic - Problem root cause: missing feature
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Problem root cause: missing feature

 
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management
View previous topic :: View next topic  
Author Message
InPadure
Newbie
Newbie


Joined: Feb 23, 2018
Posts: 1

PostPosted: Fri Feb 23, 2018 11:44 pm    Post subject: Problem root cause: missing feature Reply with quote

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?
Back to top
View user's profile
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Problem Management All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.