The project that lasted for one year has finally been closed! Summarize your experiences over the past year!

Source: Internet
Author: User

A project that lasted for one year has finally been successfully completed, and everyone is very excited. It is necessary to hold a summary meeting to talk about our gains and losses over the year, let's talk about the things in our project. The following is a summary of the meeting. We will divide various ideas from three aspects: advantages, disadvantages, and suggestions. As a record of our own, we will share with you here:

Better performance

 

1.The progress of Phase II of the Project is reasonable and there is no overtime.

2.Standardized and unified projectDivAndCSSTo improve the development efficiency.

3.Every dayImMeetings andEmailCommunication works well.

4.The development and testing personnel in the team have a clear division of labor and a reasonable allocation of tasks.

5.The project team has a high accuracy in the preliminary evaluation of the task workload, ensuring that the projectScheduleAlways in a controllable state.

6.The servers in the project team are the responsibility of professionals, which facilitates project development and testing.

7.Team members are efficient in understanding, discussing, and giving feedback on project requirements.

8.In the face of many uncertainties and insufficient resources in the early stage, the team members work together to gradually track the project until it is finally completed.

9.Centralized team members ensure efficient team communication quality.

10.Team members are enteringBug trackerAnd the amount of information is comprehensive, saving a lot of time.

11.In the early stage of the project, the U.S. team had a comprehensive schedule and efficient requirement management, ensuring the quality of the project.

12.The U.S. team provided comprehensive support, not only providing high-quality Requirement documents, but also ensuring timely and effective communication.

13.Submitted by TesterBugHigh efficiency, and timelyReviewProblems.

14.The test team has good control over system problems, maintains high quality testing standards, and actively cooperates with developers to solve problems.

15.The collaboration between the development team and the test team is smooth, the team atmosphere is good, and everyone's enthusiasm for work is also high.

16.The development team is very efficient in tackling key technical difficulties.

17.LeaderThe progress and pace of the project are well controlled, ensuring the smooth progress of the project.

 

To be improved

 

1.There are a large number of project versions, and there is a lack of strict control mechanisms.

2.There are too few opportunities for team members to evaluate and discuss their needs.

3.Project security issues have not been paid due attention, resulting in the problem of page permissions in the future becomes a very difficult problem.

4.There are many functional modules to be abstracted in the project, and there is no time for further optimization.

5.Development Team membersReviewCodeThere are too few opportunities. Too frequent demand updates directly lead to incomplete understanding of the preliminary requirements.

6. in the regression testing process, many problems are exposed due to incomplete understanding of the preliminary requirements and loose test quality control.

7. it is necessary for the test team to strengthen test case quality, take care of all functional points as much as possible. Test Case Review the meeting was not implemented in the workshop and was not updated in a timely manner as needed test case , finally, test case result.

8.The second phase of the test is heavy, mainly because of the increaseTest CaseAs well as handling a large number of demand changes left over from the first phase.

9.Bug trackerThe priority settings are not strict enough, and the size control is poor,BugThe processing method options are incomplete and repeated.BugThe probability is high.

 

Good suggestions and ideas

 

1.In the process of Sino-US team collaboration, we recommend that you actively report some questions and opinions as much as possible.

2.ProcessingCSSWhen style or other issues may involve the overall project, we recommend that you handle them with caution to ensure the availability of the overall function.

3.Improvement based on local conditionsTest CaseIn order to play its role more efficiently.

4.We recommend that you enhance the projectScheduleTo reduce project risks.

5.If conditions permit, you can consider using parameter objects to connectBllAndDalLayer.

6.We recommend that you increase the number of communication activities among team members.

7.We recommend that you add periodic development and test summary exchanges as appropriate.

8.We recommend that you add a phased demonstration of the Project Sub-function module to increase the overall understanding of the requirements of team members.

9.We recommend that you further optimize the allocation and utilization of team members' resources.

10.We recommend that you add technical training activities within the team.

11.We recommend that you ensure consistency of the Code style in the project whenever possible.

12.It is recommended that team members should strengthen their global awareness of the project to discover more hidden problems.

13.We recommend that you try to improve the quality of your personal code and find a balance between performance and time.

14.PassEmailWe recommend that you handle the communication issues as soon as possible.

15.Some Test content is not fully performed according to the requirement document. We recommend that youTest CaseTeamLeaderIt is necessary to strengthen quality supervision.

16.Whether the development team or the test team, we recommend that you enhance the overall understanding of the requirements and increase the chance of meeting discussions as much as possible.

17.There are many ways to update the demand, which leads to the failure of strict tracking of some demand changes. We recommend that you passEmailOrExcel.

 

It is a good habit to cherish every opportunity you give and summarize your mental journey in time ~

 

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.