Pre Go Live
- Document provisioning process (and automate where possible - automation more important for subsequent rollouts)
- Define Post Go Live support process
...
- Customer Team Leads to provide Level 1 support
...
- Customer DevOps & DBA
...
- teams to provide Level 2 support
- Datical Team to provide Level 3 support (daily or weekly support meetings between Level 2 & Level 3 teams are a best practice)
- Define and get agreement (from all stakeholders) on team Go Live dates
- Align Go Live date with start of new sprint
- End-user training & enablement - process and artifacts
- Prepare end-user training materials
- Datical to co-create end-user guides (based on existing documentation) - capture screen shots from completed
- Prepare end-user training materials
...
- Customer implementation
- Datical to create demo script for
...
- Customer Team
...
- Customer to deliver end-user demo in completed solution according to demo scripts
- Record session via GoTo Meeting
- Edit out any mistakes or dead space
- Optionally chop up video into small use-case videos
- Customer to deliver end-user demo in completed solution according to demo scripts
- Schedule end-user training
- Training Video &
...
- Documentation (1 hour session via GTM)
- Show demo video to teams
- Walk through user guide with teams
- Answer questions
- Hands-on Training(2 hours per team - Datical to facilitate via GTM)
- Primarily for Team Leads, but could be extended to entire team if not too many people
- Provide sample scripts and have team leads run through the common use-cases
- Have team leads
- Primarily for Team Leads, but could be extended to entire team if not too many people
- Documentation (1 hour session via GTM)
...
- bring scripts from their application to package
- Pre Go Live Environment Cleanup
- Refresh Reference Databases after production deployment (but before start of next sprint)
- Use newly deployed Production (or Pre-Prod) database as the source for the refresh
- Follow the Cleanup Process defined here - How To: Clear out Test Changes (In Preparation For Go-Live)
- Refresh Reference Databases after production deployment (but before start of next sprint)
Go Live
- Developers start packaging new scripts at start of the sprint
- Packaged artifacts get deployed down the pipeline as development and testing progresses
Post Go Live
- Follow support plan that was defined above
- First couple of sprints require the bulk of the support activity
...