MAXIMUS A OpsHub Customer Success Story. By: Manoj Juneja

Size: px

Start display at page:

Download "MAXIMUS A OpsHub Customer Success Story. By: Manoj Juneja"

Crystal Gilbert
10 years ago
Views:

1 MAXIMUS A OpsHub Customer Success Story By: Manoj Juneja

2 Agenda About MAXIMUS MAXIMUS Business Challenges The OpsHub Solution Benefits of a unified ALM Eco-system Lessons Learnt/Best Practices

3 MAXIMUS provides business process services to government health and human services agencies worldwide. Operates in: Reston, Virginia, United States (headquarters), United Kingdom, Australia, Canada and Saudi Arabia, with a total of 270 offices worldwide. Revenues: $1.1 Billion Employees: 8657

MAXIMUS A OpsHub Customer Success Story Business challenges Manual Data Entry and Multiple native ALM systems used for defect management, production problems and quality management Lack of

4 MAXIMUS A OpsHub Customer Success Story Business challenges Manual Data Entry and Multiple native ALM systems used for defect management, production problems and quality management Lack of traceability between different artifacts Solutions Unify ALM ecosystem with OpsHub. Integration enables cross-system traceability. Business value Faster and richer collaboration across teams End-to-end visibility Full traceability between different artifacts

5 MAXIMUS Business Challenges OpsHub Integration Manager Globally diverse team -spread geographically East and West coast of United States -50 people distributed team working on 10 different projects. -Team cross-project collaboration and consolidation issues.

6 MAXIMUS Business Challenges OpsHub Integration Manager Multiple disparate ALM systems being used for - Defect Management (Jira) - Quality management ( SmartBear ALMComplete) - Source in Subversion Manual data entry by development team into Microsoft Excel Fragmented Data not available in one single location

7 MAXIMUS Business Challenges OpsHub Integration Manager Lack of visibility and traceability across native ALM systems - Traceability lacking between test case failures and defect - Difficult for quality team to report defect to development team - Difficult to generate comprehensive status reports/views (due to lack of traceability)

8 The OpsHub Solution Unifying the ALM ecosystem Systems/Shared Entities at MAXIMUS ALMComplete Requirements, Test cases, Source Trace, defects JIRA Defects, Requirements Subversion Source Source traced to Jira Requirement or Defect OpsHub Integration Manager (OIM) Executive Team

9 Use Cases Overview Sync of defects between JIRA and ALMComplete Customized project mapping enables project consolidation Multiple projects in JIRA are mapped to single project in SmartBear ALMComplete Indirect mapping of check-ins of defects or requirements from Subversion Providing rich visibility to QA team on the source changes ALMComplete to ALMComplete integration to link issues of different entity types Requirements, test cases, releases (and agile tasks soon)

10 Defects Two modes Multiple Jira Projects Single QAComplete project Each project is a folder in QAComplete project One Jira Project One QAComplete Project

Code Change Traceability (Checkin) Check-in can be against (depending upon project) Jira Defect ID ALMComplete Defect ID ALMComplete Requirement ID Check-in s processed

11 Code Change Traceability (Checkin) Check-in can be against (depending upon project) Jira Defect ID ALMComplete Defect ID ALMComplete Requirement ID Check-in s processed to create proper traceability Against appropriate ALMComplete ticket Direct When ALMComplete ticket id specified Indirect Via Jira, when Jira ticket id specified in check-in

12 ALMComplete Issue Linking Use for linking issues based on field values Allows bulk upload with relationships Requirement Requirement Parent/Child link Requirement Release Release link Requirement Test case Test case traceability link Requirement Agile Task Traceability link Defect Release Release link

13 Benefits from Integration Better/Richer information available to teams Able to run holistic reports showing progress Rich in-context collaboration between teams Better traceability / visibility Lower waste End to end traceability Ability to use best of breed tools

14 Lessons Learnt

Think Unified Eco-System Integrated systems is a single unified system Common workflow and fields Build a common language across systems Status definitions Priority

15 Think Unified Eco-System Integrated systems is a single unified system Common workflow and fields Build a common language across systems Status definitions Priority definitions List of value fields Project/Release/Product/Component definitions Workflow functionality mis-matches Align administrators Changes need to be coordinated

16 Plan for System Evolution Design for Change Addition of new fields Addition of new values in a LOV field Addition of projects

17 Sync Server Functionality Functionality Functional richness Flexibility of System / extensibility framework Robustness Reliability framework Failure Management and Recovery System and Artifact support Types of systems and artifacts supported

18 Questions

OpsHub Integration Manager unifies your application. lifecycle management systems to create a single ALM

OpsHub Integration Manager unifies your application. lifecycle management systems to create a single ALM Integrate all of your ALM and customer support business systems in your heterogeneous ALM environment seamlessly to realize the benefits of synchronized collaboration, manageability, and visibility. Move