You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

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:

  • Laxmi Rao - Academic Computing
  • Kyle Pope - Client Support Services
  • Jonathan Hunt - Client Support Services
  • Darlene Fladager - Relationship Managers

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 current pilots.

Definition: PILOT

A Pilot

  1. Is a Project (complete with scope, goals, owner, 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

Current List of Pilots

Starting List:

  • VoIP
  • IPTV
  • Desktop Management
  • Stellar Images
  • Flexibile cluster work spaces
  • Hyperion
  • Disk Encryption

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

  • ISDA - Jon
  • CSS - Jon
  • OIS - Kyle
  • AC - Laxmi
  • TSS - Kyle
  • VP Office - Laxmi
  • No labels