Roles in project

Jaan Susi Front and back end development, database management.

Karl Metsand Working on front end, assets, design, communication with the client, validation.

Taavi Gilden Front and back end development, team representation, communication with professor.

Innar Hallik Back end and some front end development, Wiki management, testing.

Scope

Things we are planning to finish during October

• Android app communicating with online server. App loads information about activities from the server and user can submit new activities to the database.
• Optimized database.
• Tags system on activities.
• Show more info about activity.
• On device backup database for usage without internet connection.

Things we are planning to finish during November

• System to moderate submitted activities, also other database management.
• User system, make account etc.
• User can do actions such as "not now" and "never show again".
• Data pull for the server is corresponding to the user preferences based on use of "not now" and "never show again" functionalities.
• Finish Android development.
• Investigation about Windows and iOS mobile platforms.

Things we are planning to finish during December

• Final debugging.
• Maybe start developing app for Windows and iOS platform.
• Presenting finished product to customer.

Communication means

• Lecturer: E-mail, weekly meetings when needed (Monday 11.00 - 11.30)
• Team: Skype, meetings, git issues
• Client: Available means, Facebook, Skype, e-mail, phone, face-to-face when needed

Staging environment

• Lecturer: During our weekly meetings we show our last stable version to the lecturer on his device.
• Client: During our meetings we show our progress on our own devices.

Continuous Integration

• Our continuous integration is managed by Jenkins.

Work process

The customer already has a good idea of what he wants. To make sure he understands what we can build, we will be in constant touch while developing the app. We do not require any specific materials to build anything since everything we will be creating is purely software. The customer has the right to approve or disapprove the changes if he thinks them unnecessary. A summary is then made to reflect future changes that need to be made. This process will continue throughout the development phase until we have reached the desirable product. Internally, the source code is distributed through git and developed by everyone. The developed features are released/published when it has been developed up to the point where it runs smoothly and without interruptions.

Collaboration Infrastructure

The documentation is in the wiki, collaboratively composed and managed by Innar. If a problem or requirement arises it will be added to the Issues tracker.