Project Plan

Roles in Project

In this project, the clients are also working on the project and the students are an addition to the team.

Clients

• Timo Toots Frontend developer
• Mou - Backend developer

Students

• Bruno - Backend developer, outgoing data
• Andri - Backend developer, filtering data
• Sander - Backend developer, incoming data
• Anton - Frontend developer, documentation

Work Progress

How and using what materials the customer is going to understand what you are going to build
As the customer participates to the building, the customer has a good idea of what is going to be built. In addition to that, meetings are scheduled according to the customers needs to be able to synchronize work.

How do you determine that the customer is accepting your solution proposal
The solutions will be discussed and with the customer during the meetings.

How you are internally going to build the accepted solution (who assigns the tasks, who is going to implement it, will the tests be written, will code be reviewed, who is going to verify, who is doing the validation, etc)
Implementation is done by the person who is in charge of the subsection of the project (see "Roles in Project"). Assignment will be done according to the same rule and will be done by the person in charge of the subsection. Code will be reviewed and verified by another group member assigned by the person who did the code. Validation is done by the customer as they also participate in development.

When do you consider something ready to be published to the customer for review
The customer's participation in the development makes that the customer reviews constantly. The publication will then be done with a commit with a message on Slack.

How do you gather feedback from the customer and/or end users.
Feedback is gathered on the Slack and during the scheduled meetings with customer.

What is the definition of DONE on a task
A task is assigned to an issue, which is considered DONE when the issue is closed (usually linked to a commit). The issue is closed by the member of the team who is testing the commit.

Scope

In our current scope, the high-level tasks to be done in the project are:

1. Gather datasets from various sources and parse them (Sander 50h)
2. Filter and standardize all gathered data (Andri 50h)
3. Serve standardized data as a CKAN service with the CKAN API (Bruno 50h)
4. Create a textview to use with the API (Bruno 10h)
5. Help to create the WEB UI for the service (Anton 30h)

Detailed estimates:
2nd iteration
3rd iteration
4th iteration

Communication means

The communication with the client and the internal communication is done through Slack. Meetings with the clients are done regularly to discuss current state of the project