The standard implementation is carried out in the project implementation method of Sure Step, and the introduction process focuses on the difference analysis of the consultant based on the results of the customer process and demand interview, and follows the Dynamic 365 Best Practice (best practice) to cooperate with the standard functions and modules of the system for project import.
Analysis phase
Requirement analysis and process confirmation
Design phase
Difference analysis and prototype establishment
-
Business Process Requirements Interview:
Through the interview questionnaire, the future business process and functional requirements are understood and recorded, and the format of the existing report is collected. -
Writing and Validating Requirements Interview Transcripts:
According to the conclusion of the business process requirements interview meeting, a 'requirements interview record' document is generated, which is signed by the participants as the basis for drawing the future operation process.
After the system is launched, explain the future (To-Be) system function specifications and operation flow chart.
- The To-Be Flow is subject to repeated confirmation by both parties, and during the confirmation process, the To-Be Flow diagram is adjusted.
- The future operation proposal is based on the confirmed future operation flow chart (To-Be Flow), and contains the actual steps and screens in the prototype system, which is the definition of the scope and function of the system launch by both parties, and is also the standard for acceptance by both parties.
- The future work proposal needs to be confirmed by both parties, and in the process of confirmation, the content of the original future work proposal needs to be adjusted.
On the To-Be Flow diagram, some of the jobs are not available in the existing Microsoft Dynamics system, and the documents to be delivered by the consultant, as well as the estimate of the time required for development and testing, need to be signed off by both parties.
Based on the confirmed To-Be Flow as a blueprint, we will adjust the configuration of the system and make a trial transaction with the aim of establishing a tangible prototype system that will serve as the basis for communication and confirmation between the two parties.