During the onboarding process, clients must approve any custom functionality before development work can begin.
Business Analysts will work with clients to discuss any requirements or needs that must be fulfilled and will create a document detailing client specifications. A Business Analyst will meet with a client to create a specifications document that must be approved before development begins.
The following information captures what the client's instance of the system will look like and is used as a reference during the development process.
Figure 1 Client System Specifications Overview
|
Figure 2 System Implementation Phases 0 to 2
|
Project Phases
Figure 3 System Implementation Timeline
Phase 0: Pre-Business Analyst
Goal(s): Initial Application Build
Estimated Duration: 2-3 Weeks
Before meeting with a Business Analyst(s), the client must:
- Attend a working session with an Implementation Consultant(s)
- Capture requirements to build the application
- Review their initial setup
- Have a completed initial build of the application
Phase 1: Discovery and Alignment
Goal(s): Creation of the specifications document; Initial Configuration and Familiarization
Estimated Duration: 2-3 Weeks
During this phase, clients will meet with a Business Analyst(s) and Implementation Consultant(s) to identify requirements and confirm integrations and customizations. Using information gathered during this meeting, the Business Analyst will produce a document detailing the client's system specifications.
Phase 2: Refinement
Goal(s): Specification Refinement; Specification Signoff
Estimated Duration: 1-2 Weeks
A Business Analyst(s) will work with the client to review and sign off on the specifications document. If the client approves the original document, then the process will continue to Phase 3.
If the client adds new functionality and requirements to the list of specifications, then the Business Analyst(s) will create a new version of the specifications document. Once the document is approved, the process will continue to Phase 3.
Note: If the client does not approve the second version and additional specifications must be added, then the client will need to submit a change request. Each version created after the second as a result of changes requested by the client may incur additional costs and will impact the project timeline.
Phase 3: Development and Phase 4: Quality Assurance (QA) are combined
Goal(s): Development of customizations; Quality assurance engineer testing
Estimated Duration: 4-6 Weeks
Technical services will develop customizations based on the specifications document. Once initial development is complete, a developer(s) will work with a Quality Assurance Engineer(s) to ensure that the system is ready for the client to test.
Phase 5: User Acceptance Testing (UAT)
Estimated Duration: 2-3 Weeks
The client will perform User Acceptance Training (UAT) to test the completed system and ensure that all specifications are accounted for.
Phase 6: Deployment
Goal(s): Rollout the system
Estimated Duration: < 1 week
Note: Deployment times may vary from project to project.
After UAT is complete and the client has approved the product, the system will be deployed for use.
What else do you need help with?
Not what you're looking for? Navigate to Implementation Overview
Looking for training?
Explore this feature at your own pace - access training video content or watch a recorded webinar by clicking the link below.
