Lists and Cards Within Trello
Last updated
Last updated
Trello allows for documentation of the tasks that your team has done. Within Trello there can be multiple task groups (lists) and within the task groups there are subgroups or task cards that specify what to do for the card in that list [11]. For example, as seen in Figure 14, within the Iteration section of our methodology, our team specifically had “Backlog”, “To Do”, “In Progress” and “Completed” grouping of tasks. In a CS project, the lists do not have to be named what we have verbatim, but the naming of the lists should classify the different stages the developed code is in. Figure 10, also shows the difference between a list and card.
The way that the structure of the board works is that there are cards that live within lists. Each card lives within a list and is representative of a task that belongs to a certain category. These categories are user-defined. Although we chose to use 4 groups, the organization of lists is often left up to the project manager. Like in Figure 2 which simply contains a “To-Do”, “Doing”, and “Done”, depending on your project there can be less lists. Sometimes, especially with software development, students may want another list for “Testing”. Oftentimes, with classes like CS 3110, projects will require a large number of tests to be done before the project is finished. If the completed task has accompanying code, and that code does not pass the necessary tests, often the task will be placed back into the “To-Do” list and will be altered to reflect that it needs to change in a certain way to pass the tests.
Once the lists have been created, task cards can be created to fill those lists. In the scope of a CS project, all of the tasks should begin the “Backlog” and begin to move towards the “Completed” list.
A task card or card in Trello also has many customizable features. On the card, the user can assign the team members that are supposed to complete the task, create a timeline for the task on the card, as well as customize the look and feel of the card. On the card the user is able to add comments and things to do that will consider the card to be completed. The user also has the ability to move cards from list to list. Moving a card should only be done if the task is completed. In Figure 11, the customizations of a card within the list is shown.
