You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello to all,
Today I’ll try to outline in general terms how we organized work in Trello when we abandoned Asana and switched to Atlassian products for different divisions.
When I came to my previous place of work, the guys worked through Google Docs, used Skype and nothing else... Later, the management themselves found and voluntarily forcibly placed Asana. It was not bad, better than nothing, but not ideal. All the same, Asana is a specific system, which is not suitable for everything.
I was given a project to develop and support one system. We will not go into the quality of the code and other technical things today, so we will focus on the process.
The development and support process itself was one, one came from the other. Again, I will not describe what the process was like before we decided to change it, but after the changes, it became like this:
1) The request comes from customer
2) Prioritization, communication with the customer
3) Deadline Definition
4) Setting the request to the backlog, identifying all assignees
7) Closing a task inside a team
8) Closing a task by a customer
Two large divisions are immediately evident here: external work with the customer and internal work with the team. This is not the most trivial task in Trello, so we used two different boards. Then everything is quite simple:
The customer board contains the following columns:
1) New challenge
2) The task is taken into study.
3) Questions to the customer
4) Task planning
5) Task scheduled
6) On check
Yes, there are a lot of statuses, but specifically this customer needed to see the entire cycle of the task in order to understand what stage it was at. It is also important to say that for most of the markers, we used labels. For example, in the 5th column “Task planning” in the label they indicated which sprint it was planned for, and in column 3 “Questions to the customer”, we used labels to display the priority of the questions.
When communication with the customer is over and the task is planned, it is cloned with all correspondence into the internal board, a link to the inclined card is put in the commentary on the tasks. To display the fact that the task is inclined, I also used a label, since there are no connections between tasks in different boards in Trello. Only the development and testing team has access to the internal board. The customer, project manager, analyst have access to the external board.
In the internal board, a completely autonomous process, the development team should not bother much about how they communicate with customers, they saw the functionality. In internal development, we built such columns:
2) Priority tasks for work
3) In work
4) In testing
5) Internal acceptance of the task
6) Custom approval
7) Task closed by the customer
With labels, we showed priority, and also showed which team the task belongs to. After the task passed the internal acceptance, we transferred the related task to the customer’s board for verification.
As a result, we got a system in which the customer can work, without the use of emails and other messengers, and a team that works on tasks both from the customer and within the team, the tasks simply queue and go through a single workflow.
P.S. We started to use the Jira Software later, and used it for other projects, larger and cross-team.
I will be happy to answer your questions :)