Agile Software Development Practice-sprint Setup Meeting

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 difference with our customers (9 hours), so it is difficult for everyone to sit together and start plan like the standard sprint Setup meeting. In this model, we have 2 ways to implement it.

Implementation mode:

One way to do this is for our offshore team to send one person on a business trip each time, and then the person in the United States is responsible for the regular sprint Setup meeting with the American team, and then this person is responsible for documenting all of the meeting minutes, And then feedback the results to the Chinese side of the team, this is a typical "push" model, that is, onshore bar Setup meeting results to the offshore team, I had six months last year in the United States, when we run the model is this, the advantage is that I deal directly with customers, I can get the first-hand information about the needs and get a more precise understanding of what they really need, but the disadvantage is that as onsite coordinator, he is very tired, because he has to open 2 meetings, and once is to understand all, the second is to be the content of the "copy" To offshore team, so need coordinator itself has a certain level of technology, he can always grasp the essence of things, but also have good communication and understanding ability, but also have a good energy. (attached right 1 photo of my last business trip)

Another way to achieve this is to:

The day before we start each sprint, onshore will be able to story the sprint to complete the Jira, as shown in the following figure:

Then our team of each module will take the time to review one by one, and ask some troubling questions, and then the next day, we will only spend 1 hours with the onshore U.S. team to carry out this sprint Setup meeting, I usually host offshore this side of the conference And then we quickly review each story and then discuss our questions and onshore directly and figure out, if it can't be recorded and followed by a special email.

Summarize:

After this meeting, each member of the team should have a macro picture of the story we are going to do on this sprint. This is helpful for understanding the progress of the project team, macro-level assurance, and, in the future, to take over the task in case someone takes a leave of absence.

This article from the "Cohesion of parallel Lines" blog, please be sure to retain this source http://supercharles888.blog.51cto.com/609344/1261113