In this slide deck from the on-demand webinar presented by strategic partners Tasktop and 321 Gang, you’ll learn how to connect ALM development tools across development teams to create an architecture for DevOps automation and build process models that connect the various stages of software delivery using RLIA-TE.
2. IBM’s Definition of DevOps
Accelerate
software delivery –
for faster time to value
Balance speed, cost,
quality and risk –
for increased
capacity to innovate
Reduce time to
customer feedback –
for improved
customer experience
‘In everything we all do, it's all about working in an agile way...
envisioning an outcome, prototyping, iterating, multi-disciplinary
teams... we do that in many parts of IBM today, but we're scaling
it at an enterprise level.’
- Ginni Rometty
Continuous
Customer
Feedback &
Optimization
Collaborative
Development
Continuous Release
and Deployment
Continuous
Monitoring
Continuous
Business Planning
Continuous
Testing
Operate Develop/
Test
Deploy
Steer
DevOps
Continuous
Feedback
4. Without Integration your
transformation will fail to deliver:
• $10M* per year of expected business
value
• Traceability from concept to cash
• IT infrastructure capable of supporting
transformation
• True end-to-end visibility for all
stakeholders
• Empowered and engaged teams
* 1,500 person delivery organisation
5. Manual (re)work is costing $10M/yr
Number of developers 1200
Number of testers 300
Total users 1500
Working hours per week 38
Minutes saved per user per week 100
Productivity increase 4.4%
Total direct delivery costs $225,000,000
Delivery value add factor 1
Additional value delivered (per year) $9,868,421
6. Annual cost of Fragmented integration
Manual (re)work - value lost $9,868,421
Traceability overhead $270,000
Tool upgrades/migrations $1,045,000
Traceability and compliance Exposed
Management Reporting Manual
Visibility Fragmented
Team engagement At Risk
Total costs $11,183,421
7. Major finance house
2 senior people full-time to map traceability
PPM
Development Tools
Testing tools
Deployment tools
Direct cost $270,000
End-to-end traceability
8. • Cornerstone of Agile or DevOps
transformation
• If you’re not fixing the bottleneck, you’re
wasting your time
• What if management reporting is
inaccurate/out of date?
• What about distributed/external delivery
teams?
• How much manual effort will this involve?
End-to-end visibility
9. • Reduced velocity
• Reduced morale
• Reduced value delivery
• Employee churn
• Disproportionate effect on 10x’ers
Consequences of lack of engagement
10. • Drives DevOps transformations across departments
• Streamlines Agile, SAFe and Bi-Modal practices
• Connects the software delivery value stream
• Ensures all tool combinations run -- all the time
• Embraces continuous change
• Powers your software lifecycle analytics
• Scales to support enterprise-wide transformation
An Integration Strategy
11. Brittle point-to-point
Requires developers
Does not scale
Architected to scale
Real-time lifecycle hub
Plug-and-play
Easy to scale
Email & spreadsheets
Manual, error prone
Does not scale
Email
12. RLIA-TE is your strategy
Protects against system outages
Synchronizations/updates queued until system is back online
Concurrent modification/Conflict resolution
Synchronization in real-time, on a field level, so conflicts are minimized
Conflict resolution policy set by administrator on a field level
Suppoerts schema or workflow changes
All changes put in a pending state until administrator updates schema or mapping
Detects corrupt system data
Integrity state checking that restores inconsistent data as needed
13. RLIA-Tasktop Platform
Spec Code Build Test Deploy
SAFe / Waterfall
APM
PPM
Project
RM
Requirement
Dev
User Story
QA
Defect
Sec
Vuln
ITSM
Ticket
Continuous Integration DevOps
Executives Business Analysts Project Managers Developers IT Operations Support Desk
ManagementLayerDeliveryLayer
Agile ITIL
14. Ensure DevOps is not constrained to a
subset of the SDLC
Avoids the mistake of enabling only local
optimization
Optimize the value stream for business value
delivery
Integrate for Continuous Engineering
PPM/Agile/ALM/SDLC/ITIL tools – through
synchronization
Multiple vendor DevOps tools – through event-
based automation
Agile team tools – through synchronization
Supports your process models
15. Rational Lifecycle Integration Adapters – cont.Rational Lifecycle Integration Adapters
RLIA v1.1.5
* Denotes a connector available in opt-out mode only.
16. Fragmented Integration Platform
Manual (re)work - value lost $9,868,421 $0
Traceability overhead $270,000 $11,000
Tool upgrades/migrations $1,045,000 $683,800
Traceability and compliance Exposed Covered
Management Reporting Manual Integrated
Visibility Fragmented Integrated
Team engagement At Risk 22% improved
Total costs $11,183,421 $694,800
Savings/Margin increase (per year) $10,488,621
The Business Case for Lifecycle
Integration
17. SLI Pattern Applies to Example
Dev QA
BA
Agile PM
QA
QA ..
ALM
QA
Agile 2
ITSM
Dev
QA 1
Dev ..
Dev 1
Agile 1
18. SLI Pattern Applies to Example
PMO
Agile 2
ITSM
Dev
QA
Agile 1
PMO
Dev
Agile
ITSMDev
20. Integration factory
3300 API tests in integration spec
500K API tests running per day
339 versions supported
9 years in the making
Model-based testing
Fully automated testing
Over 100 person years invested
World’s only knowledge base of
how tools can be connected, all
API/schema shortcomings
All integrations work. All the time.
21. of the
Fortune
10042
of the top
25 world
banks11
of the top
10 US
insurers5
of the top
6 health
plans3
Tools
Supported45
Tool Versions
Supported339
API Tests
Run per Day500K
Software
Lifecycle
Integration#1
Over
200,000
Sync Seats
Over 2,000,000
Mylyn/Dev Users
Vancouver HQ
Offices in Austin,
Boston, UK.
Founded 2007
Strategic
Partners29
23. DevOps Enterprise Summit 2015
Insurance
Tasktop connects the end-to-end
integrated model providing full
visibility across the value stream.
24. RLIA-TE Gateway Add-On
Events
SCM
APM
CI / CD
Test
Automation
SDLC
Tools
Database
• JIRA
• HP ALM/QC
• IBM RTC
• Microsoft TFS
• ServiceNow
• + 30 more
• Microsoft SQL
Server
• MySQL
• Oracle
• Git
• BitBucket
• Subversion
• New Relic
• AppDynamics
• Dynatrace
• Jenkins
• Ansible
• uDeploy
• Selenium
• HP UFT
Endpoints
Tasktop Sync Gateway Add-on provides one-way integration from events
triggered by DevOps automation systems into software lifecycle systems.… and many more!
25. DevOps is hard, failing is expensive
Lack of integration will:
Cost ~$10milion/year
Cokmpromise the success of SDLC process
initiatives e.g. Agile, SAFe, DevOps
Fragmented, services-based integration
solutions do not work
Partner with Tasktop and 321Gang for
integration success with RLIA-TE!
Summary
26. See Tasktop in Action: tasktop.com/demos
Contact us: tasktop.com/contact-us
Email us: info@tasktop.com
Next steps
@tasktop
facebook.com/tasktop
linkedin.com/company/tasktop-technologies
27. Traceability From Requirement Through Deployment
Requirement Test
Development
Work Item
Source Code
Change
Application
Binary
• Integrated toolset that automatically publishes data to the
different tools to help teams link related data items e.g.
requirement to test cases
• Suite of automated traceability reports to show breaks
• Guidance for teams on maintaining the traceability relationships in
each tool e.g. on linking Source Code commits to Work Items
How will the SDLC tools support traceability?
Enhancement
Request
Business Initiative
ITSM-Problem
Production
Change
Request
DevOps
29. Tasktop Sync Integrations – continued
Jama
2014.2, 2015.1, 2015.2, 2015.3, 2015.4, 2015.5; Current On
Demand Version
LeanKit Current On Demand Version
Microsoft Project Server 2013 SP1
Microsoft TFS 2012, 2013, 2015, 2015 SR 1, 2015 SR 2, 2015 SR3
Visual Studio Team Services
(VSO)
Current On Demand Version
Microsoft Test Manager 2012, 2013, 2015, 2015 SR 1, 2015 SR 2, 2015 SR3
Planview Enterprise 11.3
Polarion ALM
2014, 2015, 2015 SR1, 2015 SR2, 2015 SR3, 2016; Current On
Demand Version
Rally See CA Agile Central
SD Elements Supplied by Security Compass
Serena Business Manager 10.1.2, 10.1.3, 10.1.4, 10.1.5, 11.0, 11.0.1.1
Serena Dimensions RM 11.2, 12.1, 12.2, 12.3, 12.4
ServiceNow: ServiceDesk
PPM, SDLC
Eureka, Fuji, Geneva, Helsinki
Sparx EA 12.0, 12.1
Targetprocess Current On Demand Version
ThoughtWorks Mingle
13.1, 13.2, 13.3, 13.4, 14.1, 14.2, 15.1, 15.2, 16.1; Current On
Demand
Tricentis Tosca 8.3.0, 8.3 SP 1, 8.4, 9.0, 9.1, 9.2
VersionOne
Enterprise and Ultimate 13.2, 13.3, 14.0, 14.1, 14.2, 14.3, 15.0,
15.1, 15.2, 15.3, 2016, 2016.1; On Demand
WhiteHat WhiteHat Integration Server - provided by WhiteHat
Zendesk Current On Demand Version
Zephyr for JIRA Supported on JIRA 7 and On Demand
Tasktop Sync 4.7 Integrations
Atlassian JIRA
5, 5.1, 5.2, 6.0, 6.1, 6.2, 6.3, 6.4, 7.0, 7.1; Current On Demand
Version
Atlassian JIRA Service
Desk
6.1, 6.2, 6.3, 6.4, 7.0, 7.1; Current On Demand Version
Blueprint 6.1, 6.2, 6.3, 6.4; Current On Demand Version
BMC Remedy 8.1, 9.0, 9.1.00
Borland StarTeam 11, 12, 13
Bugzilla 5.0, 5.0.2, 5.0.3
CA Agile Central
2014.1, 2014.2, 2014.3, 2015.1, 2015.2; On Demand Enterprise
Version
CA Agile Planning Current On Demand Version
CA Harvest 12.5
CA PPM 13.2, 13.3, 14.1, 14.2, 14.3; Current On Demand Version
GitHub Issues Enterprise 11.10.343, 2.x and higher; and Current On Demand
HPE ALM 10, 11, 11.52, 12.01, 12.2, 12.5 , 12.53
HPE Quality Center 9.2, 10, 11, 11.52, 12.01, 12.2 , 12.5, 12.53
HPE PPM 9.3, 9.31, 9.32
IBM Bluemix Current On Demand
IBM Rational Team
Concert (RTC)
4.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2,
6.0, 6.0.1, 6.0.2
IBM Rational DOORS
NG (RRC)
4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2, 6.0,
6.0.1, 6.0.2 (opt-out mode only)
IBM Rational DOORS 9.1, 9.2, 9.3, 9.4, 9.5.2, 9.6, 9.6.1
IBM Requisite Pro 7.1, 7.1.2, 7.1.3, 7.1.4
IBM Rational Quality
Manager
4.0, 4.0.1, 4.0.2 , 4.0.3 ,4.0.4, 4.0.5, 4.0.6, 4.0.7, 5.0, 5.0.1, 5.0.2,
6.0. 6.0.1, 6.0.2
IBM Rational
ClearQuest
7.1.2, 8.0.0, 8.0.1
iRise Current On Demand Version
Vendor
Tools43 Versions
Supported303 API
tests/day500KStrategic
Partners27
30. Quick Start Enablement
• Organizations with a point to point integration need
• In-house ownership or responsibility of ALM software and hardware infrastructure
• Dedicated integration admins (Certified Sync Admins)
• Looking for hands on integration training
• Looking for a rapid deployment with no need to define integration requirements or processes
• Looking for total ownership of integration deployment and maintenance
Who’s it for
What is it
• Fixed bid enablement offering delivered in ten sessions
• 3 week period of performance to consume services
• Included with every sale
• Virtual light weight deployment services approach
• Designed to rapidly deploy Tasktop Sync
• Provides training and support for deploying Tasktop Sync between two endpoints
• Enables and empowers tool admins with knowledge and skills to install, configure, extend, and maintain Tasktop
Sync to meet point to point integration needs
• One Sync instance and one mapping - between two repositories, one project, and one artifact type – no
migration, no scripting, and no relationship management
31. Enterprise Enablement
• Enterprise organizations with a need to solve specific Software Lifecycle Integration patterns
• A need to preserve artifact relationships (ARM)
• In-house ownership or responsibility of ALM software and hardware infrastructure
• Dedicated integration admins (Certified Sync Admins)
• Looking for integration guidance and enablement
• Want assistance implementing integration workflow best practices
• Looking for total ownership of integration deployment and maintenance
Who’s it for
What is it
• Fixed bid enablement offering
• 6 week period of performance to consume services
• Virtual and/or on-site delivery approach
• Designed to rapidly deploy Tasktop Sync
• Provides training, recommendations, and support for introduction of Tasktop Sync into ALM tool stack
• Provides basic SLI consulting to review and document integration patterns
• Enables and empowers tool admins with knowledge and skills to install, configure, extend, and maintain Tasktop
Sync to meet ALM infrastructure needs
• One Sync instance and up to three mappings - between two repositories, one project, and three artifact
types – no migration
32. Tasktop Data
0
2
4
6
8
May June July Aug
0
2
4
6
8
Your reporting solution
Database
Tasktop Data populates your own database with project
data for reporting and analytics.
Editor's Notes
Tremendous amount of innovation
Cost has been the disconnect between the silos
Exacerbated by geography, tools and culture
Non-technical people responsible for software
Causes software delivery breaks down at scale
Here’s what we found talking to customers
$10M per year for 1,500-strong delivery organization
Lack of integration strategy fragments the way that information flows through the organisation, with disparate tools, connectors and context.
Due to the frequent handoffs between tools used in the software delivery organisation, and increasing use of bimodal development strategy, there are more tools, each changing frequently.
Currently you won’t be seeing “integration” as a problem because it is fragmented –technically and commercially. What you will be seeing is that the cost of this fragmented approach is costing a lot of money and holding your delivery teams back. This is because all the handoffs across the tools are handled by inconsistent point connections and the cost of this, both purchase and ongoing, is hidden across departmental budgets, tool stacks and consulting agreements.
But you need to address this as part of your transformation
The delivery teams need to deliver
Value
Quality
Manual Entry/re-keying directly reduces their delivery capability
Conservatively estimated at 20mins/person/day
If your teams weren’t engaged in this essential but NVA activity, what could they be doing?
Taking the next most valuable feature off the backlog and delivering it, that’s what!
Apx. 1500
IT infrastructure fault lines
Costs of managing integrations become prohibitive
Upgrades to lifecycle tools cause costly delays
Release and API changes can and do occur frequently
Need to scale and adapt across the business
Across divisional, organizational and geographical siloes
Across on-premise, SaaS and hybrid tool stacks
Address evolving and differing practices and processes
Embrace all lifecycle tools
Support synchronization and information flow across
Bi-directional ALM tools (information synchronization)
Automated DevOps tools (event-based)
Phoenix project quote?
What you really need, what an Enterprise organization needs
Does anyone know what Bi-Modal refers to? Those are our friends still using some waterfall methods in their SDLC. I’m sure you don’t know anyone like that, do you?? I pulled that from a colleagues’s slide deck, our VP of sales for EMEA he’s from the UK. Of course a Brit would make that sound nicer that it really is…!
RLIA-TE is a full configurable, scalable enterprise integration bus architecture
Point-to-point integrations bring down tools in production
Repeated API calls overload systems at scale
Eg, connecting 3 point-to-point integrations to production JIRA can make it unresponsive
Point-to-point integrations are unmanageable at scale
One workflow schema change can cause dozens of API/webhook integrations to break, no way of knowing where the break originated
True enterprise scaleability
Built to handle dozens of systems and tens of thousands of users
Only incremental integration, all data is cached, no traffic if no changes
All integrations can be managed and monitored on a single console
Look- we know that the problem exists
We know it is expensive and hard to try and solve it yourself
We know because we made w whole company out of solving that problem
So much so that IBM asked us to use our solution as part of their software entitlements to IBM customers as an OEM offering
We are the industry leader in the Sofware lifecycle integration space
Problem
Multiple tools * multiple versions * multiple APIs/schemas
Impossible to know what works with what (eg, can I trace requirements across A/B/C?)
Manual testing is insufficient
Vendors update APIs multiple times per year
Vendors continue adding new APIs (eg, hierarchical requirements, time tracking)
Impossible to keep up with changes using manual testing
To scale, tool, version and artifact testing must be automated
System data is corrupted
E.g. links accidentally deleted by end user, comments broken, duplicates imported
Management layer on top, delivery layer on bottom
Last revision: 23 April 2015
Current for Sync 4.2
Apx. 1500 user example
This is what we commonly see
Adam’s Demo
This is our big differentiator from other commercial competitors
Domain-aware integration
Integration without coding
Model-based configuration for ease of deployment (and testability)
Transparent to end-users
Across all software development and delivery disciplines
Supports syncing in 296 versions of tools + triggered actions from Gateway tools
Does not break when tools are upgraded
High performance and integrity
Connectors developed to our integration specification and tested nightly
API integration only
Incremental syncing
Robust error handling and conflict resolution
This is who we are, and why IBM and 321 Gang work with us
Last updated: 10 August 2016
This is how we support other process initiatives like SAFe
This is an example of a large enterprise customer using RLIA-TE to support DevOps transformation
Get this add-on solution directly from Tasktop or 321 Gang at this time
Customers who take advantage of global configuration management with CLM tools from IBM they have multiple version of requirements throughout the lifecycle of a project. To maintain traceability across the versions of those requirements, possible across to non-IBM tools like HPE QC/ALM or JIRA,
Traceability From Requirement Through to DeploymentTraceability of work products helps all teams ensure key controls have been met through their SDLC process
Traceability relationships is a pre-requisite for increased automation of controls related to SDLC Governance