Nah, the trade will still go down; this way it allows us to over-analyze all the ways the trade is either the best or worst thing we could do. Major argument optional.Jmodene wrote:I guess that means no trade after all.
CANCELED: Maintenance Tonight
- obucard
- Perennial All-Star
- Posts: 8055
- Joined: April 18 06, 11:04 pm
- Location: Central AR
Re: CANCELED: Maintenance Tonight
- Jmodene
- Still waiting for someone to use a Weird Al song
- Posts: 15535
- Joined: April 18 06, 5:54 pm
- Location: Las Vegas, NV
Re: CANCELED: Maintenance Tonight
Thanks - I feel much better now.obucard wrote:Nah, the trade will still go down; this way it allows us to over-analyze all the ways the trade is either the best or worst thing we could do. Major argument optional.Jmodene wrote:I guess that means no trade after all.
- JackofDiamonds
- Bringer of Boston Baked Blue Balls
- Posts: 15047
- Joined: April 16 06, 9:15 pm
Re: CANCELED: Maintenance Tonight
What?! Cancelled? I want my money back.
- lukethedrifter
- darjeeling sipping elite
- Posts: 37434
- Joined: October 17 06, 11:19 am
- Location: Huis Clos
- sighyoung
- Mayor of GRB
- Posts: 37618
- Joined: April 17 06, 7:42 pm
- Location: Louisville
Re: CANCELED: Maintenance Tonight
Great. I've got just enough time to post this in the Cats thread.
-
- Red Lobster for the seafood lover in you
- Posts: 50608
- Joined: May 1 06, 2:41 pm
Re: CANCELED: Maintenance Tonight
Michael I think we should follow the ITIL process for change management. Next time, create a Change request ticket and then schedule a meeting with the Change Advisory Board for build approval. If you have and Requested Items please attach them to the change request, and if you have multiple change requests please create a release request and attach those to that. Please be prepared with a business justification for your change. Once you have been granted build approval by the all powerful Change Advisory Board, then please provide a project plan, release notes, a build plan, a test plan, back out plan, test results, test results from the backout plan, test results from the backout plan that didn't work, test results from the build, test results from the release, and communication plan. Also please provide information on how you plan to communicate the communication plan. Also please be sure to have all of this ready two weeks in advance of the upgrade so that the Change Advisory Board who all have their thumbs up their asses can then approve and bless your change and THEN you can go forward.
You should spend 12x more in paperwork and documentation than the work to actually do the change. At least. Otherwise the CAB will decline your request and make you write more stuff. Things like "Michael will follow the ITIL process" 500 times.
Thanks.
--jim.
You should spend 12x more in paperwork and documentation than the work to actually do the change. At least. Otherwise the CAB will decline your request and make you write more stuff. Things like "Michael will follow the ITIL process" 500 times.
Thanks.
--jim.
- Jmodene
- Still waiting for someone to use a Weird Al song
- Posts: 15535
- Joined: April 18 06, 5:54 pm
- Location: Las Vegas, NV
Re: CANCELED: Maintenance Tonight
But what about the trade?jim wrote:Michael I think we should follow the ITIL process for change management. Next time, create a Change request ticket and then schedule a meeting with the Change Advisory Board for build approval. If you have and Requested Items please attach them to the change request, and if you have multiple change requests please create a release request and attach those to that. Please be prepared with a business justification for your change. Once you have been granted build approval by the all powerful Change Advisory Board, then please provide a project plan, release notes, a build plan, a test plan, back out plan, test results, test results from the backout plan, test results from the backout plan that didn't work, test results from the build, test results from the release, and communication plan. Also please provide information on how you plan to communicate the communication plan. Also please be sure to have all of this ready two weeks in advance of the upgrade so that the Change Advisory Board who all have their thumbs up their asses can then approve and bless your change and THEN you can go forward.
You should spend 12x more in paperwork and documentation than the work to actually do the change. At least. Otherwise the CAB will decline your request and make you write more stuff. Things like "Michael will follow the ITIL process" 500 times.
Thanks.
--jim.