Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

Project implementation process and specification template (test direction)

2025-04-05 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >

Share

Shulou(Shulou.com)06/03 Report--

1. Brief introduction

1.1 Writing background

With the rapid development of the company's business, the Technology Department is facing more and more construction projects, such as basic technology research and development, customer system construction, new product research and development, old system transformation and so on. However, with the participation of many technicians and concurrent project interaction, how to define and develop project implementation processes and management norms is becoming more and more important. From the current situation, there are many problems in our current project promotion process, such as:

L the preliminary requirements planning and design are not clear and the documentation is not detailed.

L the project stakeholders did not participate in the preliminary requirements analysis.

The division of labor of the project is unreasonable

L the problem solving process is not clear

L Historical problems and documents cannot be tracked

Over-reliance on RTX for transaction communication, which is inconvenient for transaction tracking

Based on this, the technical department needs to formulate and implement the project implementation process and corresponding management norms as soon as possible.

1.2 Writing goals

The aim is to achieve the following goals through the development and implementation of project implementation processes and management specifications:

L standardize the requirements, which is the foundation of the project

Reasonable arrangement of planning and scheduling

L refine the division of project modules

L optimize the problem handling process

L retain historical records and documents for follow-up tracking purposes

Get into the habit of checking mail in time

Through the process and norms, we can clarify the project construction objectives, construction scope, project stakeholders, and the scope of responsibilities of the members, standardize the project management, and strengthen the project process promotion.

1.3 document audience

The implementation process specification of this project is mainly for colleagues in the demand, development, testing and data department, in which colleagues in the data department can focus on the fourth part of the online problem handling process.

1.4 explanation of nouns

WBS: work breakdown structure (Work Breakdown Structure) the process of breaking down project deliverables and project work into smaller, more manageable components.

Redmine: an open source, Web-based project management and defect tracking tool. It uses calendars and Gantt charts to help visualize projects and progress. At the same time, it supports multi-project management. And project members can be notified in mail form in time for any problem changes.

two。 Project implementation flow chart

3. Interpretation of internal construction project process

The formulation, implementation and management of this process are combined with the actual application of the project management tool Redmine. Same as below.

3.1 requirements Analysis and Review

The declaration of requirements needs to inform the project stakeholders, and after analysis and review, the final requirements detailed documents and prototypes need to be produced and submitted to the designated SVN directory for management.

For general platforms such as the Unified Commission for discipline Inspection, the key requirement points must be documented so as not to cause omissions of function points.

3.2 Project planning and scheduling

At present, we do not have a clear process, so that people do not know when to submit the test, and do not know when to launch. The concept of project planning and scheduling needs to be gradually strengthened to address the quality of management and efficiency of a large number of parallel projects now and in the future. You need to pay attention to the following aspects:

L prioritize the project and produce a brief project plan

L the project plan should include important function points, submission test time points, launch acceptance time points and so on.

The above contents should be notified to all stakeholders of the project in a timely manner.

3.3 work breakdown (WBS)

WBS, namely work task decomposition, is an important concept in project management. You need to enter WBS into each project in redmine, and follow and implement the following points:

When a project is received, the project manager needs to assign work tasks to each member in detail, so as to facilitate the direct counterpart of the problem feedback process in the future, so as to avoid not knowing who the problem is fed back to.

The project manager can keep abreast of the work progress of each group member through WBS, know the overall progress of the project in real time, and control the project risk.

L for the maintenance of future projects, you can directly find counterparts to deal with, avoiding a lot of invalid communication.

3.4 requirements change

Requirements are the root of the whole project, and the quality of requirements directly affects the quality of the overall project. In order to respond to changes in requirements in a timely manner and reduce the development costs caused by changes, the following process must be strictly implemented:

Any changes must be updated to SVN in a timely manner.

L timely notify project stakeholders

If there is any objection to the change of requirements, the person in charge of the project will deal with it after consultation.

3.5 New Project

After logging in to redmine, click the navigation "Project" at the top left, enter the project list page, and click "New Project", as shown in the following figure, pay attention to the red box.

3.6 join a member

New projects must include all project stakeholders, including requirements initiators, development, testing, and data personnel.

The main roles are as follows:

3.7 New features, work schedule

The project manager needs to assign work tasks after completing the project creation and personnel addition. Please refer to the following steps:

1. To create a new feature (feature) or work schedule, I suggest you choose "work schedule" here.

two。 After receiving the work schedule, the relevant personnel should update the progress and status according to the actual situation, so that the project manager can check and understand the project progress at any time.

3.8 submit the test

When submitting the test, the project needs to inform the test point and enter it into the redmine, because some functions such as project briefing folder, attribute modification and so on need to be tested online.

3.9 New question

1. When creating a new question, testers must strictly select the tracking tag status, as shown in the following figure:

Choose what the question belongs to, because the attributes of each question are different and the process is different!

two。 Assigned to: the question to whom it belongs will be assigned to.

3.9.1 add a tracker

If the new problem needs to be notified to others, you can select the tracker so that the tracker can be notified of the change to deal with the problem

3.10 dealing with problems

When a question is assigned to you, you need to deal with the update, and the relevant personnel should deal with the high priority ones as soon as possible. Please refer to the following steps:

1. Go to the specific question page and click Update

2. Update the "status" and update the "assignment" as the original question author.

3.10.1 add a tracker

If you need to inform others of this question, you can find the "stalker" column, click add, and add the corresponding person, so that the designated tracker can be notified of the status of the problem.

4. 4 online problem handling process

Guidance and specification for online problem feedback for colleagues in the data department.

4.1 New question

Colleagues in the data department should pay attention to the following points when creating new questions:

1. Track the tag. If it is an online problem, select "online bug".

If it is a suggestion, choose "suggestion". Please choose it strictly according to the requirements.

2. Assigned to, must be assigned to testers, not to anyone else.

4.1.1 add a tracker

If you want to inform others about the problem, please refer to 3.9.1.

4.2 deal with the problem

Please refer to 3.10.

5 outsourced projects

Refer to 1 internal project process specification, in which the input of outsourcing personnel is best with only one interface person, and the authority should be controlled well, which is convenient for management and post-processing.

6 description of mail mechanism

In the whole project process, the establishment of e-mail reporting and notification mechanism is very important, and we will gradually strengthen our email awareness in the future.

In addition to small projects, other projects should have the flexibility to develop a reporting mechanism to inform relevant personnel by e-mail, such as daily or weekly report mechanism. focus on what you are doing and progress, what you need to support and help, what you are going to do in the future, and your plans, simply and clearly.

7 online criteria

At present, there are no restrictions on our launch, and sometimes we go online when there are many bug unresolved. In order to standardize the launch criteria and improve the quality of the products delivered to customers, we now need to meet the following specifications before delivery.

1. High weight bug is resolved and closed.

2. All ordinary bug will be resolved and closed.

3. Low-weight bug, temporarily unresolved or postponed bug requirements can only be agreed by the relevant personnel.

8 problem solving cycle

1. The problem of high weight must be solved in time.

2. General problems need to be solved within two days if there is no emergency.

3. You need to give a clear schedule for solving the remaining problems, which can be explained in the corresponding problems in redmine.

9 other

Install email client software and check email notifications in time

Give priority to energy to solve high-weight and urgent problems

Update the status of the problem in redmine in time and refuse to cash it verbally

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Internet Technology

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report