
4.8 : Configure Systems
Objective
Configure changes and enhancements of system software, hardware, and documentation throughout the life cycle.
View Lessons LearnedRecommended Best Practices
-
Provider
Document Configuration Workbook/Blueprint to understand data & system layouts
-
Provider
Create baseline system configuration and execute unit test to validate configuration changes
-
Provider
Assess and define batch jobs
-
Provider
Define and verify business process controls framework
-
Shared
Baseline and sign-off on functional and technical requirements
-
Provider
Develop functional and technical specifications for enhancement based on requirements
-
Provider
Code and unit test enhancements
-
Shared
Validate configuration & controls with customer Functional and Technical SMEs to validate enhancements meet needs
4.8 Lessons Learned
- Leverage functional specifications to support contact center team, test case, script development, training development, and user guide development
- Conduct Configuration Workbook validation after Conference Room Pilots (CRPs) to help the customer better understand the configuration options
- Consider hiring or staffing independent Enterprise Resource Planning (ERP) experts to provide unbiased configuration alternatives for the customer
Stakeholders
Recommended stakeholders, inputs, & outputs may vary by implementation; however, agencies that contributed to this Playbook reported these factors as increasing the likelihood of success.Customer
- Functional Lead
- Functional SME
Provider
- Program Manager
- Functional Lead
- Functional SME
- Technical Lead/Solution Architect
- Configuration Lead
- Development Team
Inputs
- Requirements Traceability Matrix (RTM)
- Requirements Fit-Gap Analysis
- Target State Architectural Solution
- Technical Strategy
- Configuration Management Plan
Outputs
- Requirements Traceability Matrix (RTM)
- Configuration Workbooks