Support

Hello,

We currently have the following structure in JAMA:
- Product
- Customer A
- Customer B
- Customer N




All customers purchased a COTS product, with minor custom. We store all product requirements in Product project and the custom part in each customer X project.

Let's take the scenario where:
A review of new set of requirement (let's call it Module A containing SRS #1,2,4,6,9,12) is sent to the stakeholders through the review center, 2 months later the DEV team is ready to start working on Module A and need to be able to look at the latest requirements only and would like to avoid going through the full module requirement again.

The current solution we found is to use Tags, so we group the requirements through Module A tags. However, let's say we receive a CR for one customer and update SRS #1,4,12 from Module A, the team need to be able to look at those requirements only. If they go to the Tree Explorer, they can find those requirements only.

It's creating a huge frustration from the teams to use the tool. They often take the example that in word they could have use the Tack changes feature and be able to quickly highly what was added.

Do you have a best practice to recommend?

Ramy,
Would checking the project activity stream for changes made to reviews be helpful?

Hello,

We currently have the following structure in JAMA:
- Product
- Customer A
- Customer B
- Customer N




All customers purchased a COTS product, with minor custom. We store all product requirements in Product project and the custom part in each customer X project.

Let's take the scenario where:
A review of new set of requirement (let's call it Module A containing SRS #1,2,4,6,9,12) is sent to the stakeholders through the review center, 2 months later the DEV team is ready to start working on Module A and need to be able to look at the latest requirements only and would like to avoid going through the full module requirement again.

The current solution we found is to use Tags, so we group the requirements through Module A tags. However, let's say we receive a CR for one customer and update SRS #1,4,12 from Module A, the team need to be able to look at those requirements only. If they go to the Tree Explorer, they can find those requirements only.

It's creating a huge frustration from the teams to use the tool. They often take the example that in word they could have use the Tack changes feature and be able to quickly highly what was added.

Do you have a best practice to recommend?

Ramy,
Would checking the project activity stream for changes made to reviews be helpful?

Hello,

We currently have the following structure in JAMA:
- Product
- Customer A
- Customer B
- Customer N




All customers purchased a COTS product, with minor custom. We store all product requirements in Product project and the custom part in each customer X project.

Let's take the scenario where:
A review of new set of requirement (let's call it Module A containing SRS #1,2,4,6,9,12) is sent to the stakeholders through the review center, 2 months later the DEV team is ready to start working on Module A and need to be able to look at the latest requirements only and would like to avoid going through the full module requirement again.

The current solution we found is to use Tags, so we group the requirements through Module A tags. However, let's say we receive a CR for one customer and update SRS #1,4,12 from Module A, the team need to be able to look at those requirements only. If they go to the Tree Explorer, they can find those requirements only.

It's creating a huge frustration from the teams to use the tool. They often take the example that in word they could have use the Tack changes feature and be able to quickly highly what was added.

Do you have a best practice to recommend?