Week 4 (cont. Sprint #1, Sprint Review
- Melissa Ng

- Nov 11, 2018
- 2 min read
For this week, we had continued working on the codes and focused on making it work. One challenge that we had faced while coding is that Unity is an entirely new platform to us, although we had studied C# programming before, the language platform is completely alien to us. Hence, we need to do some trials and error to find out how the codes work in unity and to be able to do this, we have to spend time looking through the codes and experimenting more with them. Therefore, I can say that our progress has been a little slow because we are still unfamiliar with the software. However, we have promised to work on it and have been going online coding websites for help, to better guide us in this aspect.
Other than this challenge that we are facing right now, we all definitely have our own personal commitment, and there are sometimes when I ask a question in the group chat but no one replies. This shows that we again need to improve on our communication aspect and work together more as a team.
Putting all the difficulties aside, I am actually still quite proud of the project because the basic function is somewhat already built up, all that we have to do is to create the UI, for good user experience. No user would feel comfortable using a phone app that takes 15 clicks to get to the page that they want to go to. Also there are a few minor problems like creating the scene, linking buttons and input to the code that needs to be tried out before being able to function properly.
Coming to the end of our very first Sprint for NAV X, we had to do a review of the past 2 weeks. We were asked to decribe the project progress in 1/2 words and my answer "Can Improve", because I really felt that we weren't reaching our full potential as a team yet. As a team, we are leaning more towards the worrying side of the project as the main concern is being able to complete everything that we aim to by the Hackathon judging.




Comments