Long River Technology - Service Policy
There are great technical and business risks in software product development and project development, and the demand is often uncertain. Requirement discovery itself is also a resource-consuming project, but what many banks, group companies, enterprises and institutions need is a stable and robust system. Only the correct and appropriate process, communication, cooperation and understanding can achieve the goal of win-win.
The various software and services provided by LongRiverTech to customers must be confirmed by the "Risk Management Committee" and comply with various laws and regulations, regulatory compliance and industry norms. If LongRiverTech discovers that customers use the company's software and services to engage in illegal activities during the process of providing services, LongRiverTech will immediately stop the service and will not refund the various service payments received. LongRiverTech will not bear any losses and responsibilities caused thereby.
1. Legal compliance
The various software and services provided by LongRiverTech to customers must be confirmed by the "Risk Management Committee" and comply with various laws and regulations, regulatory compliance and industry norms.
If LongRiverTech discovers that customers use the company's software and services to engage in illegal activities during the process of providing services, LongRiverTech will immediately stop the service and will not refund the various service payments received. LongRiverTech will not bear any losses and responsibilities caused thereby.
2. Cooperation Process Framework
There are great technical and business risks in software product development and project development, and the demand is often uncertain. Requirement discovery itself is also a resource-consuming project, but what many banks, group companies, enterprises and institutions need is a stable and robust system. Only the correct and appropriate process, communication, cooperation and understanding can achieve the goal of win-win.
In order to achieve the respective goals of the cooperation parties, the following general process framework is determined:
Think big, act small, fail fast, learn rapidly.
Identify the right project type to employ different segmentation processes and best practices to capture maximum customer value at minimum cost and risk.
Common project types include, but are not limited to: solution consulting, technical consulting, business consulting, product development, project development, project implementation, customer service, technical support.
For the successful execution of the project, multiple partners need to be aware of the importance of the following:
(1) Customer interaction
(2) Human capital and resources
(3) Contracting, stakeholder management and negotiation
(4) Lean and concise
3. Overall Policy Description
(1). LongRiverTech's self-developed products and customized development projects based on customer needs will use various technical assets that LongRiverTech has continuously accumulated. The cost of asset pricing and division of asset scope is so high that it is often impossible to complete, so the relevant intellectual property rights are defaulted It is held by LongRiverTech, the original independent developer or the original third-party independent developer. If intellectual property transfer and technology transfer really need to occur, a detailed budget, training plan, asset division plan, consideration payment plan, and legal compliance review plan need to be formulated. After approval by the Risk Management Committee and the Strategic Development Committee, an executive director It can only be executed after a cooling-off period of one week. During the one-week cooling-off period, no other major decisions may be made at the same time. During this period, all previous decisions can be vetoed unconditionally and without reason.
(2). The design and development, delivery, training and other related services of the software or service system that LongRiverTech is responsible for must be completed within the tolerance period and quality of the plan or plan, and ensure that the software meets the customer's requirements. After the end of each phase of the project, LongRiverTech provides a project summary, the customer passes the acceptance, and after the project payment is made, the two parties can enter into the next phase of project cooperation. LongRiverTech shall not be responsible for the subsequent project delay or failure to meet the requirements due to the delay in payment by the customer.
(3). LongRiverTech shall not subcontract or subcontract the subject matter of the contract to a third party without the written agreement of the client.
(4). All legal consequences arising from the use of software and services provided by LongRiverTech shall be borne by the customer. LongRiverTech shall neither enjoy nor be liable for the profits or losses caused by the use of software and services by the customer, nor shall it be liable for any damages caused by system or other system failures. loss.
(5).LongRiverTech staff shall abide by the laws and regulations. According to the needs of the project, if they need to enter the customer's office or access the customer's information assets, they shall abide by the customer's rules and regulations, and shall not use the project work to seek any improper benefits; they shall not directly or indirectly handle or use any assets, futures deposits, stocks, reserve funds, credit or other movable property belonging to the customer from time to time for LongRiverTech's own use or to benefit LongRiverTech; shall not make or allow the customer or any of its affiliates Any act or thing by which any assets or other property may be seized to carry out an order, be secured or affected, or the interests of the Client or any affiliated company may be adversely affected or damaged.
(6). Customers should abide by laws and regulations, and the capital accounts operated in the production environment comply with laws and regulations. Only demo accounts are run in the test environment.
(7).LongRiverTech shall complete the project consulting, project planning, project management, project summary, demand analysis, design, coding, testing and training of the service system according to the customer's business needs.
(8). Software product delivery includes but is not limited to executable programs, technical documents, user guides, operation manuals, installation guides and test reports, etc.
(9).LongRiverTech and the customer promise to keep the designated confidential information confidential to each other. The confidential information may include but not limited to the following:
(a) The identity of customers and potential customers, their specific requirements, personal contact names, addresses and telephone numbers;
(b) prices, renewal dates, and other detailed terms of customer and supplier contracts and proposals;
(c) Pricing policies, how software and services are provided, marketing and sales strategies, and software and service development strategies;
(d) Bank, futures, stock and other financial accounts and password information;
(e) Source codes, object codes, specifications, user manuals, technical manuals and other documents of software products
(f) Screen design, report design and other designs, concepts and visual communication of software products;
(g) Payment records for services and items;
(h) forecasts, budgets, and other nonpublic financial information;
(i) expansion plans, management policies and other business strategies and policies;
(j) All communication documents, business card materials, lists of customers and potential customers, price lists, software, manuals, technical data, forecasts, budgets, records and all other materials containing any such information
(k) Information transfer During the performance period of this contract, any party can obtain the other party's business secrets related to this project
(l) The party who obtains the trade secrets of the other party in confidence can only use the trade secrets to perform its obligations under this contract, and only relevant engineering and technical personnel can use the trade secrets. The party that obtains the trade secrets of the other party shall adopt appropriate and effective methods to protect the obtained trade secrets, and shall not use, disseminate or disclose the trade secrets without authorization. Unless there is the written permission of the other party, or the information has been considered by the owner to be no longer a commercial secret, or has been made public, the commercial secret shall not be disclosed within __3__ years.
4. Project Management
4.1. Process
Because software development has certain uncertainties and risks, different processes should be adopted for different types of projects.
(a) Innovative projects with relatively high risks adopt the agile iterative method (Scrum).
A stage is a cycle, generally a stage is 2 weeks to 1.5 months. The project plan is completed at the beginning of the project. In principle, the project plan will not be changed during the project. After the project is over, there will be a project summary. The product release point and the project budget are determined during the project planning and paid after the project summary and acceptance.
(b) Lower-risk new feature development projects can adopt the cheaper Waterfall Model or CMMI.
Estimate the development cost and make a plan according to the existing framework and experience. The project cycle, project budget and project scope are determined when the project is established, and the project fee is paid according to the estimated time point during the project.
(c) Service, operation, maintenance, pure coding (excluding design and requirements) and pure testing (excluding design and requirements) projects adopt a fixed man-hour system and pay according to the service time.
(d) For banking or other critical businesses, use agile iterative methods that support innovation during the consulting phase, and write detailed requirements specifications, technical design plans, and test plans after completion. Then in the product development and project development stages, use the CMMI process to ensure the stability, robustness and maintainability of the system.
4.2. Communication
Communication modes mainly include but are not limited to the following:
(1). Project Intention
When Party A has a new project idea, Party B and Party A communicate and confirm the initial budget, goals, risk tolerance, quality requirement level, project process, and formulate the final project proposal for Party A's approval, and formulate the project plan after approval.
(2). Project plan
According to different projects, different processes are used for project planning and management, mainly the four types of projects described in the above process:
(a) High-risk innovative projects adopt agile iterative method (Scrum)
(b) Waterfall or CMMI processes for low-risk functional development projects
(c) Operations, support, and code-only testing projects use a fixed-hour service process.
(d) Banks, groups or other critical systems where both innovation and robustness are required.
After the communication between Party B and Party A, Party B submits the detailed project plan, and the implementation starts after confirmation.
The project plan mainly includes: budget, objectives, risks, quality, processes, functions, schedules, human resources, asset consumption and rental, procurement, important meetings, communication plans, etc.
(3). Project Summary
After each project is completed, a project summary will be made.
Party B will file in the form of documents.
The project summary mainly includes: project actual cash flow, goal achievement, delivery function list and screenshot display, task execution status, resource consumption, procurement, other decision-making management, other creative management, and other related project introductions, etc.
The purpose of the project summary is mainly to facilitate project participants to observe the specific implementation of historical completed projects for various purposes, so as to better communicate, cooperate and make decisions.
(4). Phase asset evaluation
When a series of projects are completed and reach a predetermined milestone, due to subsequent key decision-making or strategic adjustment needs, after either party proposes the other party's consent, Party B will carry out stage asset evaluation activities.
Party B obtains the initial document based on statistical analysis of historical project data, which mainly includes the following contents: (a) investment and investment distribution (including cash, human capital and other capital, investment distribution in terms of time and type) (b) division of intellectual property rights ( c) Valuation of asset projects (d) Changes in asset shares and equity structure (e) Relevant project implementation review (relevant project actual and expected comparison) (f) Asset changes (including initial assets, value-added assets, loss or abandonment of assets) (g) ) asset project confidentiality level (h) asset market strategic plan, etc.
After Party B completes the asset appraisal, submit it to Party A for review, and after communication and revision, both parties sign and file.
(5). Demand Analysis
After the project proposal formulated according to the project intention is approved by Party A, Party B begins to organize resources to analyze the needs of the project.
After the demand analysis is completed, depending on the actual situation, there may be a separate demand analysis specification as an attachment and submitted to Party A for approval together with the project plan.
After the approval of Party A, Party B will start the follow-up project planning based on this.
(6). Project acceptance
When the project is nearing the end, Party B submits the project summary document, and Party A conducts user acceptance testing based on this.
During the acceptance test, problems encountered are divided into:
(a) Defects (Critical, Project Scope, Current Modification)
(b) Defects (generally, within the scope of the project, and can be modified after communication and negotiation)
(c) Defects (outside project scope, subsequent modification)
(d) New ideas (follow-up plan for further action)
(e) Using methods, processes or configurations (critical, within project scope, addressed by current training)
(f) Methodology, process or configuration to be used (generally, project-wide, addressed by follow-up training)
(g) Usage method, process or configuration (outside the scope of the project, follow-up development of training and operation and maintenance plan)
(h) Uncertain issues (does not affect the use of the project release function, follow-up observations to determine follow-up actions)
After the acceptance, the project summary document will be archived, and Party A will pay Party B according to project expectations.
(7). Brainstorming
When both parties have new ideas at any time, they can exchange ideas through various communication modes such as meetings, dialogues, telephone, WeChat, QQ, etc. Party B tries to record and organize relevant ideas, and submit them to Party A at an appropriate time or sort them out through meetings these thoughts.
Party A can choose certain ideas as the input of project intention, project plan and demand analysis.
(8). Conflict and dispute communication
The two parties try their best to record project decisions through accurate language expressions and documents to avoid conflicts and disputes.
Since innovative projects have many uncertainties and blurred boundaries, it is inevitable that many things are difficult to express clearly in the initial documents. Therefore, more friendly cooperation and mutual understanding between the two parties are required for such situations. When encountering a dispute, try to consider it as follows:
(a) For intellectual property rights, if there is no clear description and transfer process, it should be assigned to the original author as much as possible
(b) For project execution, select the appropriate level of risk and quality, and determine the tolerance for uncertainty
(c) For the type of project, select the appropriate budget size and management model, conduct appropriate upgrades, downgrades, early warnings, and suspensions at the appropriate time, control risks and adjust strategies in a timely manner
(d) with respect to the level of confidentiality,
(i) For information that does not specify a confidentiality level, in principle, it defaults to "(a) Designated Person Top Secret Level", and the designated person defaults to the person participating in the discussion and exchange.
When there are more than 5 participants, or there are non-core personnel, or external personnel participate, it will be automatically downgraded to "(d) Internal Core Confidential 3-year Grade", or "(f) Internal Confidential 1-Year Grade", or "(h) Specify External Publicity Level".
(ii) Information that does not specify a confidentiality level may be disclosed orally in some special occasions, but the information must be specially processed so that it contains at least 30% false information, such as saying that the figure of 1 million is 2 million , The 1-year project is said to be 3 years. For the picture information, it can be blurred or transferred by mobile phone, so that the specific numbers can not be seen clearly, and only the outline can be seen.
(iii) Information indicating the level of confidentiality shall be strictly implemented in accordance with the level standards
4.3. Risk
When doing project planning, list different risk levels for each function according to team experience, and obtain the overall risk level of the project after weighted average:
(0). No risk, completely on schedule, without deviation, or complete all project plan and expected projects ahead of schedule and within budget
(1). Minor risk, completely according to plan, deviation 85%~125%
(2). Small risk, basically completed as planned, but there may be delays, with a deviation of 85%~200%
(3).General risk, 50% can be completed as planned, and there may be delays, with a deviation of 85%~200%
(4). High risk, unpredictable project results, 20% of the plan can be completed, and there may be delays, with a deviation of 85%~200%
(5). Very high risk, unpredictable project results, basically uncontrollable project process
4.4. Quality
When doing project planning, project conclusion, and phase asset evaluation, select the following expected and actual quality levels:
(1). Not tested (including developers)
(2). Only the developers themselves have tested
(3). Manually tested, no actual user experience
(4.a). Manually tested, more than 1 user has used it for more than 1 day
(4.b). With automated testing, no actual user experience
(5). Manually tested, more than 1 user has used it for more than 1 week
(6). Manually tested, more than 1 user has used it for more than 1 month
(7). Manually tested, more than 3 users have used it for more than 1 month
(8). Manually tested, more than 3 users have used it for more than 1 year
(9). Have automated testing, more than 1 user experience for more than 1 month
(10). With automated testing, more than 3 users have more than 1 year of experience
4.5. Type
The following project types are selected as a reference when the project is established, and different processes and management methods are adopted to obtain the maximum benefit with the minimum cost risk:
(1). Micro projects
No budget or unclear budget;
proof of concept or trial;
The period is less than 8 weeks;
The cost is less than 10,000 yuan;
(2). Small projects
have a specific budget;
Have a clear project plan;
The period is less than 3 months;
The budget is within 100,000 yuan;
(3). Medium-sized projects
have a specific budget;
completed in multiple stages;
The period is less than 1 year;
The budget is between 100,000 yuan and 1 million yuan;
(4). Large-scale projects
There is an approximate budget for each stage;
Completed across the year;
Responsible for the detailed operation of the project;
The budget is between 1 million yuan and 10 million yuan;
(5). Mega Projects
phased planning;
Completed across the year;
Responsible for the overall operation of the project;
The budget is more than 10 million yuan;
(6). Investment Project - Proof of Concept
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: 100-10,000 yuan
Risk Level: Very High (None, Minor, Small, Fair, High, Very High)
(7). Investment project - prototype (framework, technology, product, process, organization)
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 1,000-100,000
Risk Level: High (None, Slight, Small, Fair, High, Very High)
(8). Investment Project - Angel A
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 10,000-1,000,000
Risk Level: Fair (None, Minor, Small, Fair, High, Very High)
(9). Investment Project - Angel B
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 100,000-10,000,000
Risk Level: Fair (None, Minor, Small, Fair, High, Very High)
(10). Investment Project - Venture Capital A
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 1,000,000-100,000,000
Risk Level: Fair (None, Minor, Small, Fair, High, Very High)
(11). Investment Project - Venture Capital B
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 10,000,000-500,000,000
Risk Level: Fair (None, Minor, Small, Fair, High, Very High)
(12). Investment Project - Venture Capital C
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 100,000,000-1,000,000,000
Risk Level: Fair (None, Minor, Small, Fair, High, Very High)
(13). Investment Project - Equity Investment A
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 1,000,000-100,000,000
Risk Level: Small (none, tiny, small, fair, high, very high)
(14). Investment project - equity investment B
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: RMB 10,000,000-1,000,000,000
Risk Level: Small (none, tiny, small, fair, high, very high)
(15). Investment project - equity investment C
Have investment target planning;
Not paying attention to the details of project operation;
Only care about the operation results of the project;
Investment budget: more than 100,000,000 yuan
Risk Level: Small (none, tiny, small, fair, high, very high)
5. Relevant various needs
5.1. Business needs
Business needs refer to the ability to meet the needs of customers in terms of strategic development and evolution, new business development, reducing existing business operating costs, enhancing existing user experience, etc., and can have a positive impact on the customer's balance sheet or cash flow statement within the expected time idea. This idea may be expressed by customers in different ways. Due to different thinking angles and professional responsibilities, for a real business need, different people express and communicate in different ways, and the recipients of the information may also understand it differently. Business or technical architecture consulting experts with extensive experience in related fields can use professional methods to help guide and discover real business needs and help make correct investment decisions. False business needs can lead to irreparable failure of the project, ultimately affecting the survival of the organization.
5.2. Business requirements
Business requirements refer to the clearly described functional scope, business logic, execution process, logical relationship, and calculation formula method. It can be easily written as executable code by software developers, and can also be easily written as executable test cases by software testers. Decomposing a business need into high-quality business needs requires business analysts to use professional methods to communicate with stakeholders, analyze, investigate, statistics, prototype experiments, feedback, and write documents. Wrong business requirements will seriously affect the realization of business needs. The cost of later modification may be 10 times that of design errors, and 100 times that of development and implementation errors, which will ultimately affect the survival and stability of small teams.
5.3. Technical requirements
Technical requirements refer to the technical implementation details that must be met in order to achieve business needs. If these technical requirements are not realized, the following problems may occur but are not limited to:
(1). Business requirements cannot be realized
(2). Unstable performance causes users to give up using the system
(3). The system is still maintained and operated so that it is impossible to diagnose and solve system failures within the expected time cost, resulting in serious user disputes and possible loss of users
(4). Security risks lead to exposure of sensitive and confidential information
(5). Cannot expand horizontally with the development of the number of users
(6). It cannot be integrated with other dependent system interfaces
(7). It cannot be changed with the evolution of user habits
Common technical requirements include but are not limited to the following categories:
(1). Performance
(2). Log
(3). Security
(4). Audit
(5). Extension
(6). Specific technical limitations
(7). Move
(8). Internet
(9). Big data
(10). Integration
(11). Interface
(12). Cloud Computing
5.4. Customer Experience
Customer experience is a purely subjective feeling established in the process of using the product by the user. Factors that affect customer experience include, but are not limited to:
(1). The overall operation behavior of the system
(2). Performance and response time
(3). Interface element layout color design
(4). Business processing method
(5). Whether to support mobile devices
(6). Whether to encourage users to participate in the detailed process
(7). Whether the system is robust
(8). Is it easy to guide users to make mistakes
(9). User Interaction Design