Teamwork sixth - hindsight

This work belongs courses 2019 autumn Charms software engineering practices Z class (Fuzhou University)
Where the job requires Teamwork sixth - hindsight
Team Name T-MAX
The target job Organize meetings and publish essays hindsight
Text of the job
Other references Project management of hindsight meeting

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 to solve the problem of financial planning is consumer records in daily life.
  • Defined quite clearly.
  • A clear description of the typical user and the typical scenario. According to preliminary survey questionnaire to user needs, identify target groups, so as to establish the document.

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

3, and on a stage compared to the quality of the software engineering team to improve it? In what has been improved, increase the number of specific, how to measure?

4, number of users, users in advance of the expected acceptance of what is consistent and important functions we? Our goal from the closer it?

  • Our software to solve the problem of financial planning is consumer records in daily life.

What are the lessons? If history all over again, what would we do to improve?

  • No major flaws in the implementation process, but if history all over again, we will document, frames, etc. written in more detail.

plan

1, if there is enough time to do the plan?

  • We pre-Alpha sprint to complete the planning and division of tasks.

2, the team at the planning stage is how to resolve the disagreement colleagues for planned?

  • Actively encourage everyone to speak, then we believe that elected members to discuss appropriate solutions.

3, the original plan if you work finally done? If you have not done, and why?

  • All tasks have been completed as originally planned.

4, you do not find some hindsight did not need or do not count for much?

  • To write their own algorithms.

5, whether each task are clearly defined and measurable deliverables?

  • Clear deliverables, to adjust during the preparation process.

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?

  • As the clear division of labor, reasonable schedule, the entire process is carried out according to plan.
  • No risk is not pre-estimated, only later discovered.

7, there is no buffer left in the plan, the buffer role it?

  • Have left part of the buffer, after all, in a short time as well as throughout the sprint course, there are some subjects you want to test, the buffer is indispensable.

8, future plans will do what changes? (Eg: buffer defined, overtime)

  • Everyone should be clear and specific time period buffer, do not wait outside the buffer zone still rest

What have we learned? If history all over again, what would we do to improve?

  • More reasonable to arrange a time, after all, it does not specifically developed, as well as in the development of sprint schoolwork. To discuss more details of the discussion to local, rather than general discussions, and discuss the results of detailed records, and will not forget.

Resources

1, we have enough resources to fulfill the tasks it?

  • Pre-spend a lot of time to provide a lot of convenience for later use on the installation configuration tool.
  • Although the HR team only five individuals, but a clear division of work they would not use too large.
  • Learning materials: a lot of information for reference on this page, also assistant teacher for your advice.

2, time and other resources required for each task is how to estimate how accuracy?

  • We first determine the corresponding task is extremely difficult to value, and then assigned to each person according to the type of task difficulty and task to finalize the completion time of each task is extremely resource.

3, the test of time, manpower and software / hardware resources are sufficient? For those without programming resources (graphic design / copy) whether underestimate the difficulty?

  • Manpower, adequate hardware and software resources, but time is more rush.
  • Edited copy is still very important, though without programming, but good planning, planning, design determines the direction of the work of late.

4. Have you ever felt that you can do to let others do the (more efficient)?

  • The ability of each player are different, and each person is good at. But because a person can not do things more efficiently, put everything to pay him to do. The ability to relatively poor people can be allocated points relatively simple task, of course, the higher capacity can assign relatively difficult task. So when the pre-assigned tasks should first understand each person's ability, redistribution quite a task.

What are the lessons? If history all over again, what would we do to improve?

  • Multi conduct exchanges and communication between the teams, task allocation clear and as equally, to avoid the task was too heavy, it was idle.

Change Management

1, each of the relevant employees are aware of the news in time to change?

  • Because every day meet, what questions will be thrown into the group discussions, the messaging efficiency is guaranteed.

2, we have adopted a way of determining what is "delayed" and "must be achieved" feature?

  • By meeting to discuss jointly discuss the decision.

3, exports Items (Exit Criteria) whether the clearly defined?

  • Performance, interface requirements and other requirements in the report module in a relatively clearly defined.

4, for a possible change whether contingency plans?

  • Basically no emergency situation thanks to the liver.

5, whether employees can work unexpected efficiently handle requests?

  • Work request did not come unexpected.

What have we learned? If history all over again, what would we do to improve?

  • There is no experience to change the situation.
  • If history all over again, we will develop a good change of contingency plans in advance.

Design / implementation

1, designed to operate at what time and by whom done? Is the right time, the right man?

  • Design work is in the Project Selection report when selected by the head of the whole group of people together to complete.
  • When the right time to the right people.

2, the design work have not encountered ambiguous situations, how the team is resolved?

  • Not encountered ambiguity, there will be a general discussion after the results together.

3, the team whether using 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?

  • Team used unit testing, UML and other tools to help achieve.
  • effective. Unit testing effectively help debug tested for each class, uml help us sort out the relationship between users, the needs, the system functional unit.
  • uml documentation yet there is no difference.
  • Unl no need to update the document.

4, Bug What is the function of generating the most, and why? After publishing discovered something important bug? Why did not we think of these cases in the design / development time?

  • Adding up to the billing function bug generated. Because this piece of code logic is more complex aspects need to be considered will be more.
  • After the release has not yet discovered bug.

5, code review (Code Review) is how to proceed, whether the strict implementation of the code specifications?

  • Code review code review by the reviewer format, style, named for compliance.
  • Strict implementation of the code specifications.

What have we learned? If history all over again, what would we do to improve?

  • We learned how to use testing tools aided design and practice.
  • If history all over again, we will be more automated tools for application testing and code review.

Test / release

1, if there is a team test plan? Why not?

  • Have.

2, whether formal acceptance testing?

  • It has not been a formal acceptance testing.

3, the team tested whether there are tools to help test?

  • Use Junit and UI Automator to help test.

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?

  • It has not been carried out performance testing software.

5, which I found unexpected problems during the release of?

  • Not yet released.

What have we learned? If history all over again, what would we do to improve?

  • We learned the importance of testing.
  • If history all over again, we'll spend some more time in learning the automated testing.

The role of team management, cooperation

1, how each team is to determine the role, is not the best use?

  • The role of the team is determined by the team members choose their favorite or familiar direction.
  • There Renjinqicai.

2, there is help each other what among team members?

  • Have.

3, when the issue of project management, cooperation appears, team members how to solve the problem?

  • This problem has not yet appeared. If there will be timely feedback, collectively cooperation debug it.

    Each member represents a clear publicly thank the members of the help (and write in their blog in):

    Xu Yu Yang: I thank Tintin helping me, because she is our tomorrow.
    Xu Bin: I thank Yu Yang helping me, because team leader to help us find learning materials.
    Yu Wen Qian: I thank Tintin helped me, because I actually do not know a lot of interface, Tintin help me modify a lot of controls and interface, without her we would not tomorrow.
    Yang Xinyi: I thank Xu Yu Yang helped me, because he taught me to use leancloud manage cloud data, background processing request.
    Wenyi Qian: I thank Yu Yang to help me, because leader to attend a lecture on dinner (1˃̵ᴗ˂̵) و!

What have we learned? If history all over again, what would we do to improve?

  • We learned the importance of teamwork atmosphere for development.
  • If history all over again, we will continue to maintain a good atmosphere in the team at this stage.

to sum up

Do you think the current state of the team belongs grade CMM / CMMI in?

  • I think the team can repeat the current state of the input level (Repeatable) grade.

Do you think the team is currently in its infancy / running / specification / create a stage which stage?

  • I think the team is currently in the running stage.

What do you think most need to improve aspects is?

  • I think the best aspect is the need to improve coordination problem of synchronization between the front and rear ends.

photo

Each crew for the final results of the project's contribution

Guess you like

Origin www.cnblogs.com/T-MAX-WK/p/12026555.html