sprint merging with

part of the sixth assignment according to the progress of the project Learn the UML Diagram and the building method to learn about the tools required for blogging and design. problems encountered: a database field with a length exceeding the limit error causes an insert exception, and some hidden bugs require multiple tests to discover. When you join a group, the request fails, and there is no error returning information that needs to be parsed from the logical layer of the code.

Complete and publish Summary blog, sixth chapter of building Law, learning UML diagram Wu Jingan Unit testing of completed functions Improve the test results of completed functions, design test cases for the function of the next step plan implementation of the meeting Hu Zhiquan Complete part of the sixth assignment according to the progress of the project Learn UML diagrams, Learn the tools your blog and design requires. problems

In the agile development framework of scrum, the most important part is the Sprint plan meeting. If the meeting fails, the whole sprint will make the scrum team suffer and it is difficult to complete the initial sprint goal. After several attempts, we finally found our own model. These methods and principles are the best for us. Based on our own knowledge and our

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future. This article mainly aims to check your understanding and usage of the scrum Sprint plan meeting, Through this article, you can check1. process and steps of your scrum Sprint plan MEETING2. output results of the MeetingSprint

intended to be used by customers, acting as a consumer, feedback product information4.master: Liang, ensure the team is scheduled to complete the mission semesterSemester Sprint Time:November 4-December 18First Sprint goals and assignments:1. Register login screen claim: Wang Dahua2. Interface Jump CLAIM: Liang3. Ordering interface Claim: Feng Zifan4. Payment interface Claim: Jongjie5. Management interface

Note: The Development Management Checklists-series of articles are transplanted from my iteye blog. The Development Management checklists column will be updated directly in the future. This article mainly aims to check your understanding and usage of scrum Sprint plan meeting 2, Through this article, you can check1. process and steps of your scrum Sprint plan meeting 22. Results of scrum

1. Scrum plan MEETING Before each sprint starts, you need to hold a Sprint plan meeting. The meeting time is generally 4 ~ 8 hours, participants include product owners, scrum masters, scrum teams, and others of interest, such as managers and customer representatives.The product owner selects high-priority tasks from the product backlog and works with the scrum team to determine how many features are requi

team blog team GitHub Second sprint questions and suggestions hgf520 Regionalcrimeunit xjy-gg goidenbubble No jobs submitted for the second sprint liezhihua LWHTF No project progress control, blog/github follow up not in time caicaihong RaiCai

The Sprint Review Conference has long been an important part of scrum, a mechanism for the team to get feedback on the product increments that are delivered by the iteration. At the Sprint review meeting, the product owner determines the priority of the next sprint's requirements based on the feedback received.So, is the sprint review now obsolete?Ten years ago,

For more than a year, we've been using Ibm®rational team concert™ to support our Scrum teams, enjoy its features, coexist with its shortcomings, and develop its next version. Using the IBM Rational Team concert V2,jazz and the Rational Group concert teams can make significant improvements to Scrum and agile assessment, planning support delivery (not to mention more improved WEB clients and many other new features). Sprint Planning As we have used IB

In my previous introduction, I described the relationship between release, sprint, and story. Reference: several meetings in scrum management and our practices To put it simply, a release can include several sprints, and a sprint contains several story. Of course, a story can span multiple sprints or release. But what about the version? In practice, we need to use the GIT tag pairCodeTo ensure that all th

In the past few monthsSprint plan MEETINGIt will take several minutes to name the current sprint. It is very interesting to review it.--- Agile genie Let's take a look at the sprint name from project: Sprint1 --- "the big con" Sprint2 --- "Breakout" Sprint3 --- "hours to doom day" Sprint4 --- "the big end" Sprint5 --- "The Dragon Warrior" Those who are familiar with Garrison's death squad will be ve

Introduced: For story, an important measure of its size is story point, which is not equivalent to the function point in the software workload assessment, because story is simply a rough relative estimate of the size of the story, and function Point is used to measure the exact size of a functional module and to participate in the calculation of the formula, which is clarified here. The estimation of story point is a very deep learning, and we cannot be careless, because if we estimate less, i

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

Introduced: One of the first and most important activities for an iterative cycle sprint is the sprint Setup meeting. At this meeting, we will mainly explore some of the story that we need to accomplish in this sprint, and what the specific requirements of these story are. In fact, our company is taking the offshore development model, in which we have a time dif

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14 Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim Sprint Cyc

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim

1. Start a new sprint:Starting and ending: 2016.6.1~2016.6.14Follow the procedure below Product Backlog: Continue down refinement Sprint Planning meeting: Determine the goals to be completed for this sprint Sprint Backlog: What to do with a new sprint Mission claim