Scrum and trello


We work at the Scrum methodology (with some modifications) and the tool which allowed us to implement our management model is Trello.

This is a main view of our Trello. These boxes corresponded to particular areas of our company (like Marketing, Management & Finances), products (MDB Angular, MDB React etc.) or projects (MDB.com Forum, Sandbox etc). There are also boxes intended for me (Ascensus) and for my partner (Adach).

Each box has own specificity, but the following sections must always have a place in it (in Trello they are called cards):

  • To Do
  • In Progress
  • Tests
  • Done
  • Ideas
  • Awaiting

In the case of dynamic projects (i.e. those where the chance of appearance of unexpected variables is high) the section "To Do" was divided into 3 subsections:

  • Sprint - task to do next week
  • High priority - task to do as a priority in the next sprint
  • Low priority - task to do when the section "High priority" is already empty
See picture enlarged

In the case of stable projects (i.e. those where the chance of appearance of unexpected variables is low) we planned the long-term work - for 6 months in advanced. So the "To Do" section is divided into sprints - two-month periods of work.

See picture enlarged

It should be underlined that for a such long-term planning we could afford after achieving appropriate maturity of our products. Before that moment each long-term plan had been broken by an urgent task to do appearing out of the blue (like bugs fixing), as a result it was made impossible to implement this.

After achieving appropriate stability, long-term planning has become a fact. It is a blessing for programmers (because they can not be distracted by "urgent matters" and can plan everything) and as well as for managers, who can implement more ambitious, time-consuming and challenging visions.

A certain task from “Tests” card can be transfered to “Done” card after prior checking only by the project leader. The test procedure will be described in detail in the following articles.

In “Ideas” card are concepts, which are not yet certain whether the will be included in the project. If the project leader decides to start implementing them, adds the idea to the appropriate sprint with the designated delivery date.

"Awaiting" is a place where suspended tasks go, because their completion depends on connected task of another person.


Previous post Next post

Spreed the word: Add comment
About author
Author avatar
Michal Szymanski

Co-founder of MDBootstrap and BrandFlow. Entrepreneur, web developer, UI / UX designer, marketer. Dancer and nerd at the same time.

Leave a reply

Sign up to follow your progress and get additional benefits