Upload
others
View
16
Download
0
Embed Size (px)
Citation preview
COMPLETE STANDARDIZATION OF HP ALM
WWW.ASSURE.NET
Founded in 2006
International software company with offices worldwide
HP technology provider and partner
Deployed in the world’s largest HP ALM environments
ABOUT ASSURE
WHAT DO WE DO
Project
Management
Release /
Requirements
Management
SW
Development
QA and
Testing IT Operations
Tools
Knowhow Process
Expertise Analytics
WHY STANDARDIZE?
Successfully run large HP ALM instances with limited staff
Implement Enterprise Cross Project reporting and Integrations
Ability to centralize and save $$ by implementing automated central reporting platform
Up to 20% increase in QA efficiency
Assure provides a proven and reliable solution for complete HP ALM standardization Helping HP QC & ALM customers since 2006 We understand the challenges We know what it takes We have expertise and the tools to make it happen
Our largest customer to date had 1200 active projects – now all standardized
ASSURE AND STANDARDIZATION
Customer has two ALM instances
~200 ALM projects
4 Business units working differently
General ‘Project Template’
Projects can and are individually customized
Multiple integrations
Several groups create their own reports
How to Standardize?!?!
TYPICAL SCENARIO
Analyzing the scope
Agree on a ‘golden template’
Complex dependencies
Technical challenges – how to go about it
Availability of required knowledge
Too big task, limited resources
How to explain management the benefits
CHALLENGES
HP ALM does not help standardize
Not the Fields
Not the Data
HP IT – one of the worlds largest ALM installations is using Assure’s products!
CHALLENGES CONT.
Analysis Create Project
Template(s) Standardize
Projects Maintain and
Control Change
HIGH LEVEL STANDARDIZATION PROCESS
PROJECT TEMPLATES
A Template project is an ALM Project with additional special functionality:
Cross-Project Customization
”Regular” projects are linked to the Template
Changes are pushed from the Template to the linked projects
Template
Project 1 Project 2 Project 3
Template
Project A Project B Project C
Software Version
Software Version Software Version Software Build
Software Version
Software Version
A Field, Software
Version is introduced in
the template
To a new project, the
field is deployed
perfectly
If a Field already exists
with the same name,
customization fails
If a Field exists with different name, the field is
duplicated. Data has to be moved and
manipulated
SO – WHAT IS THE PROBLEM?!
ASSURE PROJECT HARMONIZER
Map existing fields to template fields
Solves the problem of conflicting ALM project fields
Turnkey solution
Easy to use
Field-proven with thousands of projects
HP Certified
Template Project
Defect Status List
• Open
• Closed
• Deferred
WHAT ABOUT THE DATA??
Defect Status List
• Open
• Closed
• Postponed
Defect Status List
• Open
• Closed
• Deferred
Defect ID Status
1 Open
2 Postponed
3 Postponed
ASSURE DATA STANDARDIZER
Data Integrity issues are often noted:
Cross project reports are implemented
Sharing test assets across projects
Integrations that involve multiple ALM projects
Causes:
Processes change over time: list values change over time
Business units work differently
Merges and Aquisitions
Errors
ASSURE DATA STANDARDIZER
Locate and fix inconsistent data in your HP ALM projects
Maintain high data quality
Instant Assessment of your Data Quality
Reuse tasks across projects to save time
Leverage your Project Staff / SME’s
HP Certified
STAYING STANDARDIZED
Use HP ALM Templates
Gain Full control over project customizations
Push customizations from the template with one click
Enforce standard Project Lists and Fields, User Groups, Requirement Types
Assure Data Standardizer
Keep data quality in top shape
ASSURE PROJECT HARMONIZER VS. ’MANUAL’ HARMONIZATION
’Manual’ Harmonization Assure Project Harmonizer
Development Effort A solution has to be developed.
Expertise is needed and knowledge has to be
acquired. A lot of investigation, trial & error.
Turnkey software product with support and
maintenance.
Risk Risky. A lot of testing needed and many ALM
projects will be corrupted in the process
Proven technology. Certified and recommended
by HP.
Impact handling
(Cover all aspects of database modifications)
Not handling all the aspects of database
changes. Project integrity not maintained, work
has to be redone by users (reports, favorites,
history, filters, rules, permissions and more)
Maintains everything related to modified fields
intact. Retains data integrity and consistency of
the project.
Usability Usually scripts or excel sheets, not user friendly.
Time consuming.
Extremely user friendly & easy to use UI,
designed by usability specialists to be as efficient
as possible.
Project Downtime during database conversion Significant project downtime (hours). Users
cannot use the project during this time
Optimized with the help of HP R&D and
database experts to minimize project downtime.
Benchmark document is available.
Harmonization Process Trial & Error. Best guess. Surprises likely to
arise, resulting in costly delays.
Clear documentation of the process including
methodology, considerations, tasks & roles.
Based on experience and success.
Total Estimated Time (for 200 Projects –
medium level of customization)
50 weeks 6 weeks
Assure HP ALM Project Harmonizer and Standardizer
http://assure.net/video-harmonizer/
http://assure.net/datastandardizer/
Assure TotalView videos
http://assure.net/what-is-totalview/
http://assure.net/video-assure-totalview/
Assure blog:
http://assure.net/blog/
MORE MATERIAL IS AVAILABLE ON OUR WEB SITE