First, hindsight analysis:
Vision and goals
1. Our software to solve the problem? Whether clearly defined? Is there a clear description of the typical user and a typical scenario?
The software is mainly to solve the ordering applet in the vicinity of the extension work on campus most of the features missing or incomplete, single issue menu style, our team believes that the definition was quite clear, and hope eventually to design a fully functional For such problems, businesses the kind of style rich, convenient take-away system. At the same time there is a clearer description of the typical user and a typical scenario, we focused on college students and universities located in the surrounding types of food businesses, to facilitate students eating habits, ordering them to save time and to such University City business a reservation system are also in great demand.
2. We reached the goal yet (function originally planned to do a few? Delivered as originally planned to deliver it? Originally planned to reach the number of users reached it?)?
Not yet reached our desired goal, the basic functions of the original plan have been completed, there are still some features not yet realized the need to improve the future, but we are basically in accordance with the time of delivery of the original plan. Since we do not have our software on-line, so there is no real users, but our internal team simulated users and businesses, the normal operation of the software
3. The amount of the user, the user's prior consistent with what is expected acceptance of the important functions and we? Our goal from the closer it?
Unfortunately our software is currently not able to on-line, so it is difficult to count the user acceptance of important functions, but within the team, our in-depth consideration of the needs of users, has been that most of the functions can be accepted by users. Of course, we are from the goal closer.
4. What are the lessons? If history all over again, what would we do to improve?
Lessons learned: This time we selected a software project from the departure point of view is good, but not in the expected amount of hard work engineering, leading to our team deeply feel the software project effort in the late development of huge, difficult to achieve our desired results within the expected time.
If history all over again, we would choose more suitable for the project within the expected time to complete the project, we expect to achieve results, the success of our project on-line, but also allows users to enjoy real-life use our software as much as possible.
plan
1. Is there enough time to do the plan?
Have.
2. Team at the planning stage is how to resolve the disagreement colleagues for planned?
Our team will conduct online discussions under multiple lines, also integrated in the planning stage as much as possible the views of each member, and the entire team for the views it would abandon plans to deviate from the deep in discussion.
3. You work planned if finally done? If you have not done, and why?
Yes, the original plan of work are done.
4. find that you do not have some hindsight did not need or do not count for much?
So far found no such events.
5. Is each task are clearly defined and measurable deliverables?
Yes.
6. The whole process if the project were carried out according to plan, the project what had happened? What are the risks was not estimated, why not estimated?
No, in the sprint stages of the project have appeared in the collapse of the server, this is our team of developers without first estimated, because our projects are simulated using internal users and businesses in the development process, and there is no the user is connected to the reality up, did not expect not put into actual operation of the server's collapse appeared (may build process server slight problem), but in the end developers successfully solved the problem!
7. There is no buffer left in the plan, the buffer role it?
not at all.
8. Future plans will do what changes? (Eg: buffer defined, overtime)
Leave plenty buffer.
If history all over again, what would we do to improve?
Clearly good business throughout the project, clearly define and assign each task.
Resources
1. We have enough resources to fulfill the tasks it?
- Human resources: In accordance with the proportion of tasks for various tasks are assigned a different number of members required for each task basic human enough.
- Development Resources: We have more team members are involved in the full project development, has a similar development experience and development resources are sufficient.
- Equipment Resources: equipment is relatively ample.
- Time resources: the development of the project due to some other experimental curriculum exams and so on, in terms of time are more compact, so the development time left for us but it is still inadequate.
2. The time and other resources required for each task is how to estimate how accuracy?
According to estimates of the task, the early estimates are less accurate, with the project, to grasp more deeply the entire project, will improve the accuracy of the estimation.
3. Test of time, manpower and software / hardware resources are sufficient? For those without programming resources (graphic design / copy) whether underestimate the difficulty?
Adequate basic resources, slightly underestimated the difficulty of non-programming resources.
4. Did you feel you can do something to let others do the (more efficient)?
Testing and development division of labor may need to be more clear, sometimes the Test side edge tune bug feeling very low efficiency.
If history all over again, what would we do to improve?
The division of labor is more detailed, rational use of human resources.
Change Management
1. Each relevant employees in a timely manner that the message changed?
Yes. Each member of the updated code will be uploaded to Github, and inform everyone in the micro-channel group; each member of the test interface found the document in question, we will update and inform you.
2. What measures we have adopted a decision "to postpone" and "must be achieved" feature?
Team analysis meeting the basic functions of the entire project, as a function that must be implemented, and some features of the project is too large or too difficult to achieve, you need to be postponed.
3. The conditions of export project (Exit Criteria - what "done") have a clear definition of it?
Have.
Our export conditions are able to support the number of users has reached 60 or more, and the number of businesses reached 15 or more, the normal registration, login, find the goods, order, order cancellation, the upper and lower commodity shelf, commodity merchants launch activities.
4. whether the specified contingency plans for possible change?
can. Because the back-end tasks usually done faster, so before the front end of the work not completed, if there is change possible, we also have a more adequate human resources and time.
5. Are employees can effectively deal with unexpected work request?
can. Sometimes the effect of temporarily increasing the expression or function of the page, we went together with the adjustment.
If history all over again, what would we do to improve?
Ahead to start the project, to complete basic functions, will be able to set aside more time to complete the extension, improve our project.
Design / realization
1. Design work at what time and by whom done? Is the right time, the right man?
Our design work completed by a developer with front and rear ends, such as database design and interface is done by Liuyou Bin and Chen Jingshan co-page designed by Lu Yuesheng and Jin Wentao together.
2. Design work has not encountered ambiguous situations, how the team is resolved?
No, the whole design work is rigorous discussion and exchange of developers, after roughly determine the design of the entire project, each module design we are very clear, the situation is ambiguous and does not appear.
3. Does the team use unit testing (unit test), test-driven development (TDD), UML, or other tools to help design and implement? These tools work?
Yes, in the development process, developers have used a variety of testing tools such as Junit, whether front-end or back-end are, these testing tools can effectively solve the problems we encountered in the development process.
4. What is the most versatile Bug produced, and why? After publishing discovered something important bug? Why did not we think of these cases in the design / development time?
Bug features the largest commodities produced, because the commodity function implemented on more complex than a variety of other functions, and the page button is basically the most, more likely to produce a variety of unexpected Bug when interacting with the user.
5. Code review (Code Review) is how to proceed, whether the strict implementation of the code specifications?
Each part of the code by the developer responsible for their own review of the development process, we strictly enforce a variety of pre-agreed code specifications.
6. If history all over again, what would we do to improve?
Earlier so that we together developed and tested (with a dormitory), there are problems in a timely manner will be able to discuss and timely solutions to improve development efficiency.
Test / release
1. Does the team have a test plan? Why not?
There are test plan.
2. whether formal acceptance testing?
Yes, for the various functions are tested
3. Does the team have the test tools to help test?
There, the development process has adopted a number of test tools, but it is acceptance testing manual testing.
4. The team is how to measure and track the effectiveness of the software? From the results of the actual operation of the software, these tests work useful? What improvements should have?
Performance software mainly refers to concurrency and stress testing, which is due to the equipment and human reason and not tested. The final results show that the testing operation is useful, I found a lot of potential problems not found before.
5. What unexpected problems found in the process released?
Server unstable and may crash.
Orders screen, click to confirm receipt could be charged again.
Second, summary
1. Do you think the current state of the team belongs grade CMM / CMMI in?
Reached CMMI Level two - level management degree.
2. Do you think the team is currently in its infancy / running / specification / create a stage which stage?
Bud, we still need more study, each member should enhance strength.
3. What do you think most need to improve aspects is?
Our team is currently in the development and subsequent testing distribution efficiency have not reached our desired results, it needs most is to improve the overall functioning and efficiency of the team, followed by running and communication between teams, AC frequency should be increased, enabling developers a little more harmonious and smooth.
Third, photos
Fourth, the contribution allocation
| first name | Roles | Team contribution points | Verifiable contribution |
| Liuyou Bin | rear end | 23 | Develop |
| Chen Jingshan | rear end | 22 | Develop |
| Jin Wentao | front end | 21 | Develop |
| Lu Yuesheng | front end | 19 | Develop |
| Wei Jianxiong | test | 18 | Testing and blog |
| Chen Haofeng | test | 17 | Testing and blog |