| title | link |
|---|---|
| This work belongs courses | https://edu.cnblogs.com/campus/fzu/2019FZUSEZ |
| Where the job requires | https://edu.cnblogs.com/campus/fzu/2019FZUSEZ/homework/10151 |
| Team Name | <Peer Group> |
| The target job | <Summed up the inadequacies of the process sprint> |
| Text of the job | https://www.cnblogs.com/tong-xing/p/12046697.html |
Vision and goals
1. Our software to solve the problem? Whether clearly defined? Is there a clear description of the typical user and a typical scenario?
Our software solution is confession Universities wall inconvenient to use, provide a more convenient platform for freer, more than a few launch event notification feature
clearly defined
typical user is a college student, a typical scene then the original needs analysis which has been given, It is inside universities
2. We reached the goal yet (function originally planned to do a few? As originally planned delivery time delivered what? Originally planned to reach the number of users reached it?)
Target distance short of many, many
features of the original plan did not materialize, only one interface
3. On a stage and compared the quality of the software engineering team to improve it? In what has been improved, increase the number of specific, how to measure?
no
4. The amount of users, users in advance of the expected agreement on acceptance of it and we have important functions? Our goal from the closer it?
no
5. What are the lessons? If history all over again, what would we do to improve?
More exchanges, exchanges are not in the group, the more meetings called out, spend more time.
plan
1. Is there enough time to do the plan?
Before the plan, then sprint again on the set plan. But then the result is not very satisfactory
2. Team at the planning stage is how to resolve the disagreement colleagues for planned?
I did not encounter a lot of differences, to discuss our choice consensus.
3. You work planned if finally done? If you have not done, and why?
No. At first spent a few days in learning, they did not do anything, a little impatient, and lack between team members, and slowly the enthusiasm is gone.
4. find that you do not have some hindsight did not need or do not count for much?
No
5. Is each task are clearly defined and measurable deliverables?
Not very clearly defined, resulting in the end we do not know what to make of things.
6. The whole process if the project were carried out according to plan, the project what had happened? What are the risks was not estimated, why not estimated?
The first is the software installed, do not know so much trouble, has not yet begun to write code, there are many software bug, as well as learning a bit confused above, read will not use. The reason should be the first contact, really do not understand anything.
7. There is no buffer left in the plan, the buffer role it?
No.
8. Future plans will do what changes? (Eg: buffer defined, overtime)
Plans to refine it, must have a certain daily output.
9. What have we learned? If history all over again, what would we do to improve?
The rear end of the front feeling a little out of touch points, we should all try to front and rear ends are connected together, and then divided by function modules, such as a person writing a corresponding interface as well as its back-end operations.
Resources
1. We have enough resources to fulfill the tasks it?
Great resources online tutorials, teaching assistants also gave a lot of resources, but learned not use.
2. The time and other resources required for each task is how to estimate how accuracy?
Not very accurate estimates are coming in by the day
3. Test of time, manpower and software / hardware resources are sufficient? For those without programming resources (graphic design / copy) whether underestimate the difficulty?
no
4. Have you ever felt that you can do to let others do the (more efficient)?
I am not fit to be a leader, not like other people to arrange, has been urging others.
5. What are the lessons? If history all over again, what would we do to improve?
Do not be impatient, try to learn a little write a little, do not think the whole school can be directly developed
Change Management
1. Each relevant employees in a timely manner that the message changed?
Not very clear, full reply issued a notice no.
2. What measures we have adopted a decision "to postpone" and "must be achieved" feature?
Discussion
3. The conditions of export project (Exit Criteria - what "done") have a clear definition of it?
That function can be used
4. For possible change whether contingency plans?
No
5. Are employees able to effectively deal with unexpected work request?
No unexpected work request
6. What have we learned? If history all over again, what would we do to improve?
The process will certainly be unanticipated difficulties, to have this consciousness. Improved word is not to give up difficulties
Design / implementation
1. Design work at what time and by whom done? Is the right time, the right man?
Prototype design leader everywhere complete, is to do that in the needs analysis. Is the right time to the right people.
2. Design work has not encountered ambiguous situations, how the team is resolved?
No, before discussing the design function before going to design.
3. Does the team use unit testing (unit test), test-driven development (TDD), UML, or other tools to help design and implement? These tools work? UML Documentation beginning of the project and compare the current state What is the difference? How do these differences arise? Do you want to update UML documents?
no
4. What is the most versatile Bug produced, and why? After publishing discovered something important bug? Why did not we think of these cases in the design / development time?
No function
5. Code review (Code Review) is how to proceed, whether the strict implementation of the code specifications?
There is no strict code standards
6. What have we learned? If history all over again, what would we do to improve?
step by step
Test / release
1. Does the team have a test plan? Why not?
No, a limited number of plans for his first test your modules, and then finally do the test again together
2. whether formal acceptance testing?
No
3. Does the team have the test tools to help test?
No
4. The team is how to measure and track the effectiveness of the software? From the results of the actual operation of the software, these tests work useful? What improvements should have?
No
5. What unexpected problems found in the process released?
No
6. What have we learned? If you do it all again, what would we do to improve?
Learn to use testing tools, if the number of people dedicated to a person to test
The role of team management, cooperation
1. how each team is to determine the role, is not the best use?
The number of press division, then we all pick. I think since it is their own pick should all be good
What have mutual help between 2 team members?
Have
3. When project management, when issues of cooperation, team members how to solve the problem?
Did you have any cooperation issues
Each member represents a clear publicly thank the members of the help (and write in their blog in):
Everywhere: thank Po Lin Zheng students, or understand a bit more, can put forward good ideas
Pu Zheng Lin: Thanks for the efforts and dedication of all the students
Leach: Thank lined Leader! Leader led the way many things are done a lot for this group, it is tough! Really very grateful, but also on their own do not work hard sorry.
to sum up
Do you think the current state of the team belongs grade CMM / CMMI in?
carried out
Do you think the team is currently in its infancy / running / specification / create a stage which stage?
Run-in
Do you think this team compared to the previous milestone a milestone any improvement?
No
What do you think most need to improve aspects is?
attitude
As we mentioned earlier, the quality of software engineering software quality + quality = program, and that the team in the next phase of how to improve the quality of software engineering it?
Code standards, timely test some small features
The proportion of project results
| Full name | contribution |
|---|---|
| Bristly | 16% |
| Po Lin Zheng | 20% |
| Li Cheng | 16% |
| Leach | 16% |
| Zhang Lei | 16% |
| Yuan Jiahong | 16% |