Week 3 (Sprint Planning, Sprint #1)

We started our very first sprint for NAV X, but first we had to come up with the board, indicating which features we wanted, were doing for the sprint, in progress and completed. In the very same week, we had to get started with our inception deck. Basically the board that we had to do wasn't so hard, all we had to put in was our Product backlog, Sprint Backlog, Features in Progress and completed features. We needed to think of user stories for different users, because all of them have different needs. Then after trying to think a little deeper and come up with tasks if the user story is too big to be done in a day. Mainly for our very first few sprints, we will be focusing on the Augmented reality of our application because we feel that it is the major factor that needs to be focused on for the upcoming Hackathon.

For now, our progress is quite slow because we need to improve on communication more within the team. Tasks has to be allocated properly and we have to also help each other if we have any problems. At the same time, another problem that we have faced is time management. If the feature needs time but not quality, we could maybe try to split it up into further tasks. Personally, I did the naming of the Map, so that we will be able to retrieve the map and display it when the user has selected a location and so that each specific Map has their own specific name. But I think we had overlooked that this was actually an epic, the first thing that we need to do was to create the scene, that alone took up 2 days because there was a problem connecting the scene buttons to the script. Moving on, we then had to figure out how to obtain the input from the textbox after the button has been pressed and save the input into a variable.