Date: 2015-6-12
Location: Fundamentalist 601
Attendees: Sunny-code all Members
Vision and Objectives
What problems does our software solve? Is it clearly defined?
We are going to make a software that integrates the small butterfly function, the IP quick change function, the WiFi sharing function. The aim is to solve the problem of double-connection of small butterflies at night. There are also new students who do not modify IP issues.
The functional definition is clear.
How does the team solve the different opinions of their colleagues about the plan during the planning phase?
We ask questions together, then we collectively discuss the feasibility and finally vote for the solution.
If history does it again , What will we do to improve ?
Should always be consulted, collaborative progress, timely communication, to ensure that the final function does not appear to be difficult to fit into an interface situation.
Plan
Did you finish the work you planned to do in the end? If there's anything unfinished, why?
The original work was completed and the unfinished part was not available in some notebooks, which was not taken into account at the time of the original plan.
Did you find that you did something that didn't seem necessary or valuable afterwards?
A similar function of the program, their own hard to write, and finally found not to be transplanted to other notebooks.
are deliverables clearly defined and measured for each task?
The task was abbreviated in the Spring Sprint meeting, but it was simple enough for everyone to understand.
Is the entire process of the project in accordance with the plan?
Basically everyone fighting each other, progress is still some.
Is there a buffer left in the plan, and does the buffer function?
Yes, buffers are temporarily adjusted for the eventual synthesis of problems.
If history does it again , What will we do to improve ?
1. Find out more about the portability of programming languages across multiple platforms
2. To be good at using Baidu, it is not necessary to write all the things themselves. There are ready-to-use.
Resources
Do we have enough resources to do all the work?
Three notebooks are enough.
How is the time and other resources required for each task estimated and how accurate?
Everyone took their time and did not make a good estimate of the time. Accuracy is far from the.
Is the user testing time, manpower and software/hardware resources sufficient?
Finally, a two-day test was used to find the transplant problem. resources are sufficient.
Have you ever felt that what you do can be done by others (more efficient)?
No.
If history does it again , What will we do to improve ?
1. When estimating the time spent on a task, the member needs to be consulted
2. Time to leave the team to study
Change Management
Every relevant employee is informed of the change in time?
Changes in the course of our consultations, everyone can know the news in time.
What do we use to determine the "deferred" and "must do" functions?
The importance of the function, the more important the first realization.
Is there a clear definition of the export conditions of the project (exit criteria– What is "done")?
All pages are integrated and tested and "done"
Can a contingency plan be developed for possible changes?
No.
If history does it again , What will we do to improve ?
1. More communication, although always together, but really good discussion of the time is few.
Design/implementation
When and by whom is the design work done? Is it the right time for the right person?
The design worked in the first three days of the sprint. It was designed by everyone's brainstorming. Is.
Is there any ambiguity in the design work, and how does the team solve the problem?
No.
Does the team use unit test, test-driven development (TDD), UML, or other tools to help design and implement? Do these tools work?
The team tested it with VS2010, with its own test tools.
What features produce the most bugs and why?
Synthesis, there are a lot of bugs, can not be modified, and finally have to abandon the original plan. Another way to seek out.
How does code Review work, and do you strictly enforce code specifications?
Yes.
If history does it again , What will we do to improve ?
Do a good job of each function of the interface, left to use when the final synthesis.
Test/Release
Does the team have a test plan? Why not?
The team has a clear test plan.
Is there a formal acceptance test?
No..
Does the team have testing tools to help test?
Only test tools tested with VS2010.
If history does it again , What will we do to improve ?
1. Familiar with vs2010, breakpoint debugging and other functions.
Sunny-code Beta Summary Meeting