scrum explained

The following content is discussed in scrum today: Design document alpha version review, corrected the design of the Character ModelThe previous design of the character model is as follows: the user inputs an image,ProgramExtract information such as the beginning, trunk, and limbs, and map them to the predefined character model. Because we have never done similar work before, and this solution looks quite simple. However, after Chen Zihe discussed

Agile development has always been our company's development model. We are trying scrum recently. Although he has been present for some time and has made a good comments, there is not much information in this regard in China. For more information, see the official scrum website http://www.controlchaos.com/about /. There are good explanations. There is a good blog written, http://hi.baidu.com/zeorliu/blog/ite

Notes of daily scrum MEETING Tuesday, November 4, 2014- Team members Today's team task Quota for the current day Completion status Chen shaojie Read and understand the underlying connection to the database in the code 2 h 3 H Wang Di Read and understand the underlying connection to the database in the code 2 h 2 h Jin Xin Read the data processing in the Code and create the course direct

Label: style SP data 2014 code BS ad ef Notes of daily scrum MEETING Monday, November 3, 2014- Team members Today's team task Quota for the current day Completion status Chen shaojie Read and understand the underlying connection to the database in the code 2 h 2 h Wang Di Read and understand the underlying connection to the database in the code 2 h 2 h Jin Xin

Today, four people in the group have left Beijing. It's a good weekend. Otherwise, the work in our group will not be finished. Zishun is very dedicated. A train with more than nine o'clock leaves at half past seven. before leaving, it closed a task. It was really a dry exercise.ProgramClerk. Yupeng left early in the morning, so no task is done today. Yingwei and Li Zhang only walked in the afternoon. Before they left, they basically performed more than half of yesterday's tasks. Today, t

ScrumGlossary Directory: • Burn down charts)• Daily meeting (daily scrum meeting)• Impediments)• Product backlog)• Product backlog item)• Product backlog item effort)• Product burn down chart)• Product owner role)• Release)• Release burn down chart)• Scrum roles)• Scrummaster role (scrummaster role)• Sprint• Sprint backlog• Sprint burn down chart)• Sprint goal (sprint goals)• Sprint planning meeting)• S

Tags: Android style blog http sp data 2014 Log Code Notes of daily scrum meeting (11.6 11.7) Because Friday 7 is the first day of the holiday, several players either go out to play or go home, so we have not started coding since the discussion, The remaining players continue to learn about Android development, so there is no progress in the burned-out figure 7. Our team did not assign tasks on Saturday and Sunday, Let's move the task that was

Label: style SP data on code BS ad working time Today, we held the first scrum meeting, summarized the work achievements and lessons learned in the recent period, and assigned each member the next step. Web Crawler is a difficult problem for us, because we have less contact with each other before, so we need to start from scratch. We have referred to a large number of similar projects, learned a lot of practical knowledge, and had a preliminary simp

Scrum meeting Meeting notes I. Key points of the meeting: 1. Determine the member role; 2. discuss questions about the project; 3. Create a member task within one week. II. Specific meeting content: 1. Member roles: PM: Yang Yi Dev: Xu Xiaohong, Liu Haoran, Zhang yihuang, Xu fangyu, Zhong yiheng 2. project requirements: As a mobile client with similar functions as the online teaching Q A system, the specific features have been given requirements: use

4. team collaboration When talking about team collaboration, the most common thing we hear is the team responsibility system. In a small team, it is easy to form an external team Responsibility System (because of the collective sense of honor), which is also one of the reasons why scrum encourages small teams. However, in a team, it is not easy for everyone to implement team responsibility. It seems easy to find the counterexamples. In a project with

front desk personnel function, user's order checkout function, etc. Use CSS for menu design and SQL for data collection 6 Data statistics 8 5 Data traffic Analysis, menu order number statistics Using algorithms to calculate which dishes are popular 7 Message boards 12 9 Click to enter the message to publish their own restaurant, and food advice can also be timely view DW, SQL interface design and data storage

For an organization, it is common for developers of the same group to complete multiple projects. In this situation, how should we organize a team? How should they plan and allocate their work? See http://www.21manager.com/html/2008/10-22/12562185.html for more information 　　If many resources can be allocated (for example, six to ten developers can be assigned to each project), and the size and relative priority of these projects are known, generally, divide developers into two or more teams.　　

Higher: scrum (III) 4.Too much external interference Many companies face a problem. While developing new products, they also need to cope with maintenance tasks for old products. In addition, events from the market, customer service, human resources, and other departments are constantly interrupted and focused on R DScrumTeam. For example, the marketing department requires technical staff to participate in the exhibition to provide technical b

Labels: style blog HTTP color SP strong data on 2014 In this meeting, we determined the specific assignment of tasks. In this part, each person has a programming task of about 20 hours, and the entire project has a total of about 140 hours. Tomorrow is the first day of the formal start of software implementation. The following lists the tasks of each person in the previous two days: Day 1 Day 2 Ding Xin Restaurant list JSON/XML Data Analysis Re

Stand-up meetings are the members of each other who stand up to each other and say their progress, not meetings, not writing reports. is for better communication and coordination, essentially for engineering team communication. The requirements for the scrum stand-up meeting are as follows:1. Members are equal, and statements do not differ between managers and programmers, and everyone needs to keep their statements within 15 minutes.2. The content of

Encounter difficulties Liquan Data deletion in the database Communication between two people Multi-person communication Yu Yu Learn Background Database transfer Passing registration information to the background No Liu Fangfang Two-dimensional code generation learning Two-dimensional code generation learning No Han Yuanyuan Learn GPs to get a map Learn GPs to get a map No

Group Name: nice!Group leader: LiquanMembers: Yu Yu Liu Fangfang Han Yuanyuan Hong LijunProject content: About Run app (about bar)The requirements for the beta phase are updated as follows:1. Verify that the user name is in the database at logon2. Each user has their own personal information home page3. Plan to complete the database additions and deletions4. Send and receive messages between friends5. Search for a running partner (depending on the time and location of your run, your personal inf

Scrum 3.2 Multi-fish ordering system Development Progress (page Optimization Order Details page)1. Team Name: Crime Squad2. Team goal: Long-term management, accumulate customers fully prepared, waiting for the line3. Team slogan: unswervingly, the pursuit of perfection 4. Team selection: Restaurant to shop ordering system Web5.Sprint 3 time: 12.09-12.18Serious Case Group member Name School Number Blog links GitHub

Scrum 3.1 Fish ordering system development Progress (phase III project concept and mission planning)1. Team Name: Crime Squad2. Team goal: Long-term management, accumulate customers fully prepared, waiting for the line3. Team slogan: unswervingly, the pursuit of perfection 4. Team selection: Restaurant to shop ordering system Web5.Sprint 3 time: 12.09-12.18Serious Case Group member Name School Number Blog links Git

Introduction: I will track and record a series of articles that I am currently working on using a complete scrum management project. There will be some lessons to learn and encourage readers to learn from each other. Hai Han is still recommended for some incorrect or poorly written information. Of course, I hope you can provide more valuable comments. The support of readers is my greatest motivation. (One, two, three, four, five, six) ================