Trello Workflow: Role of a Project Manager, QA and Developers
Trello is a web-based project management tool that allows individuals and teams to organize and prioritize tasks and projects. In a Trello workflow, the role of a project manager, QA, and developers can vary depending on the project and team structure. However, here is a general overview of their roles in a typical Trello workflow.
Project Manager in Trello:
The project manager is responsible for creating and managing the Trello board for the project. They oversee the entire project and ensure that everyone on the team is on the same page. They set the project timeline and deadlines and assign tasks to team members. The project manager also reviews progress and ensures that the project is progressing according to the plan. They may use labels, due dates, and comments to communicate with team members and keep track of progress.
Developer in Trello:
The developers are responsible for implementing the project requirements and delivering the product. They use Trello to manage their individual tasks and collaborate with the team. They can create cards for their tasks and move them across different lists as they progress. They may use checklists to break down the tasks into subtasks and attach files or links to the cards. Developers can also use comments to communicate with the project manager, QA team, or other team members.
New List: The project manager, team lead and Product owner should know the full business logic about the project Then they will create the card in New List.
Task Owner: Project Manager
N.B Anyone can create the tickets if the requirements are needed.
Priority Backlog List: Then the project manager and Clients will select the card for the sprint. Then both will decide along with the developers to set up the first sprint. Card priority must be known to the project manager and QA team. Owner: Project Manager.
Sprint Backlog List: Every declared card will stay on this list. The Project Manager and Developer are able to add or move the cards in this list. Sprint will be added in this section.
Owner: Project Manager & Developers.
If sprint was declared, then the Developer picked the card from Sprint Backlog. Every card in the sprint backlog should stay in one week.
Planning List: After the declaration of the sprint if any planning needs Developers, then set the card in the planning section. Card status must be monitored by the Project manager each and every time.
Owner: Project Manager & Developers.
In Progress List: If there is no need for planning, the Developers put the card in the InProgress section. After taking the card InProgress they should be assigned their name. Developing time will be included for each card in the comment section while having the Developing card item. A single developer does not put more than one card in the InProgress List. If the developer has any doubt or question about the specific card they will list them along with the tester and give the list to the project manager and ask for help or answer from the Client.
Owner: Developers.
Incomplete List: If Developers get any Priority list, then Developers put their current card into InProgress to Incomplete. Then they put their new card in InProgress and work on this card. If the Lead Developer finds any Error in the code reviewed list, then that developer puts the card in the incomplete List.
Owner: Developers.
Code Complete List: After complete coding Developers put the card in the code-complete List.
Owner: Developers.
Code Reviewed List: After code-complete Lead Developer puts the card in the Code Reviewed List.
Owner: QA team & Developers.
QA Team in Trello:
The QA team is responsible for ensuring the quality of the project deliverables. They use Trello to track bugs, issues, and feedback from stakeholders. They may create a separate board or list to manage the bugs and issues. The QA team can use labels to categorize bugs, and due dates to prioritize the critical issues. They also collaborate with developers and other team members to resolve the issues and ensure that the project meets the quality standards.
Code Reviewed List: First of all, that specific card must stay on Code Reviewed List. Then a tester takes the card from Code Reviewed and puts it on into the Test-In-progress List With giving the name of the QA Engineer and removing the name of the Developers’ name at the same time.
Owner: QA team & Developers.
Test-In-progress List: After that card will stay in this List along with the Tester name. Testing time will be included for each card comment section. Then testing will start as a tester.
Owner: QA team.
Tested List: After Finishing testing the tester put back the Tested list and also gave back the Developers name on it. The Project manager gets the card on the Tested List.
Owner: Project Manager & QA team.
Completed List: Then the project Manager takes these cards and puts them on to the Completed List.
Owner: Project Manager.
Open List: If bugs are found in testing progress, then the tester will put the card on the Open List. A Bugs list should be included on that specific card. Then the Developers take those cards on the Open List and put them on InProgress List while the card has the developer’s name.
Owner: QA team & Developers.
Released List: The Project manager gets the card from the Tested List. Then put them into the Released List When the dev branches are added to master and the final project is on the production means in the Live server. After that smoke test will be tested like normal testing (Like Is the link is working, overall functionality check) that’s it.
Owner: Project Manager & QA team.
Closed List: Then the Client will take the cards from the Released List and will be working on his UAT (User Acceptance Testing) which means he finds all the cards are working correctly and he found the final product. Then the Client takes each card, checks them manually, and puts them in the Closed List.
Owner: Client.
Deferred List: While the developers have no time for updating that specific card or The Client has no time to give a brief about that card then that specific card will remain in the Deferred List.
Owner: Project Manager & QA team.
Won’t-Fix List: Created card cannot be deleted if the cards are duplicated. These types of cards will stay on this List while having comments like (_ No card having details about this card). The tester can put the cards in here. Owner: Project Manager & QA team
Conclusion:
Overall, Trello is a versatile tool that can be customized to fit different team structures and workflows. It helps team members collaborate effectively, track progress, and deliver high-quality projects on time.
🔰 Connect With us🔰
Website : https://devxhub.com/
Linkedin : https://www.linkedin.com/company/devxhubcom
Facebook Page : https://www.facebook.com/devxhubcom
Twitter : https://twitter.com/devxhub_com
Instagram : https://www.instagram.com/devxhub_com
Pinterest : https://www.pinterest.com/devxhub_com
GitHub : Developer eXperience Hub (github.com)
Medium : https://devxhub.medium.com/
Follow or join the recruiter’s LinkedIn Account :
https://www.linkedin.com/in/hudacse6/
#Trello #TimeManagement #Development #QA #QualityAssurance #Management #ProjectManager #Developer #TimeManager #Testing #TestCase #Automation #Businesslogic #BusinessAnalsis
