...
- Barbara and Mark in attendance
- Create a picture of what an ITSM Program would look like for our department
- Statement of Direction
- articulate a vision
- identify benefits - why are we doing this
- visibility into processes
- resources become interchangeable to some extent
- better analysis
- some consistent process where we had none
- identify pain points/biggest gaps
- identify stakeholders
- identify places where we have the potential for success
- base on lessons learned from Remedy Change Management implementation
- what parts make sense in our environment
- exclude areas where processes and/or tools are already embedded
- we don not want to replace existing processes or tools
- include areas where we can collect, connect and automate ("glue together")
- ITSS incident and response
- request fulfillment
- problem management
- clearly define what is in and out of scope
- limit to Operations & Infrastructure and Customer Support
- articulate how far down the slope we go
- articulate milestones and time line
- digestible chunks of work - the sequence of events to do this right
- what we get at each step along the way
- Statement of Direction
- Barbara and Mark cosponsor this larger effort once we have agreement on the vision and the work
- projects come next
- for example, Remedy CMDB build out with custom UI (service data but not asset data) based on prototype
- deliverable draft statement for next sponsor meeting 8/22/12
August 22, 2012Review
- review ITSM Statement of Direction with Barbara
...
- and Mark
...
- : ITSM Statement of Direction Final Draft.docx
- next steps:
- lightweight evaluation of ITSM tools 9/15 - 10/31
- look at all modules and interfaces
- use customer perspective
- identify any show stoppers
- commit to ONE TOOL by 10/31
- rework ITSM Statement of Direction
- narrow scope to 18 months
- delineate more tangible deliverables (name services, the processes we would apply and the value proposition)
- lightweight evaluation of ITSM tools 9/15 - 10/31
September 19, 2012