Cross Functional / Global Project Requirements

[Paul Bryant]

We are about to start a new project where we will be using Confluence and Jira to support a large mixed (Infrastructure & Software) system development. The organisation is a large traditional waterfall system engineering business, and this is its first foray into the agile world. But we have been using Jira for some time for issue management.

What is the best approach for dealing with cross functional requirements Such as security or global look and feel? As duplicating the requirement for each component doesn’t feel right is there a way to cross link each component or epic to say a security Epic or create a cloned story that’s stays in sync with the original security story so if the master requirement changes it ripples through the clones?

Thanks

[francis]

Hi Paul,

Aren't these requirements part of the general acceptance criteria of ongoing developments. 

In our case we do have test plans checking specific concerns such as security, performance, reliability.  These test plans are currently documented on our confluence (and/or automated in our integration tests)

Whenever for instance a security requirement changes, our test plans get modified accordingly.  During the validation of a release, we check if these acceptance criteria are met. In case it failed some criteria, a bug is raised against the feature with a link to the testplan and prioritised accordingly.

Not sure if this is the 'best' approach - but it works for us.

Francis

[paul bryant]

Hello @francis

Thank you for your quick answer, but in this organisation they are seen as hard and fast requirements. That need to be fully documented / scrutinised during development especially the safety and security. 

So we really need to treat them as requirements, so any advice on cloning or linking would be appreciated

Many Thanks

Paul