Summary of Beta Milestones

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?

The problem is that the software program writer cannot find the code that was previously written, the definition is basic and the team members know it, and the typical user and typical scenario are clearly described from the database administrator's perspective.

2. Do you have enough time to plan?

The time between two sprints our team made a detailed plan and division of labor.

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

Intense discussion, so as to produce results.

user volume, user acceptance of important functions and what we anticipate in the same way? Are we closer to the target?

The user volume is similar to the idea, but the user seems to be demanding more, but closer to the target.

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

Be more fully prepared and discussed in more detail.

Plan

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

Not all finished, only completed a post, delete, modify the message function, because the original goal set is not appropriate, so only completed about 1/4.

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

This kind of thing is more, our division of labor is not particularly clear, on the project there are many do not understand the place, go a lot of detours, after all, is the first time to do, so after the experience.

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

Not clear, but you can ask.

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

Yes, but always finished, after all, no experience.

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

Yes, there is a week or so of buffer time, this time can improve the project, writing documents and so on.

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

The group also needs to strengthen cooperation.

What have we learned? If history does it again, what improvements will we make?
Set the final goal, not too high or too low, team members more cooperation.

Resources

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

There, library books, online tutorials, seniors learn elder sister's program

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

Task completion time is longer than expected, is based on workload, work difficulty and personal ability estimation, accuracy is not very high.

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

The test time is long, the manpower is not enough, the software/hardware is sufficient.

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

have, because they sometimes know the problem is not comprehensive.

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

Make reasonable arrangements for time, and strengthen communication among team members

Change Management

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

Yes, the message is changed by standing a meeting notice every day.

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

Members talk to each other, thinking that unimportant functions are deferred, such as publishing campus dynamics. It is necessary to realize the important functions and the related goals, such as adding and deleting messages and so on.

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

Version stable, functionality has been basically implemented, few bugs

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

Yes, the power of four people is limitless.

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

Yes

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

The way you work together can make your projects more successful, and set up a collaborative approach that fits our team.

Design/ Implement

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

Proposed by the leader Wang Hongwei, three members together ideas, after the team set up.

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

There, the team members discussed the unanimous conclusion.

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

Useful to unit tests, others not; more effective.

4. What features produce the most bugs, why?

There are many bugs in storing files in the database, and I don't know about this knowledge.

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

The two-bit members are checked for debugging and are basically compliant.

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

Standardizing a program for teamwork is not as simple as it is imagined.

Test/ Publish

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

Written a test plan.

2. Have you conducted a formal acceptance test?

No

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

No, I tested it myself.

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 user's use of feelings and feedback to correct.

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

A bit of a problem at the polling stage;

What have we learned? How will we improve if history does it again?

Summarize

What level of CMMI do you think the current state of the team belongs to?

Repeatable levels: A basic project management process is established to track costs, schedules, and features. The necessary process discipline has been developed to replicate the successful experience of previous similar applications.

Which stage of the budding/running/spec/creative stage Do you think the team is in?

Between the running-in and the specification.

How do you think the team is going to improve on this milestone than the previous milestone?

Team work more closely.

What do you think is the most necessary improvement in the present?

There is a periodic summary, the initial division of labor is not very clear, time estimation is not accurate, time is not sure good

Summary of Beta Milestones