1 Introduction
1.1 Writing background
With the rapid development of the company's business, the technical department is faced with more and more construction projects such as basic technology research and development, customer system construction, new product research and development, and old system transformation. However, with the participation of many technical personnel and concurrent project interaction, how to define and formulate project implementation processes and management specifications becomes more and more important. From the current situation, there are many problems in our current project promotion process, such as:
l The early demand planning and design are not clear, and the documents are not detailed
l The project stakeholders did not participate in the preliminary demand analysis
l The division of labor is not reasonable
l The problem solving process is not clear
l Historical issues and documents cannot be tracked
l Excessive 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 specifications as soon as possible.
1.2 Writing goals
It aims to achieve the following goals by formulating and implementing project implementation procedures and management specifications:
l Specification requirements, this is the fundamental of the project
l Reasonable arrangement of plans and schedules
l Refine the project module division of labor
l Optimize the problem handling process
l Keep historical records and documents for subsequent traceability purposes
l Develop the habit of checking emails in a timely manner
Through the process and specifications, the project construction objectives, construction scope, project stakeholders, and the responsibilities of each member can be clarified, project management can be standardized, and project process advancement can be strengthened.
1.3 Document Audience
The implementation process specification of this project is mainly for colleagues in the requirements, development, testing and data departments, among which colleagues in the data department can focus on the fourth part of the online problem handling process.
1.4 Explanation of terms
WBS: 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 bug tracking tool. It aids the visualization of projects and progress with a calendar and Gantt charts. At the same time it supports multi-project management. The project members can be notified by mail in time for any problem changes.
2. 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. The same below.
3.1 Requirements Analysis and Review
The presentation of the requirements needs to inform the project stakeholders. After analysis and review, the final detailed requirements documents and prototypes need to be produced, and submitted to the designated SVN directory for management.
For general platforms such as the Unified Discipline Inspection Commission, key demand points must be documented to avoid omission of function points.
3.2 Project planning and scheduling
At present, we don't have a clear process, so people don't know when to submit the test or when to go live. The concept of project planning and scheduling needs to be progressively strengthened to deal with the quality of management and efficiency when dealing with a large number of concurrent projects now and in the future. The following aspects need to be paid attention to:
l Prioritize the proposed projects and produce a brief project plan
l The project plan should include important function points, test submission time points, online acceptance time points, etc.
l The above content should be notified to all project stakeholders in a timely manner
3.3 Work Breakdown (WBS)
WBS, or Work Task Breakdown, is an important concept in project management. You need to enter WBS into each project in redmine, pay attention to and implement the following points:
l When receiving a project, 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, and avoid not knowing who the problem is reported to.
l The project manager can grasp the work progress of each team member through WBS, understand 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 the counterparts to deal with, avoiding a lot of ineffective communication.
3.4 Requirements change
Requirements are the root of the entire project, and the quality of the 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 processes must be strictly implemented:
l Any changes must be updated to SVN in a timely manner
l Inform project stakeholders in a timely manner
l If there is any objection to the change of requirements, the project leaders will deal with it after consultation.
3.5 New project
After logging in to redmine, click "Project" in the upper left navigation, enter the project list page, click "New Project", as shown in the figure below, pay attention to the red box.
3.6 Join a member
New projects must include all project stakeholders, including requirements sponsors, development, testing, and corresponding personnel in the data department
The main roles are as follows:
3.7 New function, work arrangement
After the project manager completes the creation of the project and the addition of personnel, it is necessary to assign work tasks. Please refer to the following steps:
1. Create a new function (feature) or work arrangement, here I suggest selecting "work arrangement".
2. After receiving the work arrangement, the relevant personnel should update the progress and status according to the actual situation, so that the project manager can check the progress of the project at any time.
3.8 Submit test
When the project submits the test, it needs to inform the test point and enter it in redmine, because some functions such as project briefing folder and attribute modification need to be tested online.
3.9 Create a new question
1. When testers create a new problem, they must strictly select the tracking tag status, as shown in the following figure:
Choose whatever the problem belongs to, because the properties of each problem are different and the process is different!
2. Assigned to: To whomever the problem belongs.
3.9.1 Add Tracker
If a new issue needs to be notified to others, the follower can be selected so that follower can be notified of changes to address the issue
3.10 Dealing with problems
When an issue is assigned to you, you need to deal with updating the issue, and the relevant people need to deal with the high priority as soon as possible. Please refer to the following steps:
1. Go to the specific question page and click Update
2. Update "Status" and "Assign to" to the original issuer.
3.10.1 Add Tracker
If you need to notify other people about this problem, you can find the "Stalker" column, click Add to add the corresponding person, so that the designated follower can also be notified of the processing status of the problem.
4. 4 Online problem handling process
Guidelines for online problem feedback from colleagues in the data department.
4.1 New problem
Colleagues in the data department need to pay attention to the following points when creating new questions:
1. Track the label, if it is an online problem, select "Online bug";
If it is a suggestion, select "Suggestion", please select it strictly according to the requirements.
2. Assigned to, must be assigned to the tester and cannot be assigned to anyone else.
4.1.1 Add Tracker
If you want to let others know about this issue, please refer to 3.9.1.
4.2 Dealing with problems
Please refer to 3.10.
5 Outsourcing Projects
Refer to 1 Internal project process specification, in which the input of outsourced personnel is preferably only one interface person, and the authority should be controlled, which is convenient for management and post-processing.
6Description of Mail Mechanism
In the whole project process, the establishment of email reporting and notification mechanism is very important, and we will gradually strengthen email awareness in the future.
Except for small projects, other projects should flexibly formulate a reporting mechanism and inform relevant personnel through email, such as a daily or weekly report mechanism, focusing on describing what is being done and the progress, what needs support and help, what to do in the future and plans, simple and clear Just let us know.
7 Online Guidelines
At present, there are no restrictions on our online launch, and sometimes we go online when there are many bugs that have not been resolved. In order to standardize the launch criteria and improve the quality of products delivered to customers, we need to meet the following specifications before delivery.
1. All high-weight bugs are resolved and closed.
2. All common bugs are resolved and closed.
3. Low-weight bugs, bugs that cannot be resolved temporarily or delayed need to be unanimously approved by relevant personnel.
8 problem solving cycles
1. High-weight problems must be solved in time.
2. Ordinary problems, if there is no emergency, need to be solved within two days.
3. The remaining problems need to be given a clear scheduling solution time, which can be noted in the corresponding problems in redmine.
9 other
l Install email client software and check email notifications in time
l Prioritize efforts to solve high-weight and urgent problems
l Update the status of the problem in redmine in time and refuse to honor it verbally
1 Introduction
1.1 Writing background
With the rapid development of the company's business, the technical department is faced with more and more construction projects such as basic technology research and development, customer system construction, new product research and development, and old system transformation. However, with the participation of many technical personnel and concurrent project interaction, how to define and formulate project implementation processes and management specifications becomes more and more important. From the current situation, there are many problems in our current project promotion process, such as:
l The early demand planning and design are not clear, and the documents are not detailed
l The project stakeholders did not participate in the preliminary demand analysis
l The division of labor is not reasonable
l The problem solving process is not clear
l Historical issues and documents cannot be tracked
l Excessive 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 specifications as soon as possible.
1.2 Writing goals
It aims to achieve the following goals by formulating and implementing project implementation procedures and management specifications:
l Specification requirements, this is the fundamental of the project
l Reasonable arrangement of plans and schedules
l Refine the project module division of labor
l Optimize the problem handling process
l Keep historical records and documents for subsequent traceability purposes
l Develop the habit of checking emails in a timely manner
Through the process and specifications, the project construction objectives, construction scope, project stakeholders, and the responsibilities of each member can be clarified, project management can be standardized, and project process advancement can be strengthened.
1.3 Document Audience
The implementation process specification of this project is mainly for colleagues in the requirements, development, testing and data departments, among which colleagues in the data department can focus on the fourth part of the online problem handling process.
1.4 Explanation of terms
WBS: 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 bug tracking tool. It aids the visualization of projects and progress with a calendar and Gantt charts. At the same time it supports multi-project management. The project members can be notified by mail in time for any problem changes.
2. 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. The same below.
3.1 Requirements Analysis and Review
The presentation of the requirements needs to inform the project stakeholders. After analysis and review, the final detailed requirements documents and prototypes need to be produced, and submitted to the designated SVN directory for management.
For general platforms such as the Unified Discipline Inspection Commission, key demand points must be documented to avoid omission of function points.
3.2 Project planning and scheduling
At present, we don't have a clear process, so people don't know when to submit the test or when to go live. The concept of project planning and scheduling needs to be progressively strengthened to deal with the quality of management and efficiency when dealing with a large number of concurrent projects now and in the future. The following aspects need to be paid attention to:
l Prioritize the proposed projects and produce a brief project plan
l The project plan should include important function points, test submission time points, online acceptance time points, etc.
l The above content should be notified to all project stakeholders in a timely manner
3.3 Work Breakdown (WBS)
WBS, or Work Task Breakdown, is an important concept in project management. You need to enter WBS into each project in redmine, pay attention to and implement the following points:
l When receiving a project, 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, and avoid not knowing who the problem is reported to.
l The project manager can grasp the work progress of each team member through WBS, understand 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 the counterparts to deal with, avoiding a lot of ineffective communication.
3.4 Requirements change
Requirements are the root of the entire project, and the quality of the 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 processes must be strictly implemented:
l Any changes must be updated to SVN in a timely manner
l Inform project stakeholders in a timely manner
l If there is any objection to the change of requirements, the project leaders will deal with it after consultation.
3.5 New project
After logging in to redmine, click "Project" in the upper left navigation, enter the project list page, click "New Project", as shown in the figure below, pay attention to the red box.
3.6 Join a member
New projects must include all project stakeholders, including requirements sponsors, development, testing, and corresponding personnel in the data department
The main roles are as follows:
3.7 New function, work arrangement
After the project manager completes the creation of the project and the addition of personnel, it is necessary to assign work tasks. Please refer to the following steps:
1. Create a new function (feature) or work arrangement, here I suggest selecting "work arrangement".
2. After receiving the work arrangement, the relevant personnel should update the progress and status according to the actual situation, so that the project manager can check the progress of the project at any time.
3.8 Submit test
When the project submits the test, it needs to inform the test point and enter it in redmine, because some functions such as project briefing folder and attribute modification need to be tested online.
3.9 Create a new question
1. When testers create a new problem, they must strictly select the tracking tag status, as shown in the following figure:
Choose whatever the problem belongs to, because the properties of each problem are different and the process is different!
2. Assigned to: To whomever the problem belongs.
3.9.1 Add Tracker
If a new issue needs to be notified to others, the follower can be selected so that follower can be notified of changes to address the issue
3.10 Dealing with problems
When an issue is assigned to you, you need to deal with updating the issue, and the relevant people need to deal with the high priority as soon as possible. Please refer to the following steps:
1. Go to the specific question page and click Update
2. Update "Status" and "Assign to" to the original issuer.
3.10.1 Add Tracker
If you need to notify other people about this problem, you can find the "Stalker" column, click Add to add the corresponding person, so that the designated follower can also be notified of the processing status of the problem.
4. 4 Online problem handling process
Guidelines for online problem feedback from colleagues in the data department.
4.1 New problem
Colleagues in the data department need to pay attention to the following points when creating new questions:
1. Track the label, if it is an online problem, select "Online bug";
If it is a suggestion, select "Suggestion", please select it strictly according to the requirements.
2. Assigned to, must be assigned to the tester and cannot be assigned to anyone else.
4.1.1 Add Tracker
If you want to let others know about this issue, please refer to 3.9.1.
4.2 Dealing with problems
Please refer to 3.10.
5 Outsourcing Projects
Refer to 1 Internal project process specification, in which the input of outsourced personnel is preferably only one interface person, and the authority should be controlled, which is convenient for management and post-processing.
6Description of Mail Mechanism
In the whole project process, the establishment of email reporting and notification mechanism is very important, and we will gradually strengthen email awareness in the future.
Except for small projects, other projects should flexibly formulate a reporting mechanism and inform relevant personnel through email, such as a daily or weekly report mechanism, focusing on describing what is being done and the progress, what needs support and help, what to do in the future and plans, simple and clear Just let us know.
7 Online Guidelines
At present, there are no restrictions on our online launch, and sometimes we go online when there are many bugs that have not been resolved. In order to standardize the launch criteria and improve the quality of products delivered to customers, we need to meet the following specifications before delivery.
1. All high-weight bugs are resolved and closed.
2. All common bugs are resolved and closed.
3. Low-weight bugs, bugs that cannot be resolved temporarily or delayed need to be unanimously approved by relevant personnel.
8 problem solving cycles
1. High-weight problems must be solved in time.
2. Ordinary problems, if there is no emergency, need to be solved within two days.
3. The remaining problems need to be given a clear scheduling solution time, which can be noted in the corresponding problems in redmine.
9 other
l Install email client software and check email notifications in time
l Prioritize efforts to solve high-weight and urgent problems
l Update the status of the problem in redmine in time and refuse to honor it verbally