Updated Project plan (markdown)

Lemmo Lavonen 2021-09-19 16:06:55 +03:00
parent 58ff9115e6
commit ccd7facfc5

@ -1,12 +1,14 @@
# Roles in project # Roles in project
Tanel: Team leader, Developer, Tester Tanel: Team leader, Developer, Tester
Henrik: Android UI/UX, Requirements Engineer, Documentation Henrik: Android UI/UX, Requirements Engineer, Documentation
Kevin: Scrum master, Developer, Tester Kevin: Scrum master, Developer, Tester
Lemmo: Product owner, Developer, Tester Lemmo: Product owner, Developer, Tester
# Communication means # Communication means
Main information exchange is conducted through in-person meetings. Main information exchange is conducted through in-person meetings. Specifying smaller details is done over email.
Specifying smaller details is done over email.
# Work process # Work process
**How and using what materials is the customer going to understand what you are going to build?** **How and using what materials is the customer going to understand what you are going to build?**
@ -19,12 +21,8 @@ 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.)** **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 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
All developers will implement the tasks assigned to them Client will do the validation at the end of the sprint (acceptance testing).
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?** **When do you consider something ready to be delivered to the customer for review?**