As an outcome from IS&T Leadership Group discussions, a work group has been formed to define for IS&T what a "pilot" (beside the person or computer flying the plane) is and when we should use pilots. The members of the working group are:

Goal

Our goal is to put together a definition of a "pilot", collect some best practices around when
to use and what makes a "pilot" successful and test our definition and best practices on a couple
of current pilots.
We will also pull together a simple framework and guidelines for pilot inititaion, control
and closeout We plan work closely with the Project Management Team to leverage existing
materials.

Potential candidates:

  1. Altiris for Remote Disk Management
  2. IPTV
  3. Bit Locker for Disk Encryption

Definition: PILOT

A Pilot

  1. Is a Project (complete with scope, deliverables, sponsor, project leader, etc.)
  2. Has Resources (people time, budget, equipment)
  3. Answers some Question(s) (e.g., if we build it, will they come(customer demand)? will this
    technology work?)
  4. Has a planned closeout (i.e. go, no-go decision point; if it can't be killed/stopped it isn't a pilot)
  5. Has an exit strategy for go and no-go outcomes.
  6. Experimental pilots have a discovery focus and
  7. Evolutionary pilots have a delivery focus and need to build in a plan for potential support and sustainability.

Current List of Pilots

Starting List:

To get started, we have divied up IS&T and will be collecting lists of all the current pilot projects.

List of pilots

Work Completed so far

Working Group Meetings (See Attachments)

NEXT STEPS