Embed Size (px)
Citation preview
HPE ALM STANDARDIZATION WEBINAR8TH DEC 2016
Duration: 45min + Q&A
Use the Questions box in GoToWebinar panel
We will answer as many as possible
After the webinar, we will share:
The presentation material
A video recording of the webinar
A survey regarding standardization is launched after the webinar
Please take a moment to fill it out
PRACTICALITIES
HPE ALM STANDARDIZATION WEBINAR
Software development lifecycle specialist
Strong experience in HPE ALM standardization projects
HPE ALM system administrator & developer
Partner at Assure for 10 years
Projects in the US, Asia and Europe
TUOMAS LEPPILAMPI
WEBINAR PRESENTERS
Global of Head Sales
20 years working in IT (Testing and BI)
Industry experience in Financial Services and Energy
Previously worked in Global roles in software and services
Has been a thought leader providing inputs to Gartner on various sectors
STEVE GOOD
Our mission is to enable our clients to have insights into what is going on across the IT landscape
Flagship product concentrating on advanced analytics: Assure Totalview
Consistent data comes from standardization using Assure Standardization Suite
We provide the tools that drive an optimized BI solution in testing
ABOUT ASSUREHPE ALM STANDARDIZATION
ASSURE CUSTOMERSABOUT ASSURE
Financial Technology Telecom / Media HLS / Other
Standardization cornerstones
Process story
Enterprise ALM design
Plan the implementation project
Standardization in practice
Continuous data integrity
Benefits of standardization
Insights from the field
Future!
Q&A
WEBINAR CONTENTSHPE ALM STANDARDIZATION
CORNERSTONESHPE ALM STANDARDIZATION
Business
Rules
HPE ALM
Template
Metrics &
Reporting
Leverage the functions and capabilities of HPE ALM templates and asset sharing
ALM Usage Model needs to support the business rules and processes in your company
Form an ongoing relationship between your metrics & reporting team and ALM user community
The goal is to drive the
collaboration of the actors
in ALM area
WILD WEST VS
ENTERPRISE TEMPLATE
HPE ALM STANDARDIZATION
Before
Difficulties in cross-project reporting lead to bad visibility in release readiness and product quality
Without unified terminology, comparing projects efficiency requires manual work
Induction of testing specialists to new projects takes more time
Maintenance of ALM environment is cumbersome
Overlapping customization & development effort
After
Organization wide reporting provides insight into company performance in product development
Unified terminology provides a common language understood by all actors
TCoE functions smoothly when specialists can ‘hit the ground running’ when moving into new projects
Administration & maintenance can be done with a clear set of rules
In-house customized functions can be leveraged in any ALM project
Top-down approach
Management wants a consistent way to report across the ALM landscape
What are the decisions that are supported with a standardized usage model?
Identify reports and metrics needed in management level
Regulations and compliance – how to make sure requirements are met?
PLANNING ENTERPRISE ALMHPE ALM STANDARDIZATION
Bottom-up approach
Ensure best possible usability for end-users
Retain a flexible working environment
Investigate the variety of project types and their individual needs
Support customizations and project specific configurations
HOW ENTERPRISE ALM IS DEFINEDHPE ALM STANDARDIZATION
HPE ALM Enterprise Template
Data fields List values Permission groups Status transition rules Business rules support
Provides the enterprise configuration
Ensures that all data needed for company analytics is collected
Provides support for business rules & regulatory compliance
<Digital Bank> Virtual Template
Preconfigured empty project used for basis of live project creation
Configurations specific to the digital bank user community
Enforced by process awareness
<ATM Testing> Virtual Template
A base project configuration for another business line
Additional focus on testing software on physical machines
Configurations in <Digital Bank> not relevant to user group needs
<DB> ALM Project 1
Project specific fields,
values, groups and
customizations
<DB> ALM Project 2…n
Project specific fields,
values, groups and
customizations
<ATM> Agile Project
Configuration support for
agile release process
<ATM> Waterfall Project
Configuration support for
traditional release process
Metrics & reporting User stories
Pro
ject to
po
log
y
SG
Admin
GO
VE
RN
AN
CE
Process initiatives
Current state analysis should be done from two aspects:
Technical analysis with database queries and analysis tools
Interviews of user community groups with highly customized ALM project configuration
Best practices from current projects should be leveraged in the enterprise template
Detailed documentation of the template configuration should be done in two ways:
Technical configuration documented for administrators and developers
Practical documentation as presentations and Word documents for end user communities
Mapping from existing fields and data values done in collaboration with the end users
End user communities should have clear responsibilities during and after standardization project
A recognized leader of the ALM Usage Model should actively drive the change
FROM WILD WEST TO
ENTERPRISE TEMPLATE
HPE ALM STANDARDIZATION
STANDARDIZATION IN PRACTICEHPE ALM STANDARDIZATION
Analyze current situation
Enterprise
configuration
Data integrity
quality index
User stories
from community
Prepare the usage model
Template
readiness
Usage process
definition
Alignment to
metrics
Map existing to new
Fields mapped
Enterprise
values mapped
User roles
Custom
workflow scripts
Execute standardization
Database
changes
Implement ALM
template
Support the
community
Assure HPE ALM project analysis process for investigating current situation
Assure Project Harmonizer for mapping existing data fields into template fields
Assure Data Standardizer for scrubbing the data within list fields to ensure data integrity
Contact [email protected] to arrange a demo of the products
ASSURE STANDARDIZATION SUITEHPE ALM STANDARDIZATION
HOW TO MAINTAIN A “STANDARDIZED” ENVIRONMENT
HPE ALM STANDARDIZATION
Best practices
Define clear policies in ALM usage and data collection
Provide a clear feedback channel for end user communities
Organize periodical workshops to gather and review user stories
Assign clear roles for data ownership in enterprise level and project level
Support the culture of standardization
Most standardization projects have been driven by the TCoE and metrics initiatives
Resistance can often be expected from the business users
Change management in both technical and cultural area is key
Metrics development should happen in parallel with the standardization activity
Executive support for the project is essential
Business user commitment has to be secured to the very end of the project
Standardization projects have often challenges in keeping all business lines within the standardization scope
‘Last minute opt-out’
Delays due to approval needs
Crucial to clearly communicate end user impact
Assure Standardization Suite is the key enabler of any successful standardization project
INSIGHTS FROM THE FIELDHPE ALM STANDARDIZATION
BENEFITS OF STANDARDIZATIONHPE ALM STANDARDIZATION
Clear standards, clear freedoms
Company wide
reporting
Better control for project
admins
Dynamic custom
feature sets
Methodology transitions (Agile etc.)
Single-click template updates
Lower maintenance
effort
HPE ALM Octane to offer a more development –oriented management platform with testing capabilities
HPE ALM.NET to cover existing user base and to integrate with Octane
User communities around DevOps, testing and analytics continue to revolve, solve and evolve
“Everything will be code” – In near future, all entities will have a strict format of description
Automation readiness!
Avoiding vague descriptions in Requirements, Tests and Defects
Re-usability for regression, integration testing, variants…
Key: Understanding the business goals behind our initiatives
Start your journey into advanced analytics with Assure Totalview
FUTURE…HPE ALM STANDARDIZATION
THANK YOUCONTACT: [email protected]
APPENDIXHPE ALM STANDARDIZATION
Feedback group nFeedback group n
PROJECT STRUCTUREHPE ALM STANDARDIZATION
Workshop 1
Releases &
Requirements
Workshop 2
Test Planning
& Execution
Workshop 3
Defects &
Issue Mgmt
Workshop 4
Usage Models
& Integrations
Steering Group:
Usage Model
1.0 Approval
Feedback group n
Upgrades,
updates, ideas
Current state analysis & documentation
Development of metrics & reporting initiatives
Rules from business, administration and methodologies
Ongoing development
Enterprise
template
deployed
Implement template
STANDARDIZATION SCOPEHPE ALM STANDARDIZATION
1st phase
2nd phase
3rd phase
Status System / App Release Severity
Environment Defect Category Test Level / Phase <Integrations>
Root Cause Analysis Risk Priority Platform
