Our vBulletin migration is complete.
Welcome vBulletin users! All content and user information from the Micro Focus Forums (vBulletin) site has been migrated to this site. READ MORE.
mike_se Contributor.

PPM Support Tip: Agile Integration (AgM) clarification questions

A new KCS article was published: KM00603391


When reading the documentation for Agile Integration (AgM), some answers to clarification questions

After reading the documentation on the Agile Integration (HP Solutions Integrations Guide for PPM 9.20 and the PPM 9.21 Release Notes), a User wanted clarification on some questions that they had.

For this integration, HP is introducing the first steps, hence there are some "limitations".

Documentation Defect QCCR1L52764 was logged for these questions.

See comments below after each question:

1.  Page 392 of the HP Solutions Integration Guide for PPM 9.20:  The last bullet on the page states that a Task can have no Actuals and can not be in the "In Process" Status.  What is the reason for this?  Can the Task be in at a Status other than "Ready" such as "Awaiting Predecessor?"

[Answer] In this version of AgM Integration, it is using the method Remove All and Add All to update the Agile information as Tasks in the Work Plan. All Tasks can be tracked in the Time Sheets and have time logged against them. To avoid deleting the Actual information or updated information in the Agile Tasks that are imported from Agile Manager, PPM makes these "Agile Tasks" as Read Only and User is not able to edit any information for these "Agile Tasks".

2.  Page 401 of the HP Solutions Integration Guide for PPM 9.20:  The opening paragraph reads, "Once the mapping relationship is established, it retrieves real-time information from the target server and displays..."  Would not this actually be "near real-time information based on the sync interval?

[Answer] In this Agile Integration, there are two kinds of information PPM will retrieve from Agile Manager. One is: the graphs, e.g. Sprint Burn Up, Release Burn Down Chart, and these graphs are retrieved real time from Agile Manager. The other type is: the Release/Sprint/Backlog information retrieved from Agile Manager into the PPM Work plan. and these are retrieve on the sync intervals by the sync up service and not in real time. The documentation is referring to the first type of information.

3.  Pages 403/404 of the HP Solutions Integration Guide for PPM 9.20:  Step 4 on Page 403 screen shot shows the "Agile Project Timeline" Tab for Project MyTestProject.  This shows just one Sprint.  On Page 404 there is a screen shot of viewing the Agile Project Hierarchy in the Work Plan.  This is for the same Work Plan.  In the Project Hierarchy there appears two Line Items with the same Name:  Sprint 1 (Lines 2 & 5 in the Work Plan).  Which Sprint 1 is represented on the Agile Project Timeline Tab?  It is assumed it is the highest level, though with two Tasks in the Hierarchy with the same Name, it is not completely clear.

[Answer] Assumtion is correct and it is agreed that the graphs need to avoid any confusion.

4.  Page 404 of the HP Solutions Integrations Guide for PPM 9.20:  The last statement on the page reads:  "The hierarchy information can also be used for further project health calculation."  How?  Which Health Calculations?  Does the accomplishment of the Sprint User Stories roll up to the Project Schedule Health?

[Answer] There is no such functionality in place right now. This is the anchor HP was wanting to use in future development to incorporate all the Agile Project information to the Master Project information.  It was best not to expose these words to PPM customers at this time to avoid confusion.

5.  Page 79 of the PPM 9.21 Release Notes:  The provision of a new Chart is listed.  One is the "Theme Status."  In Agile Management, how is a Theme defined and why is it important to a Project Manager?

[Answer] From Agile practice, a Theme is a Top-Level Objective that may span Projects and Products. Themes may be broken down into Sub-Themes, which are more likely to be Product specific. At its' most granular form, Themes can be used at both Program and Project Level to drive strategic alignment and communicate a clear direction. Generally one release can have limited themes. Knowing the theme status can help project managers knows the progress of the release content.

“HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.”
Labels (1)
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.