Sprint summary

Good:

1.       Communication with PO is more frequent and get feedback faster.

2.       Task will be taken by other members if he has time to do it.

3.       More people know about specific skills instead of only one, so we have a backup in the team, such as the deployment task, we can finish the deployment soon.

4.       Sharing the work cross different teams

5.       Daily standup Meeting is more efficient.

6.       Communication between members is good, and get rapid feedback after function implementation done or technical issue answered.

7.       TFS status update daily (remain/complete fields updated)

8.       Knowledge Sharing between test and dev, this is not easy but necessary

9.       Use spoofy to reduce the rely on each part. At least the dev should discuss about this and make less rely on each other.

For example, two develope may have rely. So if they discuss (include test maybe good for the discussion), they can reduce rely on each other.

 10.    Have the test to review code if they have time.

 

Not Good:

1.       For the work cross different teams, should discuss methods of implementation and get a conclusion before development start

2.       User story acceptance should be defined at the start of a user story.

3.       Sharing more technical part in the confluence page such as the fiddle usage, deployment method, and the test case.

4.       We should have sometimes (maybe 10% allocation on each sprint to know something about next sprint so that we can raise some questions or do more prepare). Figure out the risk as soon as possible.

5.       Test data prepare, spec review and other test task could make as a task.

6.