1. HP Quality Center 10 Hottest Features and Project Harmonization
Olli Laiho
Assure Oy
VIVIT TQA SIG Leader
Release quality on time

2. Release quality on time

3. Agenda Introduction HP Quality Center 10 in Brief
Hottest Features of HP Quality Center 10
Asset Sharing
Process Enablement
Quality Center Project Harmonization
The Challenge
What is Harmonization?
Benefits of Harmonization
Lessons Learned
10:45-11:00 Q&A session with questions from online 3

4. HP Quality Center 10 in Brief
Released January 2009, Patch 3 is out
Includes many new innovations
Three editions: Starter, Enterprise and Premier
Supports the ‘Quality Center of Excellence’ concept
Big benefits for large corporate-wide installations
For an exhaustive feature presentation of HP Quality Center 10, check out HP’s webinar ”Taking Quality Management to a New Level” or contact your HP representative
Direct all pricing discussion to HP
Release quality on time

5. Libraries and Baselines – Enterprise and Premier
Which HP Quality Center 10 edition includes the features mentioned in this presentation?
Libraries and Baselines – Enterprise and Premier
Asset Sharing – Premier
Process Enablement - Premier
Release quality on time

6. Libraries and Baselines
Enterprise & Premier
Libraries and Baselines
Located in the Management module
Features ”Library” and ”Baseline” objects
Makes it possible to create a comparison point (=Baseline) from Test Cases ,Test Resources and Requirements, based on folders
Test Sets can be pinned to a specific Baseline
Release quality on time

7. Asset Sharing Projects can share Baselines
Premier
Asset Sharing
Projects can share Baselines
Changes can be compared against a Baseline ja if necessary, update the test cases from a newer baseline
Enables:
Publishing and Sharing of Test Assets throughout the organization
Change Management
Keeping folder structures under control
Reduced clutter in tree views

8. Library Illustration Library Test Plan
Premier
Illustration
Baseline is imported to another project
Project A
A Baseline is created from Requirements or Test Plan folders
Project B
Library
Library
Baseline 1
Folders, Tests and Requirements are copied to Project B automatically
Requirement Folder
Test Plan Folder 1
Test Plan Folder 2
Baseline 1
Test Plan
Test Plan Folder 1
Test Plan Folder 2 8

9. Library Illustration Library Test Plan Changes are compared Project A
Premier
Illustration
Changes are compared
Project A
Project B
New Baseline is created
Library
Library
Baseline 1
Baseline 2
Baseline is imported and changes synced
Something is updated in Project A
Baseline 2
Requirement Folder
Test Plan
Test Plan Folder 1
Test Plan Folder 1
Test Plan Folder 2
Test Plan Folder 2 9

10. Libraries and Baselines, Asset Sharing
Best Practices
Define the process for Baselines
When to take a Baseline
Who shall be allowed to take Baselines
Ensure your server capacity
With each Baseline, the amount of data grows
Backup data is increased
Agree on a naming convention for Baselines
Project_Milestone_TestArea
Release quality on time

11. Process enablement Details
Premier
Details
Create template projects and assigns template administrators
Select projects to link to a template in Site Administration.
Customize a template project
Verify a project before you apply changes
Apply the customization to the linked projects
Manage quality processes across initiatives
SAP Phase 1
Process
SAP Phase 2
Key benefits
Ensure teams across organization follow best practices
Report at enterprise release level with common set of metrics
Lower administrative costs to maintain best practices
SAP Rollout 11 11 11 11
14 November November 2018
14 November November 2018
14 November November 2018 11

12. Process Enablement Template Project A Project B Project C
Premier
Process Enablement
A Template project is created.
A new field, Software Version is introduced in the Template
Template
Software Version
Project A
Project B
Project C
Software Version
Software Version
Software Version
Projects are created and linked to the Template
Field is added to Linked Projects through Cross-Customization 12

13. Challenges QC 10 brings Significant new features Decide how to deploy
Which processes are affected?
Educate the organization
All of the features will be available to all users by default
Working with existing projects
Which changes have to be done to existing projects?
Will existing projects work with all new features?

14. Quality Center Project Harmonization
Release quality on time

15. The Challenge
HP Quality Center (QC) projects can be customized to suit different kind of testing needs and testing processes
Each QC Project has it's own Database and since QC projects can be customized independently of each other, this will often lead to the situation where projects have different structures in the database.
Technical: The same database column in different QC projects can contain different types of data (CLOB vs VARCHAR, or Number vs. Date) that are incompatible with each other
Projects with different structures present challenges in the following areas:
Sharing and Copying data between projects
Applying Integrations and Reporting solutions
Workflow customizations have to be tailored for each project
No common 'testing language' and processes between projects
High maintenance
Release quality on time

16. “Template” Typical situation Project 1 Project 1 Project 2 Project 2
Process Police!
Project 3
Rogue projects from other servers, from company aqcuisitions etc.
Release quality on time

17. Lack of testing terminology standards between projects
Project A
Software Version
Project B
Software Build
Project C
Release
Release quality on time

18. Cross-Project Reporting
Change the labels
Integrations
Cross-Project Reporting
Software Version
BG_USER_10
BG_USER_22
BG_USER_03
Software Version
Software Version
Software Build
Software Version
Release
Software Version
Project B
Project C
Project A
Release quality on time

19. What and Why of Project Harmonization
Project Harmonization is the process of defining Project Templates, and converting the data structure of existing QC projects to be harmonized - to be compatible - with the pre-defined Project Templates
Project Harmonization can be performed on any HP Quality Center version
Why harmonize?
Projects with different structures present challenges in the following areas:
Sharing and Copying data between projects
Applying Integrations and Reporting solutions
Workflow customizations have to be tailored for each project
No common 'testing language' and processes between projects
High maintenance

20. Setting the scope for Harmonization
Fields
Name, Label, Type, Length, Verify, Required, History, List Name (,List Items)
User Groups
Name, Properties
Requirement Types
Workflow Code
Reports and Graphs
Release quality on time

21. Key Roles in a Harmonization Project
Responsible for the way Quality Center is used within an organization or company
Coordinates changes to Quality Center projects and Templates
Defines Project Templates
Process Owner
Responsible for managing one or more Quality Center projects
Knows the project thoroughly
Project Owner
Responsible for QC installation and maintenance
Server Administrator
Technical Owner
Release quality on time

22. Process of Harmonization
Analyse current templates, processes and ways of working
Gather best practices
Current state analysis
Process Owners design new templates based on best practices, standards
Implement the Templates in QC
Document the Templates
Establish new Templates
Project Owners create a ”map” which connects their project with the new template
Mappings should be reviewed by a Process Owner
Create Mapping
Technical Owners implement the changes to the QC database
Educate the users on the changes
Implementation
Release quality on time

23. Template Project Mapping fields TS_TEMPLATE_01 | Software Build
TS_USER_01 | Release number
TS_TEMPLATE_02 | Release
TS_USER_02 | Software ID
TS_TEMPLATE_03 | Test Phase
TS_USER_03 | Approver
TS_TEMPLATE_04 | Approver
Release quality on time

24. Project Harmonization and QC 10
Doesn’t QC 10 Process Enablement solve this problem ?
It enables you to create new projects based on a template, and manage changes to them
Fields
User groups
Workflow
Lists
Requirement Types

25. Process Enablement – the Challenge
Template
A Field, Software Version
is introduced in the template
Software Version
Software Version
Project A
Project B
Project C
Software Version
Software Version
Software Build
Software Version
To an empty project, the cross-customization will go through
If a Field already exists with the same name, customization fails
If a Field exists with different name, the field is duplicated

26. What you need in order to do Harmonization
Project Manager
Template Owners / Process Owners
QC Project Administrators
Commitment
Timeframe planning
In-depth knowledge of QC concepts
Tools created by developers with in-depth knowledge of:
QC Database architecture
QC API
Service Break
Training and communication
Release quality on time

27. Project Harmonization Benefits
When QC projects are harmonized it means that projects are compatible and thus the following can be easily achieved:
Common Reporting on all projects
Common integrations can be used
Same 'testing language' and processes across the organization
Same Customizations can be used in all projects
Sharing and copying of test assets is possible and easy
QC 10 new features unleashed for existing projects
Quality Center as the platform for Quality Center of Excellence

28. QC 10 Process Enablement with harmonization
SAP Rollout template
SAP Rollout Project 1
SAP Rollout Project 2
SAP Rollout Project 3
Instead of having a couple of new projects linked to a Template...
Primary Template
SAP Template
Agile Template
Harmonization enables all of your projects to be linked to Templates
Release quality on time

29. Lessons learned from past experiences with Harmonization
Run harmonization as a real project – it is not a small task
Use this opportunity to significantly improve your testing processes in QC
Get commitment from all parties involved
Communicate the benefits and execution plan
Train the users on the new processes
Don't allow TDAdmin rights for project users
Avoid making project specific changes
Maintain a clear process for handling template changes
Version your template and know the differences between template versions
Centralize your organization’s expertise and run HP QC as a Quality Center of Excellence

30. For more information on the topics
Visit Olli at the Assure booth (#140, next to the Smoothie Station) in Las Vegas HP Software Universe 2009
See Kaiser Permanente’s presentation from 2008 HPSUF ”Quality Processes and Workflows”
Beteoblog.com ” HP Quality Center 10 from a Test Manager’s Perspective”
Visit the VIVIT booth (#509) in Las Vegas HP Software Universe 2009
Release quality on time

31. Thank you!
Release quality on time

32. Q&A
Release quality on time