Skip to content

Changes

Page history
minor grammar edits authored by Jay Shah (jrs349)'s avatar Jay Shah (jrs349)
Hide whitespace changes
Inline Side-by-side
Project-Board.md
View page @ 4e58034f
......@@ -11,10 +11,10 @@ We used the Kanban technique for setting our project board as we used Agile meth
columns for differentiating issue types and for tracking their progress status.
Our board consists of 5 columns: Open, Backend, FrontEnd, Doing and Closed:
* Open: Issues 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 is not explicitly classified as 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.
* Doing: Issue from Open, Backend, and FrontEnd which are assigned and work is in progress.
* Closed: Issue whose progress is completed or discontinued as a feature has been dropped or changed.
*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).*
......