M2 Post-mortem analysis

Plan

1. Have you finished your original work? If there's anything unfinished, why?

The original plan was to modify the bugs found in the M1 phase and fix them. Test the software performance and increase the automatic update function.

2. Did you find that you did something that didn't seem necessary or valuable afterwards?

The M2 phase is more purposeful, but the process of solving the bug is more time-consuming.

3. Is there a clearly defined and measurable deliverable for each task?

Code test coverage, user experience, professional testing software.

4. Whether the whole process of the project was carried out according to plan, what risks were not estimated at that time, and why not?

Basically the whole project is in accordance with the plan, that is, at the end of the time is very tight, there are many courses to complete the big homework, late work is very hasty.

Resources

1. Do we have enough resources to complete the tasks?

members have no doubt that their ability to solve existing problems is only a matter of time.

2. How is the time and other resources required for each task estimated and how accurate?

The task is assigned to each developer according to the time and efficiency of the M1 phase.

3. Is the test time, manpower and software/hardware resources sufficient? Is it difficult to underestimate the complexity of resources that do not require programming (artwork design/copywriting)?

The testing time runs through the entire project development process, and the Copywriting and UI design also share some of the testing work without underestimating the difficulty.

Change Management

1. Every relevant employee is informed of the change in time?

The development phase will open daily meetings, every day we are through the QQ group to inform the message. TFS Check-in code.

2. What approaches have we adopted to determine the "deferred" and "must be" functions?

Because the basic functionality of the software is determined, we determine whether a feature is deferred or must be implemented around the basic functionality.

3. The export conditions of the project (exit criteria– What do you mean "done") have a clear definition?

We determine the export conditions of the software to be able to implement the basic functions of the guidelines, if it can be achieved, then can be published.

4. Can a contingency plan be developed for possible changes?

for some of the problems and challenges we met, we held a meeting to discuss the solution in time. Because in the project, we set up two people on the front end, there are two people on the back end, and a mobile staff, the relative ability is stronger, can handle some emergency events at any time.

5. Are employees able to effectively handle unexpected job requests?

from the founding of the team to the present, none of us have given up on our work because of slacking off, and everyone has almost 200% enthusiasm to deal with the project. Unexpected job requests occur on a daily basis, mainly because there are too many problems in the original code, so that in the process of development, it takes more than one time to repair, rather than to create.

Design/implementation

1. When and by whom is the design work done? Is it the right time for the right person?

In the M1 phase of the summary of the time has designed the M2 phase of the task, by everyone to discuss the decision.

2. Is there any ambiguity in the design work and how does the team solve it?

No, No.

3. Does the team use unit test, test-driven development (TDD), UML, or other tools to help design and implement? Do these tools work?

using the unit test, Baidu developed the test software.

4. What features produce the most bugs, why? What important bugs were found after the release? Why didn't we think of these when we were designing/developing?

See bug list.

Test/Release

1. Does the team have a test plan? Why not?

There, according to the teacher's request.

2. Have you conducted a formal acceptance test?

on the Baidu test software.

3. Does the team have testing tools to help test?

Baidu's Test software, UML.

4. How does the team measure and track the performance of the software? Is it useful to see how the software actually works? What should be improved?

The main test with Baidu software, according to the results.

5. What unexpected problems were found during the release process?

not at the moment.

Summarize:

1. The server can not accommodate many groups at the same time, resulting in the end of the project due to the server for a lot of time delay.

2. Whether the start time of the project can be in advance, many of the major tasks in the late years are in conflict with the soft workers, and there is no way to strictly follow the timetable.

M2 Post-mortem analysis