Sprint2 Review and Retrospective

Sprint2 did fail, many tasks were not completed, and product owner was not satisfied with the demo. After deep reflection, we have found a lot of problems:

Normal 0 false false en-US zh-cn x-none MicrosoftInternetExplorer4

· Scrum Master did not communicate with team members and Product owner to identify problems and resolve them in a timely manner when discovering signs of failure in Burn chart;

· The workload of the story selected in planning meeting is greater than the actual time that the team member can work;

· In planning meeting, the developer did not determine the demo with Product owner, so that the demo was asked "whether it can be done this way" and has been discussing technical details. Especially for the visual display of the server-side development, but also in advance to determine the demo mode;

· The collaboration between client and server is involved in this sprint, but the two are not communicating in time, and the task priority is not set. It is recommended to put the most difficult and need multiple assistance to the previous completion;

· Part of the server side of the sprint needs to interact with the R platform, but the developer is not aware of the R status and has not invited platform-related developers to participate in the planning meeting, resulting in a work-estimation error;

· For the above article, if other relevant personnel can not attend the meeting, or the explanation is not clear enough, need to estimate the communication cost of the development process within the task volume;

· Product backlog is not detailed enough, now only a simple word, in the demo will appear inconsistent understanding. Requires Product owner to describe the detailed requirements of each Story, and developers can also require that the demo and some of the details of the discussion to be recorded on the Story card, not taken for granted;

· When estimating the amount of task, the developer does not take into account the impact of the task volume on the task of other projects;

· communication! communication!! Communication!!!

Finding a problem is a positive improvement and hopefully there will be a substantial breakthrough in the next sprint.