0525 Scrum Project 7.0

First, Sprint summary

When it comes to the gains in a team, the first thing to do is to have a firsthand experience of the team's workflow and to be pro-Pro. The economics Department of the Hubei Economic College graduate survey, from the declaration materials, questionnaire design, interview outline, team building, bookmark production to the field interview, questionnaire filling, audio-visual data collection and processing, work, personal and team summary, investigation report writing, acceptance materials collation, publicity materials production and processing, Every step is poured into our efforts, each process is we have been repeatedly discussed after the consensus, each move is very difficult.

Second, teamwork should "make the most of the people, the most." Each person as a part of the team, have the obligation to express their ideas, opinions, there is an obligation for the interests of the team to give up some of their own things, have the obligation to contribute more to the team. A selfish and self-reliant person cannot live long in a team. We should have a say one, have one to do, in order to achieve the goal of the team to work together. This is the basis for a person to be able to survive in a team, which is the basis for a team to move forward together.

Then, team work to deal with the relationship between players and players. Since it is a team, it is necessary to ensure that team members work together to advance and retreat. The team is not just bringing together a few people with a common goal to do things, but will continue to play a role in the life of the team and beyond. Both at work and in life, it is necessary to ensure good communication between the players. Neither man nor thing should complain. Finding a way to solve the problem is what we should do, and complaining will only make things worse and make the gap between people more profound.

Thirdly, teamwork must be efficient. Make good work schedule and work strictly according to schedule. This is because the goal of the team to achieve the completion of the efficiency of the support, on the other hand because "bang, again and again, three and exhausted", to ensure the team's concerted efforts, we must abandon the work style of procrastination. There are relatively few problems with Jincu-type teams. For loose teams, such as the Graduate Survey team in economics, it is important to attach great importance to such issues. As a member, sometimes can not change the team's work style, oneself should arrange the time reasonably, do their own things, not because of the team's things and delay their own things.

Ii. statements

Korea Kirin Speech Summary: The interface is relatively concise and clear, and there are hot push and other interfaces, the next time the interface of the beautification can also do a little better, the content can be more rich, a little diversification,; In the project, everyone's style is not the same, so the things are made out with their own style characteristics, The final integration when the work is a bit nondescript, I hope the next time you can unify the style.

Wang Junjie Statement Summary: This successful completion of the task, everyone has completed their own task, it is worth continuing efforts, but the project is relatively simple, not particularly good because the major work of each section to prepare a reply, time is more tense. But we try our best to work with the team to achieve the desired results. But we hope that the next task will be better, and that we can do better in all aspects.

Summary: I think this project I do very well, you do not ask me why, in short, is very good, but still want to improve their task in the next sprint, to make the interface better look, to use the page more diversified, but also to do a back-end system, to achieve changes in database data, convenient administrator management site content.

Huang Statement Summary:

Three, productivity analysis

Our Burndown chart was not able to finish the task on time at the beginning, because at the beginning our courses were quite full, it was impossible to get the time to complete the task on time, which led to a drag-and-drop of the task, but then at the weekend, we were able to spare time on the project, So our Burndown chart began to show the trend of speeding up in the later stage, we will try our best to coordinate the time and finish the task on time. And in the latter part of the understanding of the project and the user needs more understanding. So it's more handy to do it, and the efficiency is several levels higher than the previous ones.

Iv. Review of conclusions

After that, you need to beautify the page to add interesting content.

Five, the Reading

The 8th chapter: the analysis of the project needs, how to do a good job requirements analysis, requirements analysis of the steps, let me understand to complete a project, needs analysis is very important, at the same time, software development can not meet the requirements of all stakeholders at once, but we must let these stakeholders at this stage have the opportunity to present their views and needs , and also to figure out "what they want from the software." The process of software development is the process of transmitting, transforming, implementing, distorting, or losing in a chain of relationships that "what the user needs most". How to determine "What users need most" we can rely on a number of proven methods, many of which can be used both in the software requirements collection phase, but also in the testing phase, the following is a frequently used user research methods: 1. Focus group, 2. In-depth interviews, 3. Card classification, 4. User survey, 5. User log Research, 6. Anthropological survey, 7. Eye tracking Research, 8. Rapid prototyping and 9.a/b testing.

The 9th chapter: the function of the project manager, the main introduction of Microsoft Program Manager, he is the product development and testing supplement, responsible for the long-term development of products and market promotion. For this purpose, the project manager must lead in a series of project planning, organization and control activities to achieve the project objectives.

10th Chapter: This chapter is about typical users and scenarios. According to my understanding, this chapter is to tell the program must be in the user's request to find their real needs, the program function can not be missing, but also do not have too much expansion, otherwise it is not conducive to software maintenance and security. Also said that the specifications of the output of our project development help, specifications can also be divided into software function manual and software technical specifications, only through the practice can write good specifications.

1) Function Manual

Define related concepts--specification good hypothesis--avoid misunderstanding, define some of the user/software interaction steps-----some good features and side effects---quality of service

(2) Function specification template

(3) Technical manual

(4) Function-driven design

Build the overall model, build a feature list, develop a development plan, feature design phase, to achieve specific functions

0525 Scrum Project 7.0