We switched pair this morning and he quited, leaving me fighting there. Fortunately, Julie switched in offering some help, and finally I could discuss the solution, with whom we can understand the thoughts from each other. When we came back from lunch, unfortunately, we were involved into the requirement "researching" again with BA. It's so disappointed that we have not finished this story, yet.
Besides the experiences, I found out the difference of the stand-up meeting between the team in China and in TWU. As far as I concerned, what we say in stand-up should contain these aspects of information:
- What I did yesterday. To notify the team your efforts can help teammates get an conception about the project progress.
- What I plan to do today. This can force people to always start working with a plan, and also help other people synchronize their plan.
- What I found very important and has to let the team know. It's like, had introduced an interface when refactoring, or had gotten new ideas for some strategies. Sometimes we spread knowledge with this chance.
- What I got blocked in my working. To tell your pain or problems in the working to the team, as a kind of feedback, will help the team solve the problems ASAP and improved.
However, the trainers told me not to say so much. More directly, Kai told me that DO tell just the important information for the team, without any experience or detail, like "We need help on spring MVC." Incredible, right? I think so. But when we considered we have over 20 people in the team, it makes sense. Supposing one minute for each person, we need 20 minutes, which would be "the longest twenty minutes in my life" from Jonathan.
Oh,by the way, we don't have a toy or anything as the token for speaking in TWU.
I am investing an effort to make a comparison among Git, Svn and Hg. It has not finished yet.