What can we help you with?

e.g. Gantt chart, Creating tasks, Sharing folders

How you guy manage developer and QA tasks

6 comments

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Ryan Nelson

    Not a developer but it sounds like your project and QA may be two seperate tasks. Have you thought of using request froms when issues come up that starts tasks to address the specific issues. This could start a new task with your development team to address the issue or bug. This would then create a new task and maybe have a new status workflow.

    -Hope this helps.

    Ryan

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Michael Michalak

    We use QA as a task with specific items that they check as subtasks. They number in the hundreds (which isn't ideal honestly, we are working on it) but it allows each checklist item to be passed/failed easily. Anything that is "passed" is actually being put into a custom completed status, and items that fail are flagged and assigned accordingly. Hope that helps

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Tom Napper

    (Edited )

    QA is separated out for us. After a developmentย sprint is completed QA isย done against known scripts/acceptance criteria. If a bug is found then it is logged independentlyย as a task in the QA folder. We have used forms for this and have also just added the tasks.ย 

    The task of QA is added to the main project with an estimate associated with it. QA tracks their time there or adds sub-tasks as Michael talks about. A couple of basic tasks in the QA folder: Testing, Writing test scripts, and Regression Testing. These are the tasks that QA should be capturing their time to. It's difficult and probably not super productive to have them track time to the actual bug.

    Soย the work looks like this:
    User tracks time to task "Make the widget"
    The user marks the task as "Done"
    PM indicates to QA that Component/Epic/Widget is ready to test
    QA tests tracking time to "Testing"
    QA creates tasks in QA folder for each bug found
    PM reviews tasks and assigns
    User tracks time fixing bugs

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Stephen

    Very interesting Process Tom, thanks for sharing. I'm seeing more and more people using Folder tags - is this whatย you do whenย you add the QA task to the main Project?ย 

    I can seeย the actual work goes through a sort of 'pass the baton' process between the PM and QA. Do you use Workflows and auto-assigning for this? If so, what do the task's Workflow look like for the QA tasks? Is it custom made, for example? Thanks!

    Stephen Community Team at Wrike Part of a Marketing Team? Check out Your Very Own Community Space

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Tom Napper

    Stephen.ย 

    We like sequestering the QA tasks into a separate lane as it really gives us a view of whatย may be happening globally on the project. For example, we might be seeing an issue with a particular browser, when QA tests individual tasks, finds the bug it is difficult to see that we are having global issues with a particular browser, it just shows up as an issue with a piece of work. Not sure if I'm making sense.

    We tag QA tasks to the folder we are currently working in and the component it effects. So it could be tagged "QA" "Current - Sprint 2" and "Product Detail Page". This allows the PM to understand the work that needs to be completed for Product Detail, how much work is still needed to complete Sprint 2 and how far QA has gotten in testing. All QA tasks are initiallyย assigned to the PM/Producer.

    We don't use AutoAssign in the workflows for QA we do use them when a task moves from InProgress to Ready for Code Review.ย 

    We do not use a separate QA process flow. It was tried on one project and abandoned it. We use the Board view at our daily status meetings. Board views don't work well if you have multiple workflows for tasks in a folder. It also became a nightmare to remember to change the workflow.

    One of the biggest learns we have is to not use sub-tasks for QA. We love the organizing value of a subtask but the fact that it is hidden in most views makes it difficult to gaugeย what work is left to be completed when we are doing status meetings.

  • Spot On! ๐Ÿ‘ Innovative Approach ๐Ÿ’ก Stellar Advice ๐Ÿ’ช
    Avatar
    Stephen

    Thanks for the detail Tom!

    I think your approach is a very suitable best practice for this. Basically, in a lot of ways, you have the QA and PM/Devย tasks separate butย they're givenย reference to each otherย (and theย main Dev Project) by using tagging. It's a nice clean approach ๐Ÿ‘Œ

    I thinkย you're right too about using Custom Workflows for this as it can get a bit confusing for people. However, the auto-assign can come in useful, just like you're using it for when tasks are Ready for Code Review.

    I've reached out to our own QA team to see learn a little bit about how we do thisย in Wrike, so I'll post it here when I can ๐Ÿ‘

    Stephen Community Team at Wrike Part of a Marketing Team? Check out Your Very Own Community Space

Please sign in to leave a comment.

Folllowing List for Post: How you guy manage developer and QA tasks
[this list is visible for admins and agents only]

Community

Welcome ๐Ÿ––

Hi there! ๐Ÿ™‚ Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome ๐Ÿ–– Have you checked out this week's Release Notes yet?

Hey! ๐Ÿ‘‹ Curious about something? Visit How To to search and ask the Community for answers.

Welcome! ๐Ÿ‘‹ Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.