Requirements and Releases in CA PPM

[Legacy User]

Looking for best practice recommendations.  14.2, on-prem.

 

My Story:  Requirements for CA PPM config changes, portlet/report design, changes, etc. and their releases are currently managed in MSWord docs.  Have opportunity to move this into CA PPM as a trial.

 

Questions:

- If using this feature, happily, how have you accomplished this?

- When plugging in Agile tool, later (Jira, VersionOne, Rally), does any of the work done in CA PPM Requirements and Releases translate to the Agile tool, or does one shutdown CA PPM Requirements and Releases, starting over with the new Agile tool one has plugged into CA PPM?  (I.e. is it better to wait for Agile tool and do this there?)

 

If someone is willing to share best practice via web meeting, please, let me know - our team would really appreciate seeing someone using these features, happily, creating value.

 

Dale

[Andrew M]

Hi Dale,

 

We've been using JIRA to manage CA PPM development for a while now and I've found it to be very easy to use and track delivery of items.

In regards to your question, I'd argue wait and do it in the new tool, rather than the temptation of a "bridge".

If you would like a call about how we use it, happy to share.

 

Andrew

[mike2.2]

Thanks Andrew, we are heading this way as well.