TEMPORARY PLACEHOLDER> WILL CLEAN UP -KP
Chuck King on Pilot Project:
2 people to Manage Fusion
Pilot from December 1 to February 1
**Project Control Front Page
**Project Scope and Definition
**Green Light Chart (snapshot)
**Resource Planning
- Set aside time for those 2 to meet every week and learn/test
- FSS/SAIS and DITR were testing orgs
- contact with vendor
- early January sponsor meeting pointed out areas of learning
- late January meeting with sponsor
- conference call with Dell and Altiris
- To Chuck:what has worked well as a pilot?
- Initial scope definition - structure
both what you can do, what you shouldn't do
- sponsor
- keep on track with purpose - referring back to mission statement
(easy to go down rathole...this helps ground the pilot team)
- set aside time to deal with the pilot
- have test plan?
notification server and taking inventory using Altiris agent
First introduce to DITR and add to laptops
Altiris gave 200 node
identified outside group (SAIS) to add in
Reporting from machines
- not really a test plan - more of deliverable milestones
- test plans can be a lot of work
- similar to gantt chart - can be high level
- communication plan with regular check-in to sponsor is part of the pilot
- closeout report
accounting closeout should reflect amount of time used for pilot
- roadblocks:
communication plan was not in place
definition of roles/expectations included in resource planning
- vendor relationship was excellent. sent tech for three days, available readily
- learned that our reporting structure may not be the best way - not a planned consequence, but good luck
- helpful for other pilots (SOS pilot project would have helped)
WiaP next steps:
pilot that didn't work well
report recommendations