A 3 part series about the CIRCUIT (Continual Improvement Committee for IT) presented to you by Dana P. Miller, Chair of CIRCUIT
As mentioned in my first post, CIRCUIT was started last May as a mechanism for IT Staff to submit their ideas for internal process improvement.
The CIRCUITEERS were recruited to represent all areas of IT Services:
Amy Locke-Solution Delivery
Bob Black-Process, Planning & Administration
Bryan Powell-Enterprise Operations
Connie Johnson-Security, Compliance & Risk Management
Micah Cooper-End User Services
Dana Miller-Chair-Process, Planning & Administration
Our Enterprise Architect, Bob Dein, also attends CIRCUIT.
CIRCUIT meets every Tuesday at 2:30 pm in Hoyt 107 and we review the week’s suggestions in the Improvement Registry (See link below).
Click “Run Report” after clicking the following TeamDyanmix link:
Improvement Registry by Service
CIRCUIT determines the implementation method from the following choices:
FAST
IT Project
Just-do-it
Vendor
Sometimes the implementation method can be a combination of two methods.
The CIRCUIT Chair (I, Dana P. Miller) meets with the LT every Monday morning at 9:30 am and the LT advises me when FAST Team Projects are starting, presenting and, ending.
2016 year-end efforts will be to identify CIRCUIT generated projects and tickets that have resulted in value added activity for IT Services and enter this work into the MU Lean Database to provide a university view into the efforts of CIRCUIT.
If you have any questions or ideas for improving CIRCUIT contact me or the other CIRCUITEERS.
You can also enter a suggestion to the Continual Improvement Committee for IT Services (CIRCUIT).
Thanks.
Dana P. Miller
CIRCUIT Chair
[email protected]
