Created Project plan (markdown)

Project-plan.md

@@ -0,0 +1,28 @@
+# Roles in project
+Tanel: Team leader, Developer, Tester
+Henrik: Android UI/UX, Requirements Engineer, Documentation
+Kevin: Scrum master, Developer, Tester
+Lemmo: Product owner, Developer, Tester
+
+# Communication means
+Main information exchange is conducted through in-person meetings.
+Specifying smaller details is done over email.
+
+# Work process
+**How and using what materials is the customer going to understand what you are going to build?**
+The customer has access to the project during the entire process via the open source GitHub repository and we will discuss with the customer what we are building during the in-person meetings as well.
+**How do you determine that the customer is accepting your solution proposal?**
+The customer is asked to give feedback when new features are implemented.
+**How are you going to internally 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.)**
+Team leader will assign tasks
+All developers will implement the tasks assigned to them
+Tests will be written (unit tests and likely system tests)
+Code can be reviewed by all teams members (two accepts needed per commit to approve it)
+All members will be responsible for verification
+Client will do the validation at the end of the sprint (acceptance testing)
+**When do you consider something ready to be delivered to the customer for review?**
+After the new features pass the manual and automated testing.
+**How do you gather feedback from the customer and/or end users?**
+In face-to-face meetings and via email.
+What is the definition of DONE on a task
+Tasks can be considered done after a code review is completed (accepted by at least 2 developers) and verification passes.