Anyone had one recently?
I'm contracting around NZ at the moment, theres a clear distinction in the workplace compared to the UK around ITIL and process.
So for the purposes of reporting we had some requirements..
Pretty simple we thought - we wanted some CI's adding into the CMDB (services).. As the current SD have been told to log against a 'default' CI... good one. Anyway, the SD manager here is fairly new but has a solid understanding. Once the meeting was underway it was clear that the 'admins' had been let loose on the CMDB is the past and it had evolved into something horrible.
No SDM's were in the meeting to help us out so we battled for a bit. Basically the way the admins wanted to do it was to create a 'changed password' CI and have the service in the resolution area. As they believe changing a password is a service.. They were concerned about the request area drop down box being too long but were willing to flood the CMDB with rubbish, meaningless CI's. Eventually I gave up and let them have it.
I put the usualy arguments across - relationships, ownerships, service catalogue alignment (don't have one) etc and i was met with ridiculous arguments from 3 close knit admins.
Can anyone tell me why a change password CI is ridiculous or am I going mad?
Has anyone else been in horrible meetings?
I'm contracting around NZ at the moment, theres a clear distinction in the workplace compared to the UK around ITIL and process.
So for the purposes of reporting we had some requirements..
Pretty simple we thought - we wanted some CI's adding into the CMDB (services).. As the current SD have been told to log against a 'default' CI... good one. Anyway, the SD manager here is fairly new but has a solid understanding. Once the meeting was underway it was clear that the 'admins' had been let loose on the CMDB is the past and it had evolved into something horrible.
No SDM's were in the meeting to help us out so we battled for a bit. Basically the way the admins wanted to do it was to create a 'changed password' CI and have the service in the resolution area. As they believe changing a password is a service.. They were concerned about the request area drop down box being too long but were willing to flood the CMDB with rubbish, meaningless CI's. Eventually I gave up and let them have it.
I put the usualy arguments across - relationships, ownerships, service catalogue alignment (don't have one) etc and i was met with ridiculous arguments from 3 close knit admins.
Can anyone tell me why a change password CI is ridiculous or am I going mad?
Has anyone else been in horrible meetings?



