Forum Discussion

Aleksi1's avatar
Aleksi1
Occasional Contributor
4 years ago

How to organize best Zephy Scale with multiple projects and a central Testing Team

Hi everyone   We have multiple Products, which are related to each other (SW and HW). Therefore, we have multiple Jira Projects. Every project team has also it's tester who writes Test Cases and is...
Zephyr Scale
  • MisterB's avatar
    MisterB
    4 years ago

    Hi Aleks,

     

    I'm not sure if there's a 'best approach' for this scenario but what's most important to me is reporting to stakeholders and making that as efficient and accurate as possible, so I would go with a centralised Project.  That way, I could report overall testing progress within a single project, and not have to report from multiple Product projects - and I could still also report by Product, by using Test Plans and Test Cycles.  You could also setup your Folder structure to replicate the Product setup you have, and create a Folder specifically for your System Testing team.

     

    Hope that helps.

     

    Best, Andy

Aleksi1's avatar
Aleksi1
Occasional Contributor

Thank you MisterB. Exactly what I was searching for and it works 🙂

 

But to extend my question. What are the best practices, if you have an "external Test Team". Should we

* create the Test Cycles and Test Plans in the "Test Project" where all the Test Cases from all Products are

* or should we create Test Cycles and Test Plans within the Product Projects and use the Test Cases from the centralized "Test Project"

 

The thing is, that this "Test Team" is testing all products. Should we organize it from a centralized Testing Team point of view - so everything related to product testing is in the same project.

Or should the Test Team switch to each Jira Project and execute the Test Plans and Test Cycles in the corresponding product project.

Best 

Aleks

MisterB's avatar
MisterB
Champion Level 3
4 years ago

Hi Aleks,

 

I'm not sure if there's a 'best approach' for this scenario but what's most important to me is reporting to stakeholders and making that as efficient and accurate as possible, so I would go with a centralised Project.  That way, I could report overall testing progress within a single project, and not have to report from multiple Product projects - and I could still also report by Product, by using Test Plans and Test Cycles.  You could also setup your Folder structure to replicate the Product setup you have, and create a Folder specifically for your System Testing team.

 

Hope that helps.

 

Best, Andy

  • Aleksi1's avatar
    Aleksi1
    Occasional Contributor
    4 years ago

    Thank you Andy.

    I was aiming for the same solution. Just to make it easier for the test team to manage the test cases and the reporting.

    However, I think there will be still some test cases in the project (test automation).

     

    Thank you & Best

    Aleks