scrum explained

Because of some of the problems with TFS, it has not been able to see the burndown and burn rate for Sprint 3.Today's scrum finds that there are a lot of things going on in the group during the sprint, but there is a lot of effort to finish ASC Master's task at night and on weekends, hard ~ Member Today ' s work Tomorrow ' s work Feng Nie UI redesign of the index UI redesign of the index Li

(written in 10.22 weeks four)Now the situation of personnel:Kang Jiahua leave to next Monday, Liu Yanxi to Friday 18:00, Zhang Qidong to Saturday noon.Others are working properly.And then there is the current progress situation:has completed the server database setup, as well as the basic registration login function. The background has been followed up with the UI.The next step might be to make the UI even faster, ensuring that a UI has been designed in the background when the previous UI design

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 1 time: 12.09-12.18Serious Case Group member Name School Number Blog links Git

First, the role of the introductionProduct owner (also PM): Wang Dongbo Scrum Master: Yanya Development team: Shi Li HaisuSecond, Product backlog1, user login, login can see their card information2, Query the bibliography, can inquire the book informationIii. Standing meetingsDate: May 7, 2015Location: Learning twos BuildingAttendees: Yanya Shi Wang Dongbo Li HaisuIv. Summary of the meetingOur project involves a database of linked libraries that are b

Scrum 3.3 Multi-fish ordering system Development Progress (Order Details page design)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 links

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.