M1 post-mortem analysis report summary

Genius website Project Postmortem results

Vision and Objectives

1. What problems does our software solve? Is it clearly defined? Do you have a clear description of typical users and typical scenarios?

Genius website provides an online base for computer learning, where you can upload and download public resources, you can ask questions, you can search for problems that have already been solved, and you can search the tags to see the pages under the tag. The main users of the university computer-related professional teachers and students and engaged in the field of computer work people.

2. Do you have enough time to plan?

There is a week or so of time to plan, the time can be.

3. How does the team solve the different opinions of their colleagues about the plan during the planning phase?

A vote of hands

Plan

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

Have not finished, such as file upload download has not been implemented. Because there is a period of time used to do some auxiliary functions above, but neglected the focus.

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

The above mentioned that there is a period of time in the pre-function, such as reward, anonymity and other functions, these features are not as important as uploading and downloading functions, but also not to say no value.

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

Most of them do not, and do not have a particularly precise measuring standard.

4. Is the whole process of the project in accordance with the plan?

Also, ready to complete search, integration, and resource upload and download in the M2 phase.

Resources

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

Time is tight.

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

Rough estimation based on algorithm implementation and the difficulty of UI programming implementation

3. Is the user testing time, manpower and software/hardware resources sufficient?

Not enough, the number of Team Test members and the number of hardware is far from enough.

Change Management

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

Team changes are made and notified in the discussion group and daily meetings.

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

Panel discussion, hands-on vote

3. Are the export conditions (exit criteria) of the project clearly defined?

Not very clear.

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

Panel discussion

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

Basically no unexpected requests.

Design/implementation

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

The general design has been completed in the last and last last, and what we have done is to perfect the design.

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

When there is disagreement, the team members are consulted to complete the compromise.

3. What features produce the most bugs, why?

Most bugs in user management.

4. How is code Review performed, and is code specification strictly enforced?

No review has been done, it is personal development, and then checkin for testing personnel.

Test/Release

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

Daily test tasks are discussed, as well as posted on blogs

2. Have you conducted a formal acceptance test?

No formal acceptance tests were conducted.

3. 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?

Use TFS to manage bugs for projects, changesets for projects, and tasks for members. Very useful. But not all bugs are documented in TFS and will be improved in M2.

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

Publish when deployed to the server after the input intranet IP open Web page-Reset the port;

Question or search will be error---index creation or lookup time need to call the Write.lock file is occupied by other resources, after the release is OK;

Integration of the time do not know how to use the second set of databases---has not been resolved, this is determined to M2 phase of one of the main tasks.

Question

1) In contrast to the principle of agility, what do you think is the best for your team?

Communicate with each other through daily meetings;

2) What is the next stage where M2 is to be improved? The more specific the better.

Strengthen self-management, in the regular meeting to the PM to ask the task of tomorrow to do;

Prioritize the tasks you want to achieve by prioritizing them according to their importance, first by completing the task with the highest priority.

Photo of post-mortem report meeting

M1 post-mortem analysis report summary