Alpha Phase Project Summary

One, the vision and the goal

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

For railway University students, to solve their spending money confused, do not know the whereabouts of the issue of income. is clearly defined. We have a clear description of typical users and typical scenarios, and our software helps them to plan their money rationally and to define the ratio of revenue and expenditure.

2. Do you have enough time to plan?

There is plenty of time to plan.

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

We will discuss and choose the best possible views and plans, and we will use the voting method.

Second, the user volume, the user to the important function acceptance degree and our beforehand anticipate agree? Are we closer to the target?

The number of users is less than we had expected beforehand. The user's acceptance of important functions is more consistent with our prior assumptions. This is a leap from scratch, and obviously we are closer to the target.

Three, what lessons do you have? If history does it again, what improvements will we make?

Improve team members ' motivation.

Four, plan

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

Is.

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

Found out.

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

Is.

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

Is.

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

No buffer left

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

will improve the bookkeeping function.

7. What have we learned? If history does it again, what improvements will we make?

The daily stand-up meetings are more efficient and should be invested in software projects with greater enthusiasm.

Five, resources

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

More adequate.

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

Based on the team member's programming ability and proficiency estimate, more accurate.

3. Is the test time, manpower and software/hardware resources sufficient? Do you underestimate the difficulty of resources that do not require programming (artwork design/copywriting)?

Enough. indeed underestimated.

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

Yes.

What lessons do you have? If history does it again, what improvements will we make?

The first sprint stage should be more carefully selected for their own tasks, so that the division of labor more clearly.

Vi.. Change Management

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

Is.

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

Vote.

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

Yes.

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

Yes.

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

In some cases, some of them can.

What have we learned? If history does it again, what improvements will we make?

To have plan B

Seven, design/implementation

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

Team leader, yes.

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

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?

Yes, effective.

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?

Delay jump interface, there is a flashback, no prediction.

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

Is.

What have we learned? If history does it again, what improvements will we make?

Be more rigorous.

Eight, test/release

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

Yes.

2. Have you conducted a formal acceptance test?

Yes

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

Is

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

Useful through effective reviews.

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

Need to be audited.

Nine, Summary:

1, what do you think the current state of the team belongs to in Cmm/cmmi?

The most low

2, which stage do you think the team is currently in the bud/Run/spec/creative phase?

Specification

3, what do you think the team has improved in this milestone compared to the previous milestone?

From scratch

4, what do you think is one of the most necessary improvements in the present?

Task Division.

Alpha Phase Project Summary