"Autopsy report."

Arithmetic App Project results

Finishing: Yang Linghu

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?

Our software to solve is because there is no time for children to give a question automatically to students to generate arithmetic problem. The definition is very clear. There are descriptions of typical users and typical scenarios. Think well but not enough time to be able to do it.

2. Do you have enough time to plan?

There's a little time, but it's not enough, and a lot of team members don't know how to use the time to plan, and they don't know how to plan.

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

Communicate with each other, if the author has the ability to complete it will not be excluded.

Plan

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

It's mostly done, but there's still a lot of detail not perfect.

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

Yes, there are a lot of things to feel and it's no use, so we've gone a lot of detours.

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

No, there are some tasks that have been dragged on for some time to complete. And the definition is not good enough.

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

Not exactly, the first stage of the problem began to occur, the problem has not been solved, so trapped in there.

5. Are there any buffers left in the plan, and does the buffer function?

There is no buffer left.

6. What changes will be made to future plans? (example: definition of buffer, overtime)

Buffer should be established.

Resources

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

Resources are available, but difficult to find.

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

There is no specific time, but it can be done in the end.

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

Enough.

4. Do you feel that what you do can be done by others (more efficient)?

Yes, but a lot of people don't want to work.

Change Management

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

Know, we will be the first time to open an online meeting.

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

Hold the thought that must be realized.

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

No, I don't know what it is.

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

Some.

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

OK.

Design/implementation

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

The design work began at the outset and was completed by Yang Linghu and Yang Jiane. Yes.

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

Some, some work do not know who to do, there are some features of the opinions of different people, the meeting to discuss.

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

No

4. What features produce the most bugs, why?

Select the function, because the time is not enough, not enough to complete.

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

Test yourself and try it out.

Test/Release

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

No, because people do not pay attention to this aspect, and there is no time to do it.

2. Have you conducted a formal acceptance test?

Yes, there is a real finished product coming out.

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

No.

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?

Through the user trial to test, the user raised the problem, we will try to solve.

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

No.

"Autopsy report."