Iteration 1

1. Iteration Goals

Iteration 1 will see the development of a functional website that implements the three core functions of the Travolla service: the Optimised Journey Planner (OJP), the Activity Heat Map (AH), and the Local Tour Guide matching system (LTG). In this initial phase, the content of the site will be centred around two cities: Dalian, China, and Brisbane, Australia. The goals for this iteration are at a minimum:

Goal	Description
Create a Functioning Website	Develop a website that acts as the vehicle for end-users to access the Travolla service
Create the User Interface	Design a unique, simple and easy to use interface such that it is accessible to all target consumers
Create the Backend Database	Design an efficient database to store information on users (username, password, basic customer details, billing information, personal preferences), and destinations (location, rough approximation of opening hours, type of activity)
Develop the Logical Backend for the OJP	Create a basic algorithm for sorting selected activities into an efficient timetable, taking into account factors such as distance, rough opening hours, and user preferences
Develop the Logical Backend for the AH	Create a dynamic activity heat map to display crowd sizes at various activities across Dalian, China and Brisbane, Australia
Develop the Logical Backend for the LTG System	Create a system that allows travellers and local tour guides to be matched based on location, time availability and personal preferences
Create Review System	Design a review system that allows travellers and local tour guides to review each other
Create Logos for Company and Travolla Product	Design a company logo and a logo for the Travolla product to be used on the website and in supporting documentation
Create Supporting Documentation	Supporting documentation for this project includes: a Software Requirements Specification (SRS), a Software Design Specification (SDS), and Iteration Specifications
Define a Business Plan	A carefully devised business plan will be created to ensure the company runs smoothly now and into the future

2. Team Roles

Name	Role	Description
Ada Rao	Programmer - Database/Backend, LTG Matching System, Content Provider	Development of the database used to store the information on the website, including user details and destination details. Develop logic for LTG system. Provide content for the activity suggestions.
Edward Sweeney	Programmer - Database/Backend, LTG Matching System, Quality Process Engineer	Development of the database used to store the information on the website, including user details and destination details. Develop logic for LTG system. Keep track of all tasks and ensure a high standard of completion.
Erik Brand	Technical/User Documentation, UI/UX Assistant	Generate documentation for both developers and users of the system. Assist with the development of the frontend.
Henry Burgess	System Architect, Programmer - OJP Logic	Oversee the overall structure of the project to ensure that the various components work together in the final product. Develop the logic behind the OJP.
Jason Zhang	Programmer - Heat map Logic, Content Provider	Develop the logic behind the heat map. Provide content for the restaurant suggestions.
Léa Laï Van	Project Manager, UI/UX Designer	Manages the project by enforcing the project schedule. Design and development of the frontend UI/UX.

3. Task Management

3.1. Issues

Date	Issue
5/07/18	At this stage of the development, there have been no major technical or organisational issues. The only notable environmental issue is the inability to access the internet in a stable way. This has hindered development as it meant that downloading the required software and conducting research has been slow.
11/07/18	The biggest issue encountered at this point is access to the internet. It was noted that development servers were slowing down, potentially due to being blocked. To resolve this issue, a new server had to be created.

3.2. Total Estimation

It is estimated that all of the goals of this phase of development will be completed by 12/07/18. A breakdown of estimated hours to complete each task is as follows:

Task	Hours
Logo Design	3
Website Wireframe	2
Website UI Design and Development	40
Optimised Journey Planner Development	30
Heat Map Development	15
Local Tour Guide Matching System Development	20
Database Definition and Implementation	30
Documentation	10
TOTAL	150

3.3. Screen Shots

Database Design (6/07/18)

Journey Planner (6/07/18)

Guide Matching System Design - Guide's Perspective (12/07/18)

Landing Page Content (12/07/18)

About Page with Formatting Issues (12/07/18)

About Page Developer Section with Formatting Issues (12/07/18)

My Destinations Page Without Complete Content (12/07/18)

Heat Map Embedded in Website (12/07/18)

Journey Planner Styled to Match Website (12/07/18)

Journey Planner With Activity Descriptions (12/07/18)

Journey Planner Timetable Output (12/07/18)

Receipt for Trip Purchase (12/07/18)

4. Meeting Summaries

Date	Notes
5/07/18	-Henry: Preliminary development of OJP completed, undergoing further refinement -Léa: Completed various logo designs for the company and the Travolla product, completed the landing page of the website -Ed & Ada: Started the design and implementation of the database -Erik: Started generating the documentation -Jason: Started researching the implementation of the heat map -The team voted on a logo for the company and for the Travolla product
6/07/18	-Henry: Rewritten OJP backend to make more clear and enable further adaptation in the future -Léa: Refinements of landing page and development of login and signup forms -ED & Ada: Further implementation and refinement of database. Hosted database on server -Erik: Completed documentation -Jason: Implemented basic heat map features, looking into finding current location
9/07/18	-Henry: Continued development of OJP backend. Will be working on linking to database. Considered a number of options for secure linking: Node.js, AJAX -Léa: Successfully linked sign-up forms to database. Completed logout procedure. Working generally on login sessions -ED: Further implementation and refinement of database -Ada: Populated database with attraction contents -Erik: Finalised additional diagrams and descriptions in documentation. Converted documentation to markdown and uploaded to GitHub wiki. Added images to wiki -Jason: Implemented advanced map features such as finding current location. Working on calculating travel time and refining map features
10/07/18	-Henry: Successfully linked OJP to database. OJP now pulls information on activities from the database -Léa: Working on sign-out mechanism and making UX tweaks surrounding what happens when users are/aren't logged in -ED: Began work on the implementation of the guide matching system -Ada: Working on the guide matching system from the guide's interface perspective -Erik: Created 'about' page. Updated documentation -Jason: Finalised heat map for China. Working on how to provide heat map functionality in other regions
11/07/18	-Henry: Finalised OJP and now assisting with development of guide matching system -Léa: Development of UI for OJP -ED: Continued development of guide matching system from tourist's perspective -Ada: Continued development of guide matching system from guide's perspective -Erik: Finalised 'About' page. Experimented with JavaScript to create dynamic cards for various UI elements. Updated documentation -Jason: Continued refinement of heat map
12/07/18	-Henry: Created Android application based on the Travolla website -Léa: Fixed header for each page and altered pdf receipt. General bug fixes -ED: Continued development of guide matching system from tourist's perspective -Ada: Continued development of guide matching system from guide's perspective. Working on updating the UI to match the design of the Travolla website -Erik: Created content for About and Landing pages. Updated documentation -Jason: Continued refinement of heat map
13/07/18	-Henry: Integrated guide page into main site. Finalised guide matching system from tourist's perspective -Léa: Updated header to include 'My Tours' section for guide site, index page login now directs to either tourist or guide site, responsive progress bar in sign-up, updated site photos -ED: Finalisation of guide matching system from tourist's perspective -Ada: Finalisation of guide matching system from guide's perspective. -Erik: Updated documentation. Completed UML diagrams. Prepared content for presentation -Jason: Prepared visuals for presentation

5. Retrospective

6/07/18:

At the end of the first management cycle (Friday 6/07/18), the team reflected on the progress of the development of Travolla. Both positive and critical reflections on the progress were made and from this, a list of recommended actions to take for the next management cycle was produced.

Keep	Problems	Try
-Seeing everybody everyday and working in the same place makes progress faster -Division of jobs based on each member's skillset, but also taking an interest in every member's jobs to spread knowledge	-Github synchronisation problems due to VPN	-Disconnecting from VPN whenever pushing to Github -Organising more time to work collaboratively

13/07/18:

Keep	Problems	Try
-Seeing everybody everyday and working in the same place makes progress faster -Division of jobs based on each member's skillset, but also taking an interest in every member's jobs to spread knowledge	-Merge conflicts on Github -Differences in design of certain pages	-Since we are in a small group, we found that messaging the group chat when someone is going to work on a document so that only one person is working on a document at one time, was more efficient than resolving merge conflicts -Working together to ensure that one consistent design theme is followed, and adapting all pages to this theme -Organising more time to work collaboratively

6. Next Iteration Planning

Many additional features are planned for the next iteration of the Travolla service. Most importantly, a mobile application will be developed to allow users to access the service natively on mobile platforms such as smartphones. This application will contain all of the key functionality of the website. Travolla will further expand by incorporating more major cities in its database. Additionally, a more complex optimisation algorithm will be employed in the OJP. This will factor in details such as precise opening hours and the seasonal availability of activities. Finally, Travolla will be further refined based on the feedback of users.