Team building-past experience review

Recently, the company hopes to begin rectification of the project process, so I hope to provide some related training to the team members.

Today is the first day and the first training for team members. Here, we have prepared a PPT for our own training materials.

 

As the first day, my personal thought is to summarize history and look forward to the future. What if history can give us another chance?

 

1. Review historical PPT downloads

 

At the meeting, I asked my colleagues to give some suggestions on the previous project experience.

 

A lot of opinions are collected, mainly concentrated:

Unclear requirements

Poor communication

Time shortage

Chaotic version release

No documentation

CodeNon-standard

Change demand at will

No unified defect Management Platform

I also mentioned these points in the PPT, so everyone may be deeply touched by them. We have categorized these issues once.

Question 1:The requirement is not clear and can be changed at will

To address this issue, we all agree that a standard processing process should be formed after the requirements are accepted.

1: The requirement personnel-Development-tests are used to analyze and organize the requirements. (The results are not fixed: What is the requirement specification? Is to form a unified consciousness)
2: development and testing are designed for the compiled results respectively, and test cases are designed (to form development documents and test cases)
3: After the design is complete, add a review link to ensure that there is no deviation between your understanding of the requirements and the design. If there is any deviation or you need to modify the requirements, repeat 1, 2.
4: encoding implementation starts after confirmation.
5. complete code review
6. Submit the version for test and development.
7. discover defects, submit defect reports, and develop and analyze and modify the reports.
8: Form A test report
9: officially released

 

But in this process, there may be defects and other problems. How can we report defects/problems? Communication is indeed a major obstacle.

Question 2: How to communicate

 

People in software development are the key. Therefore, communication between people naturally requires constant communication to generate a unified consciousness. How to communicate effectively is also a concern of everyone.

A unified management platform is required to support the entire lifecycle of software development.TFS.

 

Requirement: Submitted to TFs
Development: analyze and design implementation as needed
Test: design test cases as needed
Associate requirements-design implementation-test cases to form a unified whole.

Only in this way can we effectively track and analyze some of the requirements (changes) and act as a bridge between them.

 

The corresponding defect-targeting platform can also submit the defect to TFs and assign it to relevant developers for subsequent repair.

Other questions have not produced too many results in this discussion, but I will summarize the issues in the last few pages of the PPT.

Of course, the main purpose of this discussion is:

1. Review history and summarize experiences

2. Provide valuable suggestions and prepare for subsequent training and meetings.

Of course, the problem is still in the current stage, but how to solve these problems is the biggest problem!

I hope you will be able to help us with your suggestions.

Thank you!