Markus von der HeidenMarkus von der Heiden HP PPM Best Practices – The Key to Success

03/17/2008 by Markus von der Heiden

For a promising start of HP PPM projects, there are important requirements to be complied with, rules to be observed and system configurations to be carried out, right from the beginning. In the following, the most essential best practices are listed, gathered from a large number of HP PPM projects.

 

General Requirements for the Configuration and Development of HP PPM Applications:

– Development guideline
The development guideline includes all standardized rules for the development process, the applied methods and all tools to be used. Additionally, the development guideline is used to document the experience made during the development phase.

– Glossary
In the glossary, terms and abbreviations used in the context of development are explained. It is a means of standardization of terms used in conjunction with the development of HP PPM projects.

– Role concept
The role concept defines the roles of the development team members. It rules communication, escalation and responsibilities.

– Development environment
All tools used in the process of development are defined here. The developers have to be familiar with the used devices and the connection parameters.

– Up-to-date patches and fixes
The newest patches and fixes must be installed on all devices used for development and subsequent testing. You will find the newest patches on HP’s PPM Patch download page (HP passport Account required).

– Best practices
We recommend to continuously compile and document best practices. They can be derived from the software producer and, above all, from own experience. The results can be incorporated into the development guideline.

 

Specific Requirements for the Configuration and Development of HP PPM Applications

– Installation and configuration
All necessary commercial software must be installed and configured on the system planned to be used for development according to the system manual.

– Testing the development platform
The development platform must be tested using the best practices provided by HP. The HP Quality Center offering automated tests may be a helpful support. It implies the advantage of re-use.

– Testing the SSH connection
Testing of the connections between the servers defined in the development environment is a must.

– Setup of the computers of the developers
The required development tools such as Eclipse, SQL Developer, WinSCP,… should be identically installed on the computers of all developers involved.

 

Required Authorizations – Special Configuration for Starting a Development Cycle with HP PPM

– User management
Implementing a security group comprising the members of the development department who are meant to be authorized to user management. Reference to an organizational unit facilitates the administration of this group.

– Developers
Implementing a security group comprising all members of the development department. Assignment of the required access authorizations to change request types, request header types, workflows and validations.

– Object owner
Implementing a security group with all members who become owners of objects.

– Package transport
Implementing a security group with all members who are in charge of the transport of the development packages from the development system to the test system.

Basic Settings – Special Configuration for Starting a Development Cycle with HP PPM

– Required environments
Setup of all necessary environments for all defined systems. Testing the connection to the environment checker.

– Validation with global parameters
By this measure, a globally applied parameter can dynamically be changed during development, all references being based on the up-to-date parameter. These parameter references are used in all objects. This avoids errors with the referencing of transported objects.

– Transport workflow
Definition of a workflow for the transport of the developed commercial software. This workflow maps the complete process of deploying the developed commercial software.

– Change management packages
Definition of a change management package which includes all developed objects of a version (labeling). This package is used as a medium of controlled transport of the developed packages.

 

 

Summary

These guidelines are an excerpt from the best practices compiled from many HP PPM projects (formerly Mercury ITG). They contain a rough overview of the experience and the insights gained from HP PPM configuration and development. If these basic requirements are met and the recommended rules are followed, the first step towards a successful HP PPM project is done.

Sphere: Related Content

No TweetBacks yet. (Be the first to Tweet this post)

6 Responses