Project-Board.md

+
 [**<- return to homepage**](Home)
 
 
@@ -6,4 +7,24 @@
 Our project board and all issues/tasks created are available [***HERE***](https://git.cs.usask.ca/test_alpha/project_1/-/boards).
 
 
-[EXPLAIN HOW WE LAID OUT THE ISSUES]
\ No newline at end of file
+Used 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. 
+
+Open:  It consists of issue 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, issue related to 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.
+
+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".
+
+  
\ No newline at end of file