scrum for dummies

The agile development of scrum is relatively strict with the process control. Each stage has a complete set of processes and strict time control. The main development process of our project team is as follows: The picture is taken from the book scrum-Checklists-Chinese. I modified the content in Chinese. Next I will split the entire process one by one, Full meeting: mobilize the development team

New Year's Day holiday has passed, so fast! I have done a lot of work to listen to everyone's sync progress during scrum today. It seems that everyone is not busy on holidays. Now, the real-person boxing game has taken shape. The new part of Collision Detection and user input can be easily played. The following is: The evil Dev only adds an attack action to the mm on the screen, and I can only hide from the left and right ...... We are looking fo

The team recently changed a lot of fresh blood, so they held a scrum training on the day before the National Day. I personally think there is a poor job in the PPT,It would be hard to understand, but it would also be false to export scrum, which is only suitable for products and not for project conclusions. While writing this article, I read the latest information on the Internet and found that there is

What is a standing meeting? Standalone meeting is one of the technologies related to Scrum in Agile Software Development methodology. It can also be called the best practice of Scrum. The specific form is the same time every day. All members of an agile development team stand together face to face for a period of 15 ~ A 20-minute short meeting. At the meeting, everyone should answer the following three que

XP @ Scrum enjoys this classic description. The new team is transforming agile development. I also read some documents. XP @ Scrum is my goal. We hope we can help each other with experience and transformation. Let's talk about recent problems. 1. I understand the requirements, but I find that there is a problem when the requirements are passed down. 2. The number of bugs seems to need to be controlled.

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

Today, I received the extremeprogramming API@ Yahoogroups.com): "The benefits of automated building and continuous integration are required so that their VP can take a while to optimize their build scripts, in order to shorten the time from 3 to 4 days to 12 hours. Because their unit tests run for too long and building often fails due to unit test failures ." This is not ridiculous, because it is common in many companies, but when it happens to a software company that claims to be "agile" and bu

Robert Sabourin shared his test practices in the scrum team in the out of the frying-real-world stories of scrum migration-and no one got badly burned article. Traditional tests are probably divided into two types of positioning: (1) "goalkeeper": Quality champion, blocking the release of unreliable, ineffective, and bug-filled versions. (2) "information provider": provides a large number of positive inform

What is a standing meeting?Standing meetings are one of the techniques involved in scrum for Agile software development methodologies and are also known as best practices for scrum. The exact form is the same time every day, and all members of an Agile development team stand together face to head and have a short meeting for a duration of 15-20 minutes. At the meeting, everyone should answer the following t

One of the most important systems in scrum of agile processes daily standing meetingWhat to know:Question: Why not use the email report instead of the daily meeting?e-Mail can not replace the daily meeting, e-mail will only increase the cost of communication, and can not provide details or give others the opportunity to ask questions, nor can help other members to solve the problem.Purpose of the Standing meeting:1. Let everyone know what other people

This article was 2:51:42 2016/12/8 Republish to Buaa_overwatchBeta Phase Second Scrum meetingSituation Brief Beta Phase Second Scrum meeting Agile development Start Time 2016/12/7 24:00 Agile Development End Time 2016/12/10 00:00 Summary of basic content of the meeting Determine the basic tasks for the next we