Skip to content

Iteration_1

jgarnierUQ edited this page Jul 13, 2018 · 12 revisions

Iteration Goals

In the first iteration, there were only a few basic features that were aimed to be implemented due to the struggle of adjusting to a new work environment and getting everything necessary for app development. A table of specific goals can be found below.

Goal Description
Design app layout Come up with mock sketches of what each page of the app should look like to have something to go off when actually coding each section
Basic UI functionality Code the basics for the UI to be able to have some functionality to demo
Server Look into possible options for the server
Database Look into better options for storing information rather than just a text file. Also look at methods of encryption

Team Roles

Name Role
Luis Team Leader/System Architect
Jonah Requirements Analyst/Technical documentation/User documentation
Aira Quality Control/Technical documentation/User documentation
Jonny User Interface/Technical documentation/User documentation
Wesley Programmer
Mannie Marketing Analyst/User documentation

Task Management

Issues

Issue Description
Setting up necessary software/equipment During the first few days, there was a lot of time spent trying to download and set up the Android Studio IDE as well as the correct emulators
Internet Connection The internet connection has been unreliable and is prone to randomly dropping out, and even just straight up not connecting
Version control There were a few issues regarding the version control we are implementing for this project. The biggest being lack of experience using version control which has led to some confusion
Android Studio crashing Jonny's laptop not being able to open Android Studio for long lengths of time before it eventually crashes
Low PC specs Luis' laptop not having enough RAM to be able to run the emulator without his computer crashing
No VPN Luis' laptop did not have a VPN installed so we were unable to consider using Firebase for our database

Total Estimation

Below is a breakdown of each goal and when it is expected to be completed by.

Goal Expected date of completion
Design app layout 03/07/2018
Basic UI functionality 11/07/2018
Server 13/07/2018
Database 13/07/2018

Screenshots

Meeting Summaries

Date Minutes
04/07/2018
  • Group discussion sorting out individual strengths and weaknesses
  • Sorted out team roles and basic tasks each member should get started on
05/07/2018
  • Updates on where everyone was at with their designated work from the day prior
  • Delegation of tasks that need to be completed before the demo on friday afternoon
09/07/2018
  • Discussion on what got completed in the last week
  • Discussion on what needs to be done between now and the proper presentation on Friday
  • Mannie to work on backgrounds/logo's
  • Luis, Jonah, Aira, Wesley to continue working on App
  • Jonny to continue on documentation
12/07/2018
  • Meeting the day before presentation
  • Finalising where everyone is at with their respective sections
  • Jonny to work on presentation layout and content
  • Others to look over and edit where necessary when completed

Retrospective

Friday 06/07/2018 1:30pm
After the first week of development, the entire team reflected on what got achieved and what could have been improved. It was clear that in the first few days progress was slow due to issues downloading the IDE's and emulators. This could have been better improved if these tasks were already completed back in Australia with faster and more reliable internet connections. Some members of the team were also unfamiliar with Java and app development as a whole. This could have been less of an issue with more preparation before the program in learning the basics of Java and getting used to the Android Studio IDE.

Thursday 12/07/2018 6:00pm
Looking back on all the progress since the last week, not everything was perfect and as how it was expected to be, but there has still been meaningful and significant progress. The basics of the UI were completed and are ready to demo however there is little implementation of a server and database due to more time being spent on UI than anticipated. This was the fault of a few issues the team encountered including laptops not being able to run Android Studio effectively, and also a few conflicts when trying to combine everyone's code through version control which slowed down productivity. The issue of combining code was eventually solved by debugging the merged code and fixing it to all work synchronously. From then on the team were very careful to learn from this experience and push and pull much more regularly to avoid similar conflicts in the future.

Process, Methods & Tools

Process Method Tools
Downloading IDE's/Emulators Regular process to download software
  • Internet Connection
  • Laptops
Design App Layout Use design software and communicate as a team to decide and create mock sketches of what the layout should look like
  • Internet Connection
  • Laptops
  • Design Software
  • Group meeting space
Basic UI Functionality Look at online tutorials and examples to get a better understanding of app development and apply that to the Drinking Buddies project
  • Internet Connection
  • Laptops
  • Android Studio
  • Emulators
Look into options for the server Online research
  • Internet Connection
  • Laptops
Look into options for the database Online research
  • Internet Connection
  • Laptops

Next Iteration Planning

Iteration 1 was more designing and implementing the user interface of the app, only sticking with core functionality due to time constraints. Iteration 2 would entail implementing the more advanced features of the app including the matching algorithms, implementing the server, a proper chat system as well as algorithms for suggesting drink options based off the users previous orders and what companies that are partnered are promoting.

Clone this wiki locally