For every sprint (including sprint 1) a sprint summary progress report should be submitted.
Please make sure your E-mail contains everything it should, and your E-mail title is appropriate.
For the first sprint, as there is no actual implementation, therefore, the report do not need to contain
Were there any features you did not implement as planned, and why? Are you pushing some features to later sprints, and if so, why?
Tag a branch or revision in your repository to identify the code you want to submit for sprintN (replace N with 1, 2, ...). The date and time of this revision should be before the deadline. This branch should include a README file with instructions on how to run the application and tests.
And for the first two sprints, no testing is strictly required, therefore the report do not need to contain
What tests did you prepare for this sprint, and what are they covering? Did the tests you wrote deviate from your plan? What features are you not testing yet? Did you use any test frameworks?
You must include in your progress report a test coverage report. The coverage metric must be over 70%. If it's below 70%, you will lose 10% of the overall score of that sprint. This number may change each sprint. You must specify what tool did you use, and you must include one or more screenshots showing:
The overall coverage metric
The list of classes with lowest coverage. Explain why is the coverage low, and what (if anything) you plan to do about it
For every sprint (including sprint 1) a
sprint summary progress report
should be submitted. Please make sure your E-mail contains everything it should, and your E-mail title is appropriate.For the first sprint, as there is no actual implementation, therefore, the report do not need to contain
And for the first two sprints, no testing is strictly required, therefore the report do not need to contain
Check the link below for more detailed instruction. https://github.com/swsnu/swppfall2018/blob/master/project/sprint-instructions.md