Proposal for design team Trello board organising

As a team, design uses a Trello board for organising tasks outside GitHubGitHub GitHub is a website that offers online implementation of git repositories that can can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. and TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub. During this week’s design weekly meeting there was a discussion about how to iterate on this and put it back at the heart of our weekly meetings.

A simpler flowing structure

Here is a structure suggestion might work better and has more of flow across the board. 

  • Inbox
  • Needs design
  • Needs feedback
  • Building
  • Blocked
  • Icebox*

*Icebox will be cleared down every month to avoid becoming a place cards go to become invisible.

Focused labels

Currently, our labels are being used for workflow. By having the above flow this stops those being it and can bring in the labels as subjects.

  • Documentation: identity what needs documentation
  • MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress.
  • CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress.
  • Task
  • First contribution: a great label for contribution day
  • … there might be more labels but keeping simple to start, for example, type of design like icons could be good to note.

In practice, whatever structure we have only functions if we go back to having this board be the focal point of weekly meetings again.

Future considerations

Whilst other processes, tools are interesting to review, for now iterating on what we have is a great first step. Some key points to explore after this first iteration would be:

  • What belongs in TrelloTrello Project management system using the concepts of boards and cards to organize tasks in a sane way. This is what the team uses for example: or should be in GitHub/Trac/other tools?
  • How do we sync everything or even should we?

For now, those topics are out of the scope of this proposal but I note to show they are future discussion points.

Next steps

If everyone agrees this will be implemented in a week and handbook updated with the information on how to use Trello now. Once done, the board will become a part of our weekly meetings again.

The idea is to start by doing this and in a month review if this is working out. One of the problems in the past has been doing something without review.

#trello #organising