Mistakes made in the workflow setup may not be noticeable at the beginning of project development. Moreover, it might seem that the setup has no drawbacks, but eventually, the mess will undoubtedly occur as the project grows. This can lead to an unwanted situation of changing workflow in the middle of development. Thus, the key to success lies in preparing the proper structure which will last throughout the whole project development cycle.
Taking a look at the case of a custom website, its development could be split into two parts:
- Front-end development and design to make sure the website satisfies the client expectations
- Back-end and integration to make sure the website works perfectly as a unit
The simple Trello design pattern in such a case would be to create two lists for the two parts mentioned above. Each list would be filled with cards, each one is a task with a specific deadline, description, etc.
Completing the task would only require moving the card to a separate “Done” list. Sounds simple and efficient, doesn’t it? It might seem this way, but only for the first stages of the project. Problems start to appear when developing the second part.
The growing number of cards and their complexity might result in making navigation of your Trello board a nightmare. What to do when you have 30 tasks waiting for you? How could you define which tasks are in progress or which have a priority over another? This is not the situation you wanted and you instantly realize that something went wrong at the stage of the initial workflow setup. Now it is time to clean things up.