1. Dependencies
1.1. confirmation app is ready for pilot
1.2. Each area (manager) will need to set up their team's structure (systems, work types, tasks, assignments, etc.)
2. Feedback
2.1. Problems
2.2. Suggestions
2.3. Maintain master list of problems, suggestions in Excel
2.4. Set up a mailing list
3. Scope
3.1. Test the system with real-world scenarios
3.2. Refine the system as needed before full rollout
3.3. Develop reference and training deliverables?
4. Issues/questions
4.1. Should documentation be developed by the pilot group or the implementation group?
4.2. Confirm that when we go live, managers will need to reenter their structure in the prod environment.
4.3. Communicate to EAS
4.3.1. It's coming
5. training
5.1. Things staff will want to know
5.1.1. How do I enter time?
5.1.2. When should I enter time?
5.1.3. New node
5.2. Things staff should understand before beginning
5.2.1. Work types, Effort Types
5.2.2. Area-specific guidelines
5.3. develop training plan
5.4. Approach
5.4.1. Team members train small pilot group
5.4.2. During small pilot develop training
5.4.2.1. Collect topics for training
5.4.3. Provide training as part of large pilot group
5.5. Delivery alternatives
5.5.1. Classroom training
5.5.1.1. Create video
5.5.1.2. Includes explanation on work/effort types
5.5.1.3. (deal with cultural dimensions)
5.5.2. On-line video
5.5.2.1. Conduct a WebEx and record it
5.5.3. Training documentation
5.5.4. Reference documentation
5.5.4.1. Post in EAS wiki
5.5.4.1.1. Potentially build as stand-alone then move into the EAS wiki later
5.5.4.2. Add as hover-help in application
5.6. Documentation
6. Plan
6.1. Strategy
6.1.1. small pilot
6.1.2. larger pilot
6.1.2.1. include manager & team leads
6.2. Schedule/milestones
6.2.1. conduct small pilot
6.2.1.1. Engage/train manager
6.2.1.2. Finalize environment
6.2.1.2.1. Establish 1.0 version of code
6.2.1.2.2. Provide clean database (in QA environment)
6.2.1.3. Complete manager's preparation work
6.2.1.4. Engage/train pilot members
6.2.1.5. Ensure we have same starting point for all pilot members
6.2.1.6. Time entry & get feedback
6.2.1.6.1. interact with system as they will in real world
6.2.1.6.2. 1 or 2 weeks
6.2.1.7. review feedback
6.2.1.8. fix/enhance during pilot
6.2.2. Determine what needs to be fixed before large pilot
6.2.3. Conduct large pilot
6.2.3.1. Pilot-Wide Communication
6.2.3.1.1. John develop/publish
6.2.3.2. Engage/train manager
6.2.3.3. Finalize environment
6.2.3.3.1. Establish 1.0 version of code
6.2.3.3.2. Provide clean database (in QA environment)
6.2.3.4. Complete manager's preparation work
6.2.3.5. Engage/train pilot members
6.2.3.6. Ensure we have same starting point for all pilot members
6.2.3.7. Time entry & get feedback
6.2.3.7.1. interact with system as they will in real world
6.2.3.7.2. 1 or 2 weeks
6.2.3.8. review feedback
6.2.3.9. fix/enhance during pilot
6.2.4. Determine what needs to be fixed before go-live
6.2.5. Fix/enhance system and documentation
6.2.5.1. How much time should we allow for this?
6.3. Action items for pilot team
6.3.1. Map out time line
6.3.1.1. Serialize this document (paul)
6.3.1.2. Estimate each step
6.3.1.3. Develop schedule
6.3.2. Review critical bugs at Tuesday's meeting (8/28)
6.3.3. Juris finish fixing critical bugs
6.3.4. Engage/inform senior directors
6.3.4.1. Get commitment, establish priority
6.3.5. Develop plan for how to conduct pilot
6.3.5.1. eg, submit time every day as you would for real
6.3.6. Find out how Juris will manage work intake
6.3.7. establish list of people in small pilot group
6.3.8. establish list of people in large pilot group