Page History

• The sprint length of 3 weeks was excellent.
• The Quality Assurance that was applied for this sprint was good:
  • Extra measures such as Resharper Code Formatting (for uniform coding standards), SonarQube (acting as an intermediate SIG analysis tool to perform static code analysis for increasing the quality of the code) were put in place
  • The preparation of a demo file which could be used during the development of features of 1.8.4 was found to be helpful
  • A dedicated tester and the testing dynamic was good (David delivering resources when required, the willingness of Ali to test)
  • Tester notes were added to issues to give an indication to the tester what to test
• Despite the situation (forced remote working at home), the team work and communication between the team members was good
• The results of the sprint were satisfactory: minimum was delivered.

The main point of discussion during the retrospective was that:

Issues are unclear for the testers and developers and cause miscommunication.

In order to improve this:

Action points:

• The issues need to be more elaborated in detail about what is needed, how it is supposed to work. As a help for the P/O, Ali Hadi and Dennis Tang will send their respective issue templates that are used in their projects.
• Acceptance criteria and work instructions to test the finished functionality of an issue should be added. In case of bugs, reproduction steps should be added
• In case things are still unclear, it is the task of the developers and the testers to identify this situation and talk with the P/O to reach the same understanding of what is needed.
• The sprint preparation needs to be more elaborated. The SCRUM MASTER should take an active lead to filter or flag issues when their description is unclear.