# Project Plan

## Table of Contents


## Customer

Craig Bradley:
* Role - Owner of D-Ranged
* Email - [e-mail]
* Phone - 0880193497

## Product Lenenhood

*Name derives from the play on words "Lenen" and "Neighbourhood"*
- Lenen - Borrow or lend
- Neighbourhood - A community

## Group Information

### The Blue Kangaroos

#### Members:

[Henry Wright](@washedszn):
* Student number = 474288
* Mail address = [e-mail]
* Client Liaison, Backend developer

[Kurt Lopez](@Kurtuhkus):
* Student number = 495308
* Mail address = [e-mail]
* Sprint 1 Scrum Master, Backend developer

[Max Uhlig](@MaximilianUhlig):
* Student number = 491072
* Mail address = [e-mail]
* Sprint 3 Scrum Master, Frontend developer & designer

[Mostafa Ali](@mostafaali1995):
* Student number = 499484
* Mail address = [e-mail]
* Sprint 2 Scrum Master, Frontend developer

#### Important Dates:

Client:

* 12th September - Client proposal

*There are other dates when we meet the client but haven't found them anywhere*

Saxion:

* 12th September - Sprint 0 Hand in
* 24th September - Sprint 1 review
* 26th September - Sprint 1 Hand in
* 8th October - Sprint 2 review
* 10th October - Sprint 2 Hand in
* 29th October - Sprint 3 review
* 31st October - Sprint 3 Hand in

## Descriptions

### Persistence Description

Throughout this project the three of us members will be working together in order to fulfil our customers' needs. This will be executed through a scrum structure, in which there will be 3 sprints, each one having a different scrum master.

### General Project Description

D-Ranged wants us to create a web application for neighbourhoods. They will be able to lend and borrow goods via the application.

## Result

### Wireframes
The following images will demonstrate a few of the intended functionalities of the product:

<b><center>User story 09 - Item/Skill search</center></b>
<b><center>User story 10 - Secure user information</center></b>
<b><center>User story 11 - Categorize catalog</center></b>
<b><center>User story 8 - Easy user interface/landing page</center></b>
<b><center>User story 7 - Value Tags</center></b>

**KURT AND MAX ^^^^**

### Deliverable:

* Web application
* System file
* Project file

### Requirements:

Required:
* Web application that allows members of a neighbourhood to lend and borrow items from each other
* Values assigned for compensation amount for damaged/broken items
* Neighbours grouped automatically based on address
* Events section of the application where members of the neighbourhood can post upcoming events
* Compliance with GDPR
* Ratings system for once items are returned to the lender

Not Required:
* Criteria of what you have for other to lend on what you can then borrow.
* Potentially provide an option to own a product as a neighbourhood. Members contribute money towards it.

## Product Backlog

*All items seen below also have corresponding issues, in order to keep track and distribute tasks within the group*

<table>
<thead>
<tr>
<th width="72px" >ID: 01</th>
<th width="428px">Task: Implementing a compensation/fine system for when lent items are broken/damaged</th>
<th width="100px">[Issue Link](#1)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Backend + Frontend</td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> When adding an item to lend, there must be a field on the form where the user inputs a fine amount, in case the item is broken/damaged. This is a required field on the form. Once the item has been returned to the lender, there must be functionality for the lender to take action against the borrower for damaging/breaking the item. This will correlate to the fine amount set by the lender.</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 02</th>
<th width="428px">Task: Creating an events tab/section</th>
<th width="100px">[Issue Link](#2)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + Backend</td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> As for backend developers, the data for each event will need to be stored on the database; consequently api calls will need to be setup in order to have communication between frontend and backend. Then frontend developers need to create a clearly designed user interface for creating and viewing events</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 04</th>
<th width="428px">Task: Functionality for reviews</th>
<th width="100px">[Issue Link](#3)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + Backend</td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Backend developers need to store reviews on the database and have api endpoints so that frontend can communicate with backend. As for frontend developers, all review data will need to be simply displayed to the user and some functionality for writing reviews after a service has completed</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 05</th>
<th width="428px">Task: English and Dutch language support</th>
<th width="100px">[Issue Link](#4)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> The application will be primarily written in English initially. Therefore, once we have finished the English version we will then translate all English elements of the application. Once all elements have been translated, the frontend will need to be updated to handle switching between the two languages. As well as adding a button/dropdown so users can simply switch between the two.</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 09</th>
<th width="428px">Task: Adding a search box for users to quickly pinpoint items/services</th>
<th width="100px">[Issue Link](#5)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Backend + Frontend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Backend: Fetch specific data from the database
<br> Frontend: Only allow the data being fetched to be displayed </td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 10</th>
<th width="428px">Task: Hide information only available to registered users from the non-registered users</th>
<th width="100px">[Issue Link](#6)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Hide sensitive HTML from non-registered users </td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 11</th>
<th width="428px">Task: Create a way for items/services to fall under certain categories</th>
<th width="100px">[Issue Link](#7)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Backend + Frontend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Create a number of general categories for when items/services are posted.
<br>Users can attach a minimum of one category to a item/service. </td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 3</th>
<th width="428px">Task: Offer set of skills</th>
<th width="100px">[Issue Link](#8)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> While users are able to offer up items to be lent/borrowed a user is also able to choose a set of skills
<br>to be used by others.</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 6</th>
<th width="428px">Task: Available hours</th>
<th width="100px">[Issue Link](#9)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Either on the users profile or on their item listing they should be able to state at what times they are
<br> available to either meet up to lend the item or to offer their special skill set service.</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 7</th>
<th width="428px">Task: Value tags</th>
<th width="100px">[Issue Link](#10)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + Backend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> We want to allow the users to add a tag to their items giving a quick overview for their neighbours
<br> to see how expensive an item is to give an insight to the neighbour whether they want to risk lending an expensive item or not </td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 8</th>
<th width="428px">Task: Easy user interface</th>
<th width="100px">[Issue Link](#11)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + Backend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> There should be an easy user interface which will allow for smooth user operations such as browsing, creating
<br> product/service listings and talking with other neighbours about the product they want to lend..</td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 12</th>
<th width="428px">Task: User History</th>
<th width="100px">[Issue Link](#12)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + Backend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Want to give the user the chance to access to his history of his account beside review others history since the joining date. </td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 13</th>
<th width="428px">Task: customer service</th>
<th width="100px">[Issue Link](#13)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + Backend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> Dedicate valid customer services for each neighborhood so the user can inform about any complaints related to his account or his operations. </td>
</tr>
</tbody>
</table>

<table>
<thead>
<tr>
<th width="72px">ID: 14</th>
<th width="428px">Task: social media </th>
<th width="100px">[Issue Link](#14)</th>
</tr>
</thead>
<tbody>
<tr>
<td colspan="10"><b>Roles:</b> Frontend + backend </td>
</tr>
<tr>
<td colspan="10"><b>TODO:</b> We want to give the user the access to the different platforms of the social media so he can share his experience with others and extend his social media network. </td>
</tr>
</tbody>
</table>