Afterwards Zhuge Liang meeting unfinished edition

2 assumptions and goals

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

2.1.1 Our software is primarily designed to address the students who find classrooms and record some urgent notes in a short period of time.

The 2.1.2 goal is defined to be clear, and the ability to choose an app is too much to be delivered on time to take into account all students and not individual students who really need the app .

2.1.3 has considered a typical user but no typical scenario has a clear description, resulting in fewer targeted users.

2.2. Do you have enough time to plan?

2.2.1 Did not have enough time to plan, all said the work "to good things, its prerequisite" but our team did not really first to improve the plan, are waiting until the problem arises when the way to do, and you, did not make plan B. The original work was completed and the unfinished part was not perfectly integrated with the other two UI groups and front-end pipeline . But this is mainly because the team did not coordinate well, and finally we volunteered to provide the data added API

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

2.3. How does the team resolve their colleagues ' disagreement about the plan during the planning phase? User volume, is the user's acceptance of important functions consistent with our prior assumptions? Are we closer to the target?

2.3.1 DN has been in a hurry, so most of the time is to listen to Daniel, resulting in the emergence of Daniel's mistake led to the loss of the entire project.

2.3.2 The user's acceptance of important functions is inconsistent with our prior assumptions, our original design class has been removed almost all of the functions, leaving only the original thought can be neglected function curriculum and Notepad.

2.3.3 No doubt we are closer to the goal, we have three of the ability to program the novice after a semester of exercise we have been familiar with the development of Android simple app .

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

Each person fighting each other, causes the whole team to do the function to be somewhat coincident, moreover everybody's data structure has the difference, has caused the great trouble to the code integration, at the same time, the software's specific function has not defined clearly. There is also a repetition of the writing text. The actual development progress completely does not meet the normal progress, the function is completely deleted. If we can get tired again our team must first plan to stabilize the output.

3 Plan

3.1. Have you finished your planned work at the end? If there's anything unfinished, why?

3.1.1 only completed the 20%.

3.1.2 because he is too lazy, everyone has to work for the expected team.

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

3.2.1 has, too focused on the distribution of interests and the entire team spent a few days to complete a meaningless login system.

3.3. is there a clearly defined and measurable deliverable for each task?

3.3.1 at this stage of development we do not clearly define and measure deliverables, resulting in the success or failure of our team projects and depending on individual individuals.

3.4. is the entire process of the project in accordance with the plan?

3.4.1 The whole process of our team's project is not in accordance with the plan, is to see the problem to complete the implementation.

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

No, are always in the mood to start, there is no fixed programming to make time.

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

3.6.1 in the future, we will set aside a class after class, if completed, the early return to the dormitory.

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

1. Use Google English search to learn more about popular open source solutions.

2. Reserve the necessary buffer time and leave it to the later integration.

3. To get rid of procrastination

4 Resources

4.1. do we have enough resources to accomplish the task?

4.1.1 We have enough resources to accomplish the task, but what we lack is a passion.

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

4.2.1 The first stage is the day to record, and the second stage is when we are.

4.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 ) ?

4.3.1 relative to the amount of work, is already more adequate, especially I have studied art.

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

4.4.1 No, according to the Pig is the chicken, at the bottom my efficiency can be achieved completely.

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

1. when estimating the time spent on a task, the time is accurate but also leaves the buffer.

2. leave the time for DEV to study.

3 to cooperate to complete the more difficult is.

5 Change Management

5.1. every relevant employee is informed of the change in time?

5.1.1 Yes, we have contact information Group, the main message we are in the inside notice.

5.2. What do we use to determine the "deferred" and "Must Do" features?

5.2.1 We use the Delete function to determine the "deferred" and "must do" functions

5.3. Is there a clear definition of the export conditions of the project (exit Criteria – What do you mean "done")?

5.3.1 not clear .

5.4. can a contingency plan be developed for possible changes?

5.4.1 We are able to make contingency plans for possible changes.

5.5. are we able to effectively handle unexpected learning requests?

5.5.1 We are not able to handle unexpected job requests effectively because we are just in touch with android development.

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

1. QQ Mutual transfer files.

2. multiple open brief meeting or email notification, less by SMS notification .

3. please call to learn the experience of seniors.

6 Design/implementation

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

6.1.1 requirements are too large.

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

6.2.1 have, through communication.

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

6.3.1 through its own mobile phone to achieve debugging.

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

6.4.1 Notification alert function

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

6.5.1 not, mainly because of their own quality is not.

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

1 easy to modify and maintain

2 to reality, to be practical, can not always want to skyrocketing rise.

7 Test/Release

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

7.1.1 has, is for the stable delivery of software and bang lookups.

7.2. Have you conducted a formal acceptance test?

7.2.1 not, is mainly the software engineering introduction of the big job.

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

7.3.1 have, mainly their own mobile phone/computer.

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

7.4.1 This is what the East ah .....

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

7.5.1 None

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

1. to develop a rigorous test plan

2. be flexible.

8 Summary:

8.1 Do you think the current state of the team belongs to which grade in Cmm/cmmi?

8.1.1 ... There are no signs of any specification.

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

8.2.1 running.

8.3 What do you think the team has improved in this milestone compared to the previous milestone?

8.3.1 everyone is working.

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

Passion

Afterwards Zhuge Liang meeting unfinished edition