!mit-redgrey-footer3.gif|hspace=4,align=left! !ist_logo.gif|hspace=4,align=right!

h3. Who are we?

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

h3. 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:
# Altiris for Remote Disk Management
# IPTV
# Operating System Bundled Disk Encryption (FileVault, BitLocker, EFS)

h3.  


h3. Definition: PILOT

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

h3. Current List of Pilots

Starting List:
* VoIP
* IPTV
* Altiris for 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.
* SAIS - Darlene
* ISDA - Jon
* CSS - Jon
* OIS - Kyle
* AC - Laxmi
* TSS - Kyle
* VP Office - Laxmi

h3. List of Pilots CSS (Pilot name & Project lead)

* ALTIRIS in PMM toolkit PM Chuck King Sponsor: Pope Sponsor
* Operating System Bundled Disk Encryption (FileVault, BitLocker, EFS) - Jonathan Hunt
* Student Software Nominal Fee Pilot (Mathematica) - Jonathan Hunt
* IS&T and SAVE Pilot - Oliver Thomas
* SuSE Linux Dual Boot T60 Laptop through GovConnection Pilot - Bill Cattey

h3. List of Pilots ISDA (Pilot name & Project lead)

* Alfresco project for Content Management - Josh Scott & Chatherin Iannazzo
* MITBI (pilot project using Hyperion for forecasting & modeling) - Mary Weisse
* Jabber Project - Dennis Barron
* WebSSO (web single sign on) - Bob Basch & Sam Hartmann doing work, Chatherine Iannazzo overseeing project

h3. List of Pilots OIS (Pilot name & Project lead)

Nothing reported from OIS.  

IPTV will be moving into OIS from Academic Computing.  

h3. List of Pilots SAIS (Pilot name & Project lead)

Fladager reports no pilots based on e-mail to Meholic and direct report team leads

h3. List of Pilots TSS (Pilot name & Project lead)

From Allison Dolan: 

I could not think of anything on the telephone side that I would call a 'pilot'.  There are several activities (e.g. ACD, Mir3, NameConnector upgrades) where we are phasing in implementation and we have testing etc, but it is on an implementation path - we are learning/tweaking, but the go/no decision has been made.  Even VoIP, although still called a pilot, is really early phases of implementation rollout.

On the CG side, we have 'informal pilots' of the new Performance Appraisal process - some people are using it (volunteers), and we hope to get feedback.  However, even here, the pilot framework is weak

h3. List of Pilots AC (Pilot name & Project lead)

IPTV R. Winchester

h3. List of Pilots VP - Office (Pilot name & Project lead)

None
VOIP? PM TBH

h3. Working Group Meetings

* November 15, 2006 [^WIAPWG_Nov1506_agenda_action.doc]

h3. {color:green}Work Completed so far{color}

* Kick-off Meeting - November 15, 2006
* Working group wiki set up - November 16, 2006
 

h3. TODO


h3. {dynamictasklist:NEXT STEPS}