MC Tools
Description and tutorials of how to use the tools used in the MC team.
Last updated
Description and tutorials of how to use the tools used in the MC team.
Last updated
When you get an invite, please put your attending response there, it literally takes 5 seconds.
Tutorials before diving into how we’re going to use it.
For the ones that like to read more: click here and read at least the Trello 101 and Feature Deep Dive articles
For those who like to watch videos more: link.
We’re going to use Agile project management, specifically a mix of Scrum and Kanban (you can get some info about what they mean and what’s the difference from the #learn slack channel, on the pinned messages).
After you’ve accepted the invite your TL has given you, you’ll be added to the team where most of the boards reside.
This will contain the big battles and plan for each Q, and will be used to define and select tasks for the “next sprint”.
The board that you’ll work most of the time.
We’ll use this to track sprint tasks and has lists with the logical flow of our workflow (besides some self explanatory informative lists: links to other boards, useful resources [where you’ll find the link to this file], topics for the next meeting, and meetings outputs - this list is a work in progress)
Use to create cards for including worthwhile topics for the next team meeting.
Sprint list
Contains the tasks that we defined to be fulfilled in the current sprint (they come from the Q Roadmap Board)
In Progress
The task that the team is currently working on (we’ll define the maximum amount of tasks that a member can have In Progress at the same time)
Done
Well, pretty straight forward, tasks that have been completed.
Blocked
Tasks for some reason cannot proceed (maybe you’re waiting for another task, or member to complete another task, or waiting for an external party to be completed)
Not yet finally defined how we’ll use this one, but it currently has the purpose to contain all the info about our digital presence: our website, the wiki, entity dashboard etc.
Not yet finally defined how we’ll use this one, but it currently has the purpose to contain all the info about our EwA projects: WLL, YSS, YSF etc.
Descriptive Title (don’t be afraid to make it long, but not too long)
Description (if necessary, it usually helps with explaining what needs to be done, if task was created not by the “implementer”)
Labels (used to group type of tasks, define if it’s one that should be done by LC, important, urgent etc) Eventually we’ll add or remove labels to fit our workflow.
If task has a definite deadline: include a Due Date
IF the CARD is a MEETING. Additional “tags” are for defining if a card is a meeting and to better understand the purpose and people present:
[MC2LC]
[MC]
[MC2RO]
Feel free to add others, but be consistent in them. They are used by starting the name of the card with them. In the card name, in parenthesis, include the date the meeting happened.
Example: [MC2LC] oGV Meeting (4 August)
You must create an account using your AIESEC email and then send it to your Team Leader for him to add you to the Clockify workspace.
You can add time either by:
Entering it Manually, after you’ve completed the task you enter what you did in Clockify and how much it took
Entering it as a Timer, which means that you “click” on the tracker when you start the task and click again after the task has been completed.
And you can use it to start tracking Trello tasks within the board or calendar events
By clicking the “Start timer” button, you will automatically start tracking your time with the entry of the Trello card name or Calendar event name respectively.
(At least) a member assigned to it
