internal document - must-read

Precautions for low-code implementations of MiCount

Team Norms - quality standard - risk prevention - customer satisfaction

quality first

the customer reigns supreme

on time

Continuous optimization

What must be accomplished before a project can be initiated(crux)

1Contract and Authorization Review

Prior to project initiation, The following must be confirmed:

Clients have signed formal contracts, Clear payment terms(Advance payment has been received)
Platform authorization is available(username, cryptographic, Privilege level confirmed)
The scope of the project has been clarified(Function List, Delivery standards, Conditions of acceptance)
The project cycle has been finalized(milestone timeframe, Deferred processing program)
Responsible persons have been designated(project manager, Head of Technology, customer interface)

Prohibitions

❌ Implementation cannot begin without a contract

❌ No development resources may be invested without the receipt of an advance payment

❌ No commitment to delivery times without clarity of scope

2Requirements Research and Confirmation

In-depth requirements research must be completed:

Organize demand research meetings((say the) least3stakeholder participation: Client Services, our customersIT, arithmetic team)
Documentation of detailed requirements(textual description+flow chart+prototype)
Identify core pain points(prioritize: P0/P1/P2/P3)
Assessment of technical feasibility(Are platform capabilities met, Whether or not a second opening is required)
Written confirmation of requirements from the customer(mails/Confirmation of signature, Avoiding verbal commitments)

Risk Warning

⚠️ Unclear requirements are the number one reason for project failure

⚠️ All requirement changes must go through a formal process(written request+valuation+quote+recognize)

3Technology Selection and Architecture Design

Technology selection must be considered:

Whether platform capacity meets demand(functionality, performances, concurrency)
Data level assessment(prediction3Annual data volume, Consider scalability)
Integration Requirements Validation (Interfacing with existing systems: ERP/CRM/OA, etc.)
Security Compliance Requirements(Equivalency requirements, data privacy, Audit log)
Deployment options(fig. high in the clouds/privatization/hybrid deployment)

Considerations during project implementation(critical)

4Customer Communication and Expectation Management

Maintaining high frequency, Transparent communication:

Weekly progress reports(mails/sessions, Description of progress, concern, Next week's plan)
Timely synchronization of risks(Extension risk, technological difficulty, Insufficient resources)
Managing Customer Expectations(No overcommitment, Non-concealment of issues)
Record all communications(written summary of a meeting, mail exchange, WeChat Screenshot)
Change Management Process(Changes in requirements must go through formal approval)

5Code Quality and Specification

Ensure code maintainability:

naming convention(form (document), field, workflows, universal function naming)
Annotation specification(Critical logic must be commented, Convenient for post-maintenance)
code reuse(Avoid duplication of development, Wrapping public components)
Test Coverage(Functional Testing, boundary test, stress test)
Code review(Critical modules must go throughPeer Review)

6Data Security and Backup

Data security is the bottom line:

privilege control(least authority principle (LAP), Periodic review of competence)
data backup (Daily Backup, Retain at least 30 days)
Sensitive data desensitization(Test environments don't use production data)
operating log(Documentation of critical operations, Easy traceability)
safety training(Client administrators must receive security training)

strictly prohibited

❌ Prohibit direct testing in production environments

❌ Prohibition of disclosure of customer data

❌ Prohibit the use of weak passwords(Must comply with strong password rules)

7performance optimization

Focus on system performance:

Query Optimization(Avoid full table scans, indexing)
Process Optimization(Reduce unnecessary approval nodes)
Front-end optimization(Reduce page load time)
concurrent testing(Simulation of peak usage scenarios)
Monitor Alarms(Setting up Performance Monitoring, Timely identification of problems)

Project delivery and acceptance criteria

8User Training and Documentation

Training must be completed prior to delivery:

Administrator training(System Configuration, Rights Management, Data Maintenance)
End-user training(basic operation, Frequently Asked Questions)
Preparation of training materials(operation manual, video tutorial, FAQ)
Evaluation of training effectiveness(check up on, poll)
Archiving of training records(sign-in sheet, Training Photos, Assessment results)

9Go-live preparation and switchover

Pre-launch checklist:

Production environment preparation(Account Opening, Privilege Configuration, Data initialization)
Data Migration Validation(Historical Data Migration, data integrity check)
performance stress test(Simulation of real scenarios, Ensure performance to standards)
Backup Solutions(data backup, Rollback program)
emergency plan(Troubleshooting Process, List of contacts)

10Acceptance and handover

Formal acceptance process:

Function Demo(Demonstration of itemization according to the contract list)
Customer Acceptance Testing(Customer Hands-on, Problems found)
Problem rectification(Documentation of the list of issues, time limit for rectification)
Receiving and Inspection Report(Written acceptance report, Signature of both parties)
Handover of deliverables(source code (computing), (computer) file, username, Training materials)

After-sales Services and continuous optimization

11Response Time Commitment

Hierarchical response based on the urgency of the problem:

P0 (system crash): 15Response within minutes, 2Resolved within hours
Level P1 (Core function failure): 30Response within minutes, 4Resolved within hours
P2 (General functionality issues): 2Response within hours, 1Resolved within one working day
Level P3 (Optimization Recommendations): 1Response within one working day, scheduling on a case-by-case basis

12Regular inspection and optimization

Proactive Services, Prevention of problems:

Monthly health checkups(Performance Monitoring, log analysis, Competence review)
Quarterly Optimization Recommendations(Optimization solutions based on usage)
Annual escalation planning(Platform version upgrade, functional enhancement)
User Satisfaction Survey(Regularly collect customer feedback)

13Knowledge deposition and reuse

Project experience archive:

Project summary report(success stories, Pothole Record, Suggestions for improvement)
Technical Solutions Documentation(architectural design, core code, Tackling the Difficulties)
Component library deposition(Generic Component Extraction, For reuse in subsequent projects)
Best Practice Sharing(In-house team training, Knowledge base update)

final reminder

✅ quality first I'd rather slow down., Ensure quality as well

✅ the customer reigns supreme Put yourself in the customer's shoes

✅ Teamwork Ask for help when you have a problem, Don't go it alone.

✅ continuous learning Focus on the new features of the platform, Upgrading of technical capacity

❌ Prohibition of unauthorized commitments Out-of-scope needs must be escalated for assessment

Back to Customized Implementation Center