因为团队重组了一下，我所在组的组员和工作内容都发生了一些变化，所以这次在月末，我们拿起来很久没有开的Retrospective Meeting,整体效果来看还是不错的，发现了不少的问题，大家的积极性比我想象的高，看样子是公司推动Scrum有一定的成效啊。
下面是一些照片，公司用的是玻璃墙，我也没用白板，而且~~~~~~~~~~~~手机拍照。。。。。。。。。
左边是Timeline右边是Leaning
好看点的TimeLine
在上图中我很NB的写了一个SMART，结果我也不是很清楚为什么要将Action做成SMART的，因为当是时我的确忘记了SMART每个字母的具体含义。
详细的Learning,上面部分是满意部分，横线以下是不满意部分。
最后总结的 Impediments 和Actions
以下是总结
Impediments and Actions
** Our Competence Is Not Good Enough.
1. Reserve some time in each sprint for competence developing.
2. Pair working
3. Reduce interruption in the daily work.
4. Facilitate Stand Meeting, push him to updating Wiki pages when somebody reported a issue or sharing something.
5. Using Wiki pages to sharing knowledge.
6. Add a FAQ document into SVN, anybody can update it.
** DOD For Tasks/Backlog-Items Is Not Clearly
1. Involve APO into Sprint Grooming/Planning meeting.
2. Voting carefully and seriously.
** The Amount And Quality Of Test Cases
1. Store all test cases description into QC carefully.
2. Using UML to describe requirements/design/architecture.
3. Clarify test case standard (how to write a "good" test case)
4. Test case review.
5. Reserve time for legacy test cases' upgrading/refacting/regression-testing.
6. Store the result of test cases into SVN