1. Using HP Quality Center 10.0 Premier
to introduce processes and control into
existing testing
Michael Deady, CPC
Test Tool Administrator
JC Penney Inc.
1 ©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

2. Introduction The Implementation Plan
 About JCPenney Inc  Plan, Train, Design and Development
 JCPenney Application Testing Center In Closing
 Business Problem  Things to Know
Quality Center 10 Premier  Hints and Tips
 ATC & Quality Center  Other Premier advantages
 Decision Process  Summary
2 ©2010 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

3. About JCPenney
Department Store Retailer with 1,110
stores
Locations in United States and Puerto
Rico
Largest Apparel & Home Furnishing site
on the internet (JCP.COM)
Stores also provide styling salon, optical,
portrait photography, and custom
decorating services
Corporate Headquarters: Plano, Texas
Employees: 150,000
3

4. JCPenney Application Testing Center
The Application Testing Center (ATC) was founded to create a Center
of Excellence (COE) for JCPenney I.T. division by providing the
Application Testing Teams, the best tools, services, and resources
to improve the quality and consistency of application testing
across JCPenney.
• What we Provide JCP I.T.
• Processes
• Services
• Test automation engineers
• Performance engineers
• Training
• Templates
• Forum for best practices sharing
• Other Benefits
• Centralized administration
• Framework creation
• Vendor management
• Aggregated purchase
4

5. Test Management JCP Business Problem
Pitfalls: Huddles:
• After consolidating Quality • Most of the QC projects were still
Center into a single environment, active
we had over 250 projects, several • Admin permissions were very loose
housing 10 defects or less. ??? • Most Admin personnel had no formal
• Each Quality Center project was training
unique, and highly customized • The level of understanding of the tool
• Testing groups were very was limited
isolated and had very little • No environment management
interaction with peers or staff • An understanding of the tools
• High use of Excel upload • Defect vs. Test Management
processes
• A lot of manual rework causing
user frustration with the tools
• No training around the tools
• Contractor-driven testing
5

6. JCPenney Application Testing Teams Top
Ten (Why HP-QCP)
1. Keep It Simple or K.I.S. - A.T.C.
2. Sharing information across projects and development tools
3. The capability goes back in time or compares historic
information (Version Control)
4. The ability to customize an individual HP Quality Center
project to better fit the Development project, while
maintaining a level of uniformity.
5. Consistent KPI's across projects
6. Use templates and build a process.
7. Reduce the level of duplication and redundancy
8. Customize control capability
9. The ability to test in any environment (Production, Test, and
Development) at the same time -- (baselines)
10.The capability to manage every facet of QDLC and/or SDLC
What ATT’s want in a (Test) Management System?
6

7. Relation between ATC & Quality Center
In 2008 ATC selected HP’s Quality Center as the enterprise solution for test
management to ensure continuity and consistency across JC Penney.
ATC was tasked with aiding our IT and business partners in the
conversion and consolidation of all leagues of defect tracking and
testing repository systems and/or test applications into the Approved
Test Management system.
ATC has been so successful at integration of the testing tools into the
approved testing process and methodology that if you login into the
newer QC projects you are more than likely following ATC’s Processes.
“Quality Center acts as the Backbone to our
Methodology”
7

8. Decision Process
Why Quality Center 10.0?
JCP needed the ability version artifacts and establish points reference
Why Quality Center Premier
• Structure and best practices into the environments
that could not afford the cost or the time to
implement.
• The capability to share information across several
projects to eliminate the duplication of artifacts and
reduce test development time (Test Case,
Requirements, Resources, etc.)
ATC Objectives
• Upgrade legacy Quality Center projects
• Lower maintenance model for 2010
• To better align the Quality Center projects with the
AUT
• Reduce the amount of training across JCPenney
8

9. Quality Center 10.0 Premier’s Point of
Interest for ATC
• The ability to enforce processes and methodology
• The capability to change the process, fields or workflow
without negatively impacting the project
• The ease of moving information from one project to
another
• The ability to introduce change with speed and accuracy
• The capacity to share and control the flow of data across
projects
• Built-in cross project reporting
• Real-time dashboard
• The new friendly dashboard user interface
• Etc..
9

10. The Implementation Plan
The plan was straightforward
• Create the template which
incorporated the ATC
methodology and processes
• Then attract the Projects to
the new template by enticing
them with QC Premier’s new
functionality
10

11. The Road Show
Brown Bags including Tool Overview by HP
and Open Deep Dive training
One on One Meeting with the
Application Testing Team
Demos
Open Brainstorming Forums
Meet with the business user
11

12. Step 1: Define what is a Quality Center
Project
QC Project
• Is the logical collection of data relevant to a set of applications that
interacts to serve a business purpose. This data may refer to
hardware, software, requirements, tests, defects, and/or any other
artifacts used in the validation of the system. The Quality Center
project documents the complete lifecycle of the application or system
from concept to decommission.
Application
• A program that gives a computer instructions that provide the user
with tools to accomplish a task
System
• A group of interacting, interrelated, or interdependent elements
forming a complex whole.
12

13. Step 1A: _ ____ Cross-Project
___ HP’s QC ______ ____________
Customization Overview
_______
Linking the Customizing the Verifying Cross Applying
Creating a
Template to Template Project Customization to
Template Project
Projects Project Customization Linked Projects
Creating a Template Project
Linking the Template to Projects
Customizing the Template Project
Verifying Cross-Project Customization
Applying Customization to Linked Projects
13 Quality Center Help File 2009 Hewlett-Packard Development Company, L.P.

14. Step 1B: HP’s QC Cross Project
Customization Examples
Set a standard for working with defects
Enable consistent reporting by managers.
Create corporate Policies and Processes for
separate sectors of an organization
14

15. Step 2: Training and Planning
• Spend some time on understanding all the
new features
• Warning: the template tool has a large
foot print on the projects and access
should be controlled
• Take note of the what the template will or will
not change at the project level
• Create a template that reflects your workflow,
and can generate the required information for
reporting metrics
• Tools and Skills
• A understanding of Quality Center
project backend, especially workflow
• Quality Center 10.0 Premier
• A well documented testing process
• Access to both SA and TD
• An understanding of roles and
responsibilities within Quality Center
15

16. Step 3: Design and Development
• Development of Template Workflow
• Template Entity vs. Local Entity
• Levels of Access
• Version Control
• Template Reports
• Presentation Layers
16

17. Process using QC Premier Template
(Workflow)
Set standards
Key
STATUS
DISPOSITION
REPORTING OPEN NOT REPORTED
DECISION PENDING
NEW REVIEW
DOCUMENTATIO
N FOR
WORKAROUNDS
Clarification
IS DEFECT
VALID
No REJECTED
YES
A DEFECT/
ENHANCEMENT CAN USER ERROR
PENDING
ENTER DEFERRED No OPEN ASSIGNMENT
STATUS FROM ANY
POINT ALONG THE DUPLICATE
TEMPORARY
LIFECYCLE AS THIS WORKAROUND
STATUS USUALLY
REQUIRES A RISK
Create unique policies ANALYSIS EXTERNAL ISSUE
ACCEPT
DEFECT? INVALID
REQUIREMENTS
FUTURE RESEARCHING
ENHANCEMENT DEFERRED
YES
SENT TO INVALID TEST
VENDOR
ASSIGNED WAITING FOR
VENDOR
WORKING
Enable consistent reporting by
READY FOR
FIXED QA TEST
REPORTING
CLOSED
managers.
YES
DEFECT RETEST
SUCCESSFULLY? CLOSED
NO
RETESTED
PENDING SUCCESSFULLY
ASSIGNMENT REOPEN
PERMANENT
WORKAROUND
Technical Customer Operations
17
Impact Impact Impact

18. Process using QC Premier Template
(Entities)
• Project Entities (Shared) link to
customize system fields and
create user-defined fields.
18

19. What Templates update
Template Update
Task Local update Only
Sharing
User Properties
Project Users
Groups
Module Access
Project Entities
Requirement Types
Risk-Based Quality Management.
Project Lists
Auto mail
Alert Rules
Workflow Template With Calls only
Cross Project Customization Linked Projects Linked Template
19

20. Step 3: Implementation
To add a project to a template you need to be
in the Site Admin screen
To push changes to the
projects you need
to be in the Project
template
customization
screen
20

21. Template Verification
Verification Report
Provides results of verification for the
linked project.
Applied Customization Report
Provides results of template
customization applied to the linked
project.
21

22. Detailed Reporting
Result Verification
category Report
Successful The change can be
successfully
applied to the
linked project.
Warning The change can be
applied to the
linked project, but
may result in data
loss.
Failure The change cannot
be applied to the
linked project.
22

23. Project Level Customization
Cross-Project Customization
• Linked Template page.
• View details about template customization
• Send email to the template administrator
• Check for conflicts between customization in the
project and customization in the template project
• Request to block template customization updates
23

24. Project Update (Pushing)
• Updates pushed while
people logon
• Detail reporting for
users
• Email Notification
• Built-in Process
• Update one or all of the
projects
• Update time stamp
• Contact Help
• Easy to follow
instructions
24

25. Other Premier Advantages
Dashboard allows the different Application Testing Teams to
consolidate reporting
Defect Synchronizer allows users to send defects across projects
and external applications (JIRA)
Requirements sharing has helped ATC make the business case that
the development and management of business requirements
should be managed in Quality Center
Sharing test cases and business components development, track,
and execute across several projects reducing redundancy and
duplication
Resource sharing has greatly added to the automation of
applications by drawing on existing functional libraries, object
repositories, and data
25

26. Quality Center Synchronizer
The Synchronizer enables you to synchronize data between Quality
Center and other applications, or between two Quality Center
projects.
QC Project
C
Integrity Checks
QC Project QC Project
B D
Incremental Synchronizations
QC Project Quality QC Project
A Center E
Full Synchronizations Synchronizer
Working with Quality Center Version Control QC Project
QC Project
H F
QC Project
JCP
26

27. QC 10 Premier Baseline (sharing across
SDLC)
Cycle End to End
Cycle System
Cycle Functional QC Project A
d
d
En
En
Sy
Sy
s
s
to
to
te
te
d
d
m
m
En
En
Cycle Unit
Release 1.1
Cycle UAT
Baseline Baseline
Project A
te & IT
te & IT
Release 1.0 Project A
N
N
n
n
U
U
U
U
io
io
AT
AT
at
at
gr
gr
Develop Update Develop Update
In
In
Share Project A Share Project B Share Project AShare Project B
Develop Update Develop Update Develop Update
U & tion
U
U & tion
N
N
N
In
In
In
AT
AT
AT
IT
IT
IT
& atio
te
te
te
U
U
U
gr
gr
gr
Baseline Baseline Baseline
a
a
Project B Project B Project B
n
Release 3.10
En
En
En
Release
m
m
m
d
d
d
te
te
te
to
to
to
3.11
s
s
s
Release
Sy
Sy
Sy
En
En
En
4.00
d
d
d
27 QC Project B

28. Quality Center as part of the SDLC Process
Reduce rework and
duplication
Version control
documentation
Easy to modify existing
documentation
Single repository
Reduce training costs
Easily customized
Sharing of documents
Incorporated technical and
functional documents
Traceability
28

29. Things to Know
Key Note: Purge all local workflow before adding project to template -
this may cause errors later
Module access is handled at the Project Level
Remember that sharing defects uses the Quality Center
Synchronizer.
I recommend that you standup the Synchronizer on independent
hardware to avoid any issues.
Sharing information from two projects relies on base lining
functionality
(Migration) uses the QC Synchronizer to move Defects from older
projects to updated projects using QC 10 Templates
Backup code manually before making changes to the Template
project
Limit your support for Excel Add-in
29

30. Tricks and Tips
Plan a phased rollout of all the new functionality
This can be overwhelming for the local project administrator and
can cause training issues as well.
Uses Brown Bags or short training sessions
Introduce the new functionality (what’s new)
Keep your Template Simple
The number of templates can also be an issue
Follow best practices
When coding workflow and document everything
Try to keep information and defect sharing inside one template
Create a process flow before attempting to share information
Defects, Requirements, Resources, Test cases
30

31. Introducing Processes and Control Into Existing
Testing Environments Using HP Quality Center 10.0
Premier
31

32. 32