Looking for tight ALM integration, ideally making both tools the same GUI. (287 Views)
Reply
Occasional Advisor
Holm_1
Posts: 10
Registered: ‎07-15-2007
Message 1 of 3 (287 Views)

Looking for tight ALM integration, ideally making both tools the same GUI.

To avoid people have to switch tools, use separate logins, copy data and extra eforts to "intregrate" separate tools we are looking for tight ALM integration, ideally making both tools the same GUI. Also to make TestCases, Defects and release manageemnt consistently managed in a single place regardless of an project using AGILE methodology or not.

One imaginable solution would be making both tools having a portlet GUI that can be plugged together into one portal solution.

 

 

Please use plain text.
Frequent Advisor
MacJ2
Posts: 40
Registered: ‎08-03-2011
Message 2 of 3 (284 Views)

Re: Looking for tight ALM integration, ideally making both tools the same GUI.

Tight Integration. Yes Please

 

very much so

 

/M

Please use plain text.
Occasional Advisor
Holm_1
Posts: 10
Registered: ‎07-15-2007
Message 3 of 3 (208 Views)

Re: Looking for tight ALM integration, ideally making both tools the same GUI.

Hi AGM Team,
after some discussions with our team I need to be more precise on what we need:
We do need an AGM to ALM integration like it was done for AANG - ALM to be the master
for all data stored. (not just synchronization = duplication of data)
This is required because we do have a mixture of AGILE and Waterfall model projects.
To run them together into the same release date we do need a consistent view on test cases and status as well as defects. Since Waterfall model based requirements and designs etc. stored in ALM are not well to be migrated to AGM the only consequence is AGM to be based on ALM. Note that this mixture of projects also mean that we continue a project so far run as Waterfall model in AGILE, so people do need access to existing requirements & designs etc. as well as we have cases where projects run as AGILE later continue with Waterfall model (e.g. once implementation matured).

Please use plain text.
The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation