> For the complete documentation index, see [llms.txt](https://handbook.renaissancelabs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handbook.renaissancelabs.org/collaborating/communication-channels/working-with-trello.md).

# Working With Trello

### Steps <a href="#steps" id="steps"></a>

The Board Contains 3 and 6 Basic Board Columns for Management and Engineering Teams Respectively. For Management Staff, the Board Columns Includes; To Do, Doing and Done. For Engineering Team, the Columns Includes; Backlog, To Do, Doing, Code Review, Testing

#### BACKLOG: <a href="#backlog" id="backlog"></a>

* Possible things that can be added or done, features that can be implemented.
* This is the staging area where specs should get fleshed out.
* No limit on the list size, but should be reconsidered if it gets long.

#### TO DO: <a href="#to-do" id="to-do"></a>

* A list of Tasks and Activities to be Carried within a Week.
* Tasks Should be Added Every Monday to the Cards on this Column
* Each Card should have a description explaining the task and expected outcome
* One or More Persons can be assigned to a card to ensure efficient delivery

#### DOING: <a href="#doing" id="doing"></a>

* Ongoing Tasks should be moved to the Doing Column.
* Each User is not allowed to have more than 2 Cards in Progress.
* All Users should have at least one item in this state.
* Any Ongoing Task should be deleted from the To Do column
* There should be a Timeline attached to each Card in this column
* Task Here can be broken into bits especially where a checklist is applicable.
* Documents, Designs, Links, Videos can be attached here for reference purpose.

#### CODE REVIEW <a href="#code-review" id="code-review"></a>

* This list is for items in code review.
* When a task has gotten approval, it moves off to Testing.
* If there are too many cards here, we should break off from other tasks to get code review done.

#### TESTING <a href="#testing" id="testing"></a>

* Cards come here after being code reviewed, and we're in a place for QA and fixing things QA finds.
* Design review also happens at this stage

#### DONE <a href="#done" id="done"></a>

* Completed Task.
* Only Team Lead for Product Team is expected to Push a Task to the Done Column.

Links to the completed Task should be attached to the Done Column.

### Notes: <a href="#notes" id="notes"></a>

* Any Urgent Task added should be recorded and the date of addition should be noted.
* Blockers should be reported before EOD in a checklist Format.
* Cards should be updated by EOD.
* All communications should be done on Slack with Link to the card attached for reference.
* Any Task Carried over to the Next week, should be reported to the Team Lead and such task Must be completed on the Tuesday of the Next Week.
* The Menu Bar contains an Activity Log stating time and Name of a User that makes a change, and the time the changes was made. Everything is Monitored

<br>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://handbook.renaissancelabs.org/collaborating/communication-channels/working-with-trello.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.