...
- Position the collection and reporting tools for easier collaboration.
Rob's laptop now owns all the files; yes, backups are made. A shared filesystem would be a better idea -- the Help Desk does not run a fileserver, Barb G says, so we'll rely on AFS until they do. Quota is a concern. - Switch from RT-export to Warehouse-export for dashboards and for monthly case-analysis.
Resolve to just live with the reduced reporting capability for certain variables, and enjoy the enhanced reporting of certain others (that the help desk arguably would find more useful anyway). - Document / Diagram the locations, paths and processes where data is generated, recorded, reported.
Draw arrows and make labels. - Redefine Metrics and Measures with buy-in from current HD Leadership
Play out the Measures Architecture model for all the variables reported on.
Help Desk Measures Inventory will help us here. Let it document what the Warehouse report can do for us.
Goals
By the end of FY09 (end of June, 2009) the weekly surveys for all IS&T queues should use one extraction engine based on the Warehouse ticket report. Ideally there is one survey web form. The survey spreadsheet will know queue the ticket came from and use that to drive the reporting out in a series of cascading pivots. Hmmm -- I can build that part first.
By the end of FY10 Q1 (end of August 2009) a new help desk quarterly reporting metrics engine will be driven by the RT-to-Warehouse reporting path, will be well-documented and broadly shared with Help Desk staff, and perhaps largely operated by Help Desk staff.
...