Ever since starting at my new employer in Des Moines, I've learned just exactly how much I have to learn. Well actually, I can't say that. Because I'm sure I don't yet know how much I have to learn. I'll just say I've learned how much I don't know. Hmmm. Guess I can't say that either, because it's simply restating the previous....
I've just learned that I have a lot to learn! How about that?
I think I'm pretty good with the process analysis, but only mentally - for some strange reason, they want what I know in my head to be reduced to writing! Now I'm a pretty good writer, but if you ask me, I could use a little help. Like when I was asked to document the Change Management process and put it into an SOP format, for example.
I know the ITIL process; I know what has to happen with a Change from initial request, through the approval, through deployment, through closure. I know what has to be documented for testing, validation and back-out. I know if the change fails it has to trigger a post-implementation review, and that if it's cancelled it isn't necessarily a failed request.I know that the requester can't approve the change. I know the developer can't push to production. I know the tool has to be configured so that people can't make material modifications to their requests after submitting them for approval. I know there has to be some sort of infrastructure discovery component associated with the Change Management system, else changes will be deployed without an associated RFC.
But to put all that stuff into an SOP document?? Daunting, to say the least. After it was all said and done, the SOP doc I submitted was 29 pages!
Sheesh! I didn't think I had it in me!
See ya.
