Sprint 2 Demo and Retrospective - paceuniversity/cs3892015team4 GitHub Wiki
##Demo Status of the software to be developed – summary
As of the end of Sprint 2, we managed to complete some of the graphics we will be using within the app as well as the app icon. We also were able to add music to the app to make the experience a lot more entertaining for our target audience. Another thing we were able to do was to make the app stay in the portrait orientation as we feel that that would be the best way that the app would play out. Finally, we were able to create a seekbar in the options menu of our app that controls the volume of the music in the app.
- Screenshots
- Video Demo
- APKs
##Retrospective
Sprint Goal
The goal of this sprint was to complete a lot of the background functions of our app such as the music and the volume controls. We were able to complete a lot of it and so we were pretty happy with that outcome. We were also able to come to a consensus on some of the visuals that we would implement in our app, though we do need to do more to have the finished product. Unfortunately, we were also hoping in completing some of the games that will be in our app and that was not completed. Tiarah was able to start on creating the first game, which would be in the subtraction category, however it was not completed to perfection.
Number of stories planned versus implemented
We planned to complete 5 User Stories and were able to complete 4 of them.
Planned versus actual velocity
Sprint retrospective written summary
-
What should the team start doing?
We should start putting more time in learning Github as we did start having some issues when it came to uploading and merging code. We did get a little more comfortable with Android Studio during this sprint, however there is always room for more to learn and so we shouldn’t stop learning about Android either.
-
What should the team stop doing? We should stop putting the games as the last thing to do for our app because it is essential that our app has games that work perfectly.
-
What should the team continue doing? (in terms of process, communications …) We should still come together more. We were able to code together for a couple of hours which really helped as it allowed us all to get on the same page.
Status of the evolution of the Product Backlog
- Through Sprint 2..
Burndown Chart
Click here
Statistics of GitHub
Click here