It's been a few years, and a couple of employers, since I've done a COTS implementation. I no longer have a template for COTS implementations, but there are some thoughts that come to mind.
- Is it truly COTS - no customization required (interfaces, reports, etc...), or integration with other applications?
- Testing to make sure there are no conflicts with other software used?
- Manual or automated distribution to end users?
- Any user involvement needed during installation or setup?
- Communication plan?
- Training required?
- Pilot?
- Post-implementation support plan?
...
1 reply by Gillian Summers
Apr 28, 2017 4:22 AM
Gillian Summers
...
Thanks for your reply, that's really helpful!
Saving Changes...
Deepesh RammoorthyICT Project Manager ( PMP®AgilePM®Certified ScrumMaster® (CSM®))| Australian Red Cross Blood ServiceTarneit, Vic, Australia
I can give you the headings that you need to cover
1. Introduction
1.1. Purpose
1.2. System Overview
1.3. System Description
2. Scope Statement
3. Assumptions and Constraints
4. System Organization
5. Implementation
5.1. Summary of Implementation
5.2. Points-of-Contact
5.3. Major Tasks
5.4. Implementation Schedule Tasks
5.5. Security and Privacy
5.6. System Security Features
5.7. Security Set Up During Implementation
6. Implementation Support
7. Hardware, Software, Facilities, and Materials
7.1. Hardware
7.2. Software
7.3. Documentation
7.4. Personnel
7.5. Staffing Requirements
7.6. Training of Implementation Staff
7.7. Outstanding Issues
7.8. Implementation Impact
7.9. Performance Monitoring
7.10. Configuration Management Interface
8. Go Live Implementation Details
8.1. Requirements Post Go Live
8.2. Risks and Contingencies
8.3. Implementation Verification and Validation
8.4. Acceptance Criteria
8.5. Entry Criteria
...
1 reply by Gillian Summers
Apr 28, 2017 4:22 AM
Gillian Summers
...
These are very useful, thanks!
Saving Changes...
Gillian SummersIT Programme Director| FreelanceAndover, Hampshire, United Kingdom
Apr 27, 2017 5:12 PM
Replying to Aaron Porter
...
It's been a few years, and a couple of employers, since I've done a COTS implementation. I no longer have a template for COTS implementations, but there are some thoughts that come to mind.
- Is it truly COTS - no customization required (interfaces, reports, etc...), or integration with other applications?
- Testing to make sure there are no conflicts with other software used?
- Manual or automated distribution to end users?
- Any user involvement needed during installation or setup?
- Communication plan?
- Training required?
- Pilot?
- Post-implementation support plan?
Thanks for your reply, that's really helpful! Saving Changes...
Gillian SummersIT Programme Director| FreelanceAndover, Hampshire, United Kingdom
Apr 27, 2017 8:22 PM
Replying to Deepesh Rammoorthy
...
I can give you the headings that you need to cover
1. Introduction
1.1. Purpose
1.2. System Overview
1.3. System Description
2. Scope Statement
3. Assumptions and Constraints
4. System Organization
5. Implementation
5.1. Summary of Implementation
5.2. Points-of-Contact
5.3. Major Tasks
5.4. Implementation Schedule Tasks
5.5. Security and Privacy
5.6. System Security Features
5.7. Security Set Up During Implementation
6. Implementation Support
7. Hardware, Software, Facilities, and Materials
7.1. Hardware
7.2. Software
7.3. Documentation
7.4. Personnel
7.5. Staffing Requirements
7.6. Training of Implementation Staff
7.7. Outstanding Issues
7.8. Implementation Impact
7.9. Performance Monitoring
7.10. Configuration Management Interface
8. Go Live Implementation Details
8.1. Requirements Post Go Live
8.2. Risks and Contingencies
8.3. Implementation Verification and Validation
8.4. Acceptance Criteria
8.5. Entry Criteria
Great input from Deepesh. We do lots of these projects, I've also found it useful to include tasks around capturing user requirements and then making resulting configuration changes, and also user testing, to ensure that the software is installed correctly, works with our hardware, and works with our business processes. Finally, data capture for MI and benefits management.
...
1 reply by Gillian Summers
Apr 28, 2017 4:52 AM
Gillian Summers
...
Thanks! This has been really helpful. I am now armed with lots of questions to discuss with the suppliers next week.
Saving Changes...
Gillian SummersIT Programme Director| FreelanceAndover, Hampshire, United Kingdom
Apr 28, 2017 4:46 AM
Replying to Tim PM
...
Great input from Deepesh. We do lots of these projects, I've also found it useful to include tasks around capturing user requirements and then making resulting configuration changes, and also user testing, to ensure that the software is installed correctly, works with our hardware, and works with our business processes. Finally, data capture for MI and benefits management.
Thanks! This has been really helpful. I am now armed with lots of questions to discuss with the suppliers next week. Saving Changes...