Project-Board.md

@@ -7,24 +7,23 @@
 Our project board and all issues/tasks created are available [***HERE***](https://git.cs.usask.ca/test_alpha/project_1/-/boards).
 
 
-Used Kanban technique for setting our project board as we used Agile methodology for development. We used multiple 
+We used the Kanban technique for setting our project board as we used Agile methodology for development. We used multiple 
 columns for differentiating issue types and for tracking their progress status.
-Mainly our board consists of 5 columns named Open, Backend, FrontEnd, Doing and Closed. 
+Our board consists of 5 columns: Open, Backend, FrontEnd, Doing and Closed: 
 
-Open:  It consists of issue related to Milestone for grading or the problem which are not explicitly classified to the backend or frontend. 
+* Open:  Issues related to Milestone for grading or the problem which are not explicitly classified to the backend or frontend. 
+* Backend: Issues related to backend functionality for objected-oriented programming, Firebase database, and Firebase Authentication.
+* Frontend: Issues related to the graphical appearance of the application, XML, Layouts, graphs and other graphic components. 
+* Doing:  Issue from Open, Backend and FrontEnd which are assigned and work is under process. 
+* Closed: Issue whose progress is completed or discontinued as a feature has been dropped or changed.
 
-Backend: Issues related to backend functionality for objected-oriented programming, Firebase database and Firebase Authentication.
+*Note: Instead of using our project board just for user stories (i.e. high level), we used our project board for individual tasks that had to be completed. This was a group decision that we thought would work best for us (and we think it did).*
 
-Frontend: Issues related to the graphical appearance of the application, issue related to XML, Layouts, graphs and other graphic components. 
+How we used our Project Board : 
 
-Doing:  Issue from Open, Backend and FrontEnd which are assigned and work is under process. 
-
-Closed: Issue whose progress is completed or discontinued as a feature has been dropped or changed.
-
-How we use our Project Board : 
-
-1. During our group meeting, we used to create a list of issues to be worked on and classify them based upon backed and frontend. Generally, issues were assigned while they were created. Also, if someone has completed their issue they can look for the unassigned issue, which has low priority. 
-2. If a member found any issue while working on the project and he is not sure how to handle it they can list the issue under the "Open" column and someone will look into it.
-3. On completion of milestones, we always created an issue for milestone evaluation and assign it to the respective Teaching Assistant(TA) under the "Open" column. Once TA starts the evaluation, it can be placed under the "Doing" an,d on completion it, can be moved to the "Closed".
+1. During our group meeting, we created a list of issues to be worked on and classified them as either backend or frontend (or both). Generally, issues were assigned to members of the group when they were created.
+2. When someone completed their issue, they transferred it to the "completed" column. Then, that member looked for other issues assigned to them or open issues that they could assign to themselves.
+3. If a member found any issue (bug/problem) while working on the project and he was not sure how to handle it, then he listed the issue under the "Open" column, messaged in the group Slack communication app, and someone else looked into it (and in many cases for difficult cases, we talked about it during our weekly meetings).
+4. On completion of milestones, we always created an issue for milestone evaluation and assigned it to the respective Teaching Assistant (TA) under the "Open" column. Once the TA starts the evaluation, it can be placed under the "Doing" and on completion, it can be moved to "Closed".
 
   
\ No newline at end of file