First, background

In the field of software development, process collaboration has always been one of the hot topics. In different organizational structures, the scope of responsibility of different roles and personnel should be defined, and the connection mechanism between different roles should be managed through process specification, so as to continuously improve the efficiency of collaboration.

The core elements of

  • Roles: Roles are configured differently in different organizational structures, and roles and personnel have a clear correspondence.
  • Responsibilities: The definition of responsibilities for different roles, used to clarify the stages and times of involvement in the process;
  • Flow: Define the sequence of nodes in the flow according to the scenario, such as development, testing, and deployment.
  • Node: make clear the responsible roles of different nodes and act as the facilitator for the orderly completion of nodes;

Reasonable process management mechanism is conducive to efficient work; In order to avoid excessive complexity of process collaboration, it is necessary to establish collaboration rules, such as three (or two), the first person responsible and so on.

Second, the routine process

Products go through multiple key nodes from demand to release. In the process of collaboration, problems at any stage will have an impact on the upstream and downstream of the whole process. Therefore, appropriate requirements should be set for the quality of output results at each node to avoid repeated low efficiency.

The details can be seen from the following four aspects: product demand, project management, RESEARCH and development management, and project summary. Mastering these key stages will greatly improve the stability and efficiency of the team.

Third, product demand

  • Collection: receiving requirements from multiple sources, including business side, product planning, system optimization, architecture upgrade, etc.
  • Sorting out: sorting out the collected requirements, making overall planning and implementation plans according to important and urgent strategies, and providing preliminary documents;
  • Business review: give the business (demand) side the process management, the operation diagram of the first version of the product, align the expectation in the heart;
  • Technical review: perfecting detailed rules of requirements, evaluating rationality, realizability, complexity, risk and other related issues;

As the most upstream node of software development, product requirements stage must output product documents with clear requirements, in line with business expectations, and technically achievable. After consensus is reached by all parties, relevant personnel shall be notified by email to indicate the completion of the work in the current stage.

Iv. Project management

Project management is a complicated affair, usually divided into four stages: start-up, implementation, monitoring and ending, so as to realize the control of “quality, cost and time” of the project. Most companies pursue to reduce time and cost without reducing quality, thus forming the internal volume state of the Internet.

  • Start-up: the start-up stage mainly refers to the reasonable allocation of resources, project man-hour evaluation, milestone node definition and other matters;
  • Execution: in software development, that is: UI design, development and implementation, testing, online deployment and a series of processes;
  • Monitoring: the key point is the progress and risk, the pace of progress follow-up, as well as the possible risk judgment and solution;
  • Closing: quality acceptance of the project, review and summary of the whole process, and notification of relevant personnel;

Project management, as a basic ability in the workplace, is worth accumulating for any staff, and they often think about how to optimize management strategies and methods, so as to make things more efficient and organized.

Research and development management

Research and development is a time-consuming and problem-prone stage, so at this point, careful management and promotion should be carried out, and the pursuit of quality should be put in the absolute first place, so as to avoid shoddy engineering due to the idea of “more, faster, better and less”, which will lead to higher cost of rework.

  • Preparation: in the early stage of version development, accurately understand the requirements, complete the dismantling of functional modules, and the corresponding time assessment;
  • Design: UI interface output, development of front and back end design, test cases, the completion of each node design review alignment;
  • Coding: front-end and back-end code implementation, API docking and joint adjustment, configuration changes, structural scripts, logical processes and other daily documentation;
  • Testing: development self-testing, professional testing, automatic script testing, UI visual acceptance, product functional process acceptance;
  • Release: pre-release environment simulation deployment, online grayscale environment release, formal production environment online, complete online acceptance;

As a development (back end) player for many years, the development process is roughly broken down into the following nodes, of course, this refers to the complex business implementation, the following process is rarely executed with awareness deviation:

The service side, in the face of the complex business is vital to translate requirements into the design, the first is to demand a comprehensive and detailed understanding of the many times in the process a little rules corresponding implementation costs are huge, the second is to conceive and design of the development process and output, and complete the project development review alignment, such basic can ensure smooth completion of the development.

Vi. Project Summary

In a complex project, it’s easy to overlook the final analysis and feel that the release will go live without any problems, and as a developer I always support this statement.

Complex business corresponds to complex product design, which also means long project cycle, namely high cost. Normal online use only means high quality of research and development, but the demand for the overall business and the rationality of product design need to be analyzed based on users’ use:

  • Embedded action: embedded action for each link of the business process, for the collection of behavioral data;
  • Log collection: Logs key API requests to analyze and judge the system and services;
  • Data analysis: classified and summarized the data of each core node in the business process to form a set of data analysis results;
  • Summary report: make objective analysis of product functions based on business requirements, and output necessary optimization plans;

Here mainly explain the analysis report, the data analysis is completed, give to the corresponding market or business people, or have professional point of view, the collection and summary of various opinions or Suggestions, objective assessment of ground product process, no matter good or bad are key factors need output, as the accumulation of experience and subsequent reference.

END