Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo
CORPORATE
OVERVIEW
A BUSINESS / MARKETING PRESENTATION
An Intro to Column DevOps
Presented by:
Everything you need for continuous delivery
“Atlassian Test Case Management Options
and Integrations”
Software Automation with Quality Delivery
Presented by:
Blaine Pryce - VP DevOps
Bob Ho - APM Consultant
June 12, 2018
Software Automation with Quality Delivery
Column Technologies at a Glance
2
Founded in 1998
Offices across the United States, Canada, India,
and the United Kingdom
88+ Million Revenue
Over 3,000 Projects Implementations Service Management (BMC, ServiceNow)
InfoSec, DevOps
Built on Services
Process, Architecture, Implementation,
Support, Managed Services
440+ Employees
Over 300+ Technical Consultants and Engineers
Practices
Long Term Customer Partnership
Service Expertise with Leading Market
Solutions
Software Automation with Quality Delivery
About Column DevOps
Accelerating DevOps Adoption
Through Automation
3
Software Automation with Quality Delivery 4
DevOps Technology Overview
▪ Fast growing, market
leaders
▪ Built from the ground
up for today’s complex
application
environments
▪ Less instrumentation
▪ Faster ROI
Test
Develop
Plan
Operate
Deploy
Software Automation with Quality Delivery 5
DevOps Framework and Principals
Flow of Data
Continual Learning and Experimentation
Feedback
Plan
Develop
TestDeploy
Operate DevOps
Framework
Continuous Improvement
Software Automation with Quality Delivery
IDC : DevOps and the Cost of Downtime
6
✓IT organizations that have tried to custom adjust
current tools to meet DevOps practices have a failure
rate of 80%, thus making tool replacement and/or
addition a critical requirement
✓There are many areas where tool replacement is likely
to occur including application management, testing,
QA and operations….
Software Automation with Quality Delivery
DevOps Challenge: Technical Debt
7
Cost of additional rework caused by choosing an easy solution
instead of using a better approach that requires re-tooling.
Software Automation with Quality Delivery
Why?
“Old methods and processes don’t work”
80%
OF ALL COMPANIES expected to
adopt DevOps within the next
2 years
8
*ServiceNow
Software Automation with Quality Delivery
Why?
“It’s not our fathers software architecture”
It’s no longer this simple…
It’s this complex...
9
Mobile
Big data
SOA
NOSQL
Cloud
Agile
Web
Software Automation with Quality Delivery 10
DevOps Re-tooling
“New processes, outdated tools, manual and point solutions create Software Delivery Bottlenecks”
Software Automation with Quality Delivery
IDC: DevOps and the Cost of Downtime
11
Category % of Respondents AppDynamics Applicability
Application management 25 YES
Testing / QA 21.4 YES
Operations 21.4 YES
Development 14.3 YES
Integration 14.3 YES
IT analytics 3.6 YES
In which discipline are you likely to purchase new tools to accelerate DevOps?
Software Automation with Quality Delivery
DevOps Testing
Atlassian Test Case Management Options
12
Software Automation with Quality Delivery 13
Testing Charters Yesterday VS Today
Agile
▪ “Shift Left” - Test Early and Often”
▪ Prevent Bugs
▪ Building the Best Application
▪ Team Responsibility for Quality
Waterfall
▪ Test at the End of Development
▪ Find Bugs
▪ Breaking the Application
▪ Tester’s Responsibility
“Testing can no longer be cut from a
project”
Software Automation with Quality Delivery
Integration with
other agile tools
▪ Bitbucket
▪ Bamboo
▪ Automated testing tools
14
DevOps TCM Tool Requirements
Agile workflows
▪ Kanban, Scrum
▪ TDD/BDD/ATDD
▪ Exploratory Testing
▪ Test plan review - post sprint
Easy to Use
▪ Intuitive UI
▪ Customizable
Multi platform and browsers
▪ Microsoft
▪ Lynx
▪ Chrome
▪ Firefox
▪ Safari
▪ Mobile
“The testing game has changed”
Software Automation with Quality Delivery
JIRA Add-ons / Plugins
▪ Zephyr
▪ Adaptavist
▪ Xray
15
Atlassian Test Case Mgt. Options
Legacy
▪ Borland
▪ IBM
▪ HP
External Solutions
▪ QASymphony
▪ Zephyr Enterprise
▪ TestRail
“What’s the right TCM tool for today and
tomorrow???”
Software Automation with Quality Delivery
Financial
16
Legacy Tool Advantages
Suite Based
▪ No Cap x
▪ Leverage the infrastructure
Ready to Go
“Legacy tools can provide a quick
testing solution with low initial cost”
▪ Time to market
▪ Experience
▪ No learning curve
▪ Func and Performance Tools
▪ ALM/Waterfall
Software Automation with Quality Delivery
Lack of integration with
other agile tools
▪ Integration support required
▪ JIRA, automation tools
▪ Manual steps
17
Legacy Tool Challenges
Hard to Use
▪ Training time
▪ Tool Bloat
Doesn’t fit agile workflows
▪ Not sprint friendly
▪ Automation gaps
Not cross platform/browser
▪ Limited scope
▪ IE only
“Legacy testing software are not built
for the Agile world”
Software Automation with Quality Delivery
Integration Capabilities
▪ REST API
18
Add-ons / Plugins Advantages
Extend JIRA functions
▪ Test Issue type
▪ Link defects
▪ Link stories, tasks, requirements
▪ Plan test execution cycles
Fast Deployments
▪ Simple purchasing
▪ Hours to days
“Testing add-ons are available via
Marketplace”
Look and Feel
▪ JIRA, JIRA, JIRA
▪ Easy Adoption
▪ Dashboard ready
Software Automation with Quality Delivery
Minimal OTB Integration
▪ Integration support
19
Add-ons / Plugins Challenges
Not Enterprise Ready
▪ Limited Reporting
▪ Test case versioning
▪ Non- Reusable test suites/plans
▪ Unknown change history
Designed for
▪ Smaller teams
▪ Less mature teams
Scalability
▪ Recreating tests
▪ Multiple testing approaches
▪ Licensing
“Add-ons /plugins are not designed for
enterprise class operations”
Software Automation with Quality Delivery
OTB Integration with
other agile tools
▪ Automation
▪ CI
20
External Solutions Advantages
Supports full Agile/DevOps
▪ Designed for continuous
▪ Exploratory
▪ TDD/BDD/ATDD
Leverage JIRA
▪ Bi-directional
▪ Dedicated Testing Tool
Enterprise Testing Features
▪ Test case reuse
▪ Test Plan Mgt
▪ Enterprise Reporting
“DevOps teams struggle without the
appropriate level of TCM automation”
Software Automation with Quality Delivery
Integration to agile tools
▪ Integration support
▪ 3rd party
▪ Open source
21
External Solutions Challenges
Investment
▪ $$$
▪ Longer Implementation
Leverage JIRA
▪ DB Sync VS real-time
Application Mappings
▪ Artifacts and permissions
“External testing tools are not typically
deployed in year 1 of DevOps/Agile
transformation”
Software Automation with Quality Delivery 22
Where to Start?
Evaluate current state vs future state
▪ How soon?
▪ Maturity?
▪ How much tools/functions can I bring on today?
▪ Impact?
▪ Will my requirements change in 6 months?
Software Automation with Quality Delivery
DevOps Technology Use Case
Atlassian Test Case Management Integrations
Bob Ho - APM Consultant
23
Software Automation with Quality Delivery
Commit is pushed to Bitbucket –
This triggers the CI / CD pipeline
Delphix provisions a prod-like data
for testing
Automated testing from Cucumber
Monitoring from AppDynamics
Test results, and a Delphix
Bookmark, are reported to qTest
qTest opens a defect in Jira
The Jira bug then allows a branch
to be opened in Bitbucket or Github
Commit is Pushed
1
2
3
4
5
6
7
Provision Test Data
Test Results
Automated
Testing/Monitoring
Bookmark
Remediate
Bug Tracking
1
2
3
4
5
6
7
Atlassian TCM Integrations
Software Automation with Quality Delivery
DevOps Technology Use Case
Visibility of Code Releases
25
Software Automation with Quality Delivery
Improve code release visibility
Performance Before
Performance Today
Who struggles with understanding how
releases impact performance?
My insurance customer lacked visibility into
impacts from code releases
Software Automation with Quality Delivery
Identifying code release timeframes
• Add custom events to the CI/CD
pipeline
▪ REST call from IBM UrbanCode to
AppD
• Events are actionable within
AppDynamics
• Alert user when deployment
occur
Software Automation with Quality Delivery
Identify performance issues vs. deployments
By now correlate events to
transaction score
Easily identify if performance is
related to application
deployment
Broader audience using AppD
for release validation
28
Software Automation with Quality Delivery
Summary
29
✓ Technical Debt exists in every DevOps Organization
✓ Technology Review and Roadmap Exercise
✓ Crawl-Walk-Run Journey
Software Automation with Quality Delivery
Further Reading
30
✓ IDC Report: https://www.appdynamics.com/press-release/idc-releases-first-ever-
devops-and-application-performance-survey/
✓ Docker/Jenkins Continuous Delivery https://www.cloudbees.com/press/cloudbees-
reports-on-state-of-docker-jenkins-and-continuous-delivery
JIRAforbusinessThe Swiss Army Knife
E T H A N F O U L K E S • V P O F D E L I V E R Y • C P R I M E
B A T M A N • C R I M E F I G H T E R • G O T H A M
Agenda
cPrime Toolbox
JIRA – From front to back
Problems
Problems
JIRA – From front to back
Toolbox
1,734
I built a person….
AWESOME!!!
Time to upgrade?
JIRA makes me sad
AUG NYC June 12 - Event Presentations
AUG NYC June 12 - Event Presentations
Problems
JIRA – From front to back
Toolbox
What we used
Batman’s favorite!
Only visible when resolved and reopen date is set.
Clones and copies certain fields
Clears reopen date field
Sends e-mail on reopen date
JIRA – From front to back
cPrime Toolbox
Problems
Automating freight rate collection
Support Services Logistics
Vendor 1
Vendor 2
Vendor 3
Vendor 4
Vendor 5
Vendor 6
Vendor 7
Logistics Responsibilities
• Follow-up
• Data entry
• Aggregate/Analyze
Freight Requests
AUG NYC June 12 - Event Presentations
• SQL Queries
• API Calls
• Due date forces workflow transition
• Required fields based on selections
• Dynamic fields
External Source
What we replaced
• Summary Renamer
• Intelligent Routing
SQL injected with field values
47 Vendors down to 18
Future: Intelligent sorting based on results (Knowledge Transfer)
Each checkbox creates a sub-task
47
• Creates sub-tasks for each checkbox
• Copies all relevant info
• Sets # of vendor field / Portal updates
• API push to portal
• Sends custom e-mail
What we replaced
3 Phase Project
Phase 1: Collect e-mails / Automate reminders
Phase 2: Portal for data entry
Phase 3: (Future) Automated vendor selection
• Triggers transition in JIRA
• Adds comments to JIRA
Request Info
Fast forward 1-2 weeks
Request Info
3 Lanes, 14 Rates
Transitions Workflow
Tacit to Codified
What we replaced
$850 Initial
$425 Recurring
• Power Scripts
• KCF Pro
$7,050 Initial
$3,525 Recurring
• CCC Last Comment
• Dynamic Forms
• nFeed
• Create on Transition
• Update on Transition
• Email This Issue
• Workflow Toolbox
• Misc Workflow Extensions
• Automation
Ethan Foulkes • VP of Delivery • cPrime
Thank you!
Power Scripts vs. Others
SIL Script
Groovy Script
ABSTRACTION LAYER
Others Power Scripts
Jira
Jira
Dependencies
Classes
Packages
Tech Debt
Dependencies
Classes
Packages

More Related Content

AUG NYC June 12 - Event Presentations

  • 1. CORPORATE OVERVIEW A BUSINESS / MARKETING PRESENTATION An Intro to Column DevOps Presented by: Everything you need for continuous delivery “Atlassian Test Case Management Options and Integrations” Software Automation with Quality Delivery Presented by: Blaine Pryce - VP DevOps Bob Ho - APM Consultant June 12, 2018
  • 2. Software Automation with Quality Delivery Column Technologies at a Glance 2 Founded in 1998 Offices across the United States, Canada, India, and the United Kingdom 88+ Million Revenue Over 3,000 Projects Implementations Service Management (BMC, ServiceNow) InfoSec, DevOps Built on Services Process, Architecture, Implementation, Support, Managed Services 440+ Employees Over 300+ Technical Consultants and Engineers Practices Long Term Customer Partnership Service Expertise with Leading Market Solutions
  • 3. Software Automation with Quality Delivery About Column DevOps Accelerating DevOps Adoption Through Automation 3
  • 4. Software Automation with Quality Delivery 4 DevOps Technology Overview ▪ Fast growing, market leaders ▪ Built from the ground up for today’s complex application environments ▪ Less instrumentation ▪ Faster ROI Test Develop Plan Operate Deploy
  • 5. Software Automation with Quality Delivery 5 DevOps Framework and Principals Flow of Data Continual Learning and Experimentation Feedback Plan Develop TestDeploy Operate DevOps Framework Continuous Improvement
  • 6. Software Automation with Quality Delivery IDC : DevOps and the Cost of Downtime 6 ✓IT organizations that have tried to custom adjust current tools to meet DevOps practices have a failure rate of 80%, thus making tool replacement and/or addition a critical requirement ✓There are many areas where tool replacement is likely to occur including application management, testing, QA and operations….
  • 7. Software Automation with Quality Delivery DevOps Challenge: Technical Debt 7 Cost of additional rework caused by choosing an easy solution instead of using a better approach that requires re-tooling.
  • 8. Software Automation with Quality Delivery Why? “Old methods and processes don’t work” 80% OF ALL COMPANIES expected to adopt DevOps within the next 2 years 8 *ServiceNow
  • 9. Software Automation with Quality Delivery Why? “It’s not our fathers software architecture” It’s no longer this simple… It’s this complex... 9 Mobile Big data SOA NOSQL Cloud Agile Web
  • 10. Software Automation with Quality Delivery 10 DevOps Re-tooling “New processes, outdated tools, manual and point solutions create Software Delivery Bottlenecks”
  • 11. Software Automation with Quality Delivery IDC: DevOps and the Cost of Downtime 11 Category % of Respondents AppDynamics Applicability Application management 25 YES Testing / QA 21.4 YES Operations 21.4 YES Development 14.3 YES Integration 14.3 YES IT analytics 3.6 YES In which discipline are you likely to purchase new tools to accelerate DevOps?
  • 12. Software Automation with Quality Delivery DevOps Testing Atlassian Test Case Management Options 12
  • 13. Software Automation with Quality Delivery 13 Testing Charters Yesterday VS Today Agile ▪ “Shift Left” - Test Early and Often” ▪ Prevent Bugs ▪ Building the Best Application ▪ Team Responsibility for Quality Waterfall ▪ Test at the End of Development ▪ Find Bugs ▪ Breaking the Application ▪ Tester’s Responsibility “Testing can no longer be cut from a project”
  • 14. Software Automation with Quality Delivery Integration with other agile tools ▪ Bitbucket ▪ Bamboo ▪ Automated testing tools 14 DevOps TCM Tool Requirements Agile workflows ▪ Kanban, Scrum ▪ TDD/BDD/ATDD ▪ Exploratory Testing ▪ Test plan review - post sprint Easy to Use ▪ Intuitive UI ▪ Customizable Multi platform and browsers ▪ Microsoft ▪ Lynx ▪ Chrome ▪ Firefox ▪ Safari ▪ Mobile “The testing game has changed”
  • 15. Software Automation with Quality Delivery JIRA Add-ons / Plugins ▪ Zephyr ▪ Adaptavist ▪ Xray 15 Atlassian Test Case Mgt. Options Legacy ▪ Borland ▪ IBM ▪ HP External Solutions ▪ QASymphony ▪ Zephyr Enterprise ▪ TestRail “What’s the right TCM tool for today and tomorrow???”
  • 16. Software Automation with Quality Delivery Financial 16 Legacy Tool Advantages Suite Based ▪ No Cap x ▪ Leverage the infrastructure Ready to Go “Legacy tools can provide a quick testing solution with low initial cost” ▪ Time to market ▪ Experience ▪ No learning curve ▪ Func and Performance Tools ▪ ALM/Waterfall
  • 17. Software Automation with Quality Delivery Lack of integration with other agile tools ▪ Integration support required ▪ JIRA, automation tools ▪ Manual steps 17 Legacy Tool Challenges Hard to Use ▪ Training time ▪ Tool Bloat Doesn’t fit agile workflows ▪ Not sprint friendly ▪ Automation gaps Not cross platform/browser ▪ Limited scope ▪ IE only “Legacy testing software are not built for the Agile world”
  • 18. Software Automation with Quality Delivery Integration Capabilities ▪ REST API 18 Add-ons / Plugins Advantages Extend JIRA functions ▪ Test Issue type ▪ Link defects ▪ Link stories, tasks, requirements ▪ Plan test execution cycles Fast Deployments ▪ Simple purchasing ▪ Hours to days “Testing add-ons are available via Marketplace” Look and Feel ▪ JIRA, JIRA, JIRA ▪ Easy Adoption ▪ Dashboard ready
  • 19. Software Automation with Quality Delivery Minimal OTB Integration ▪ Integration support 19 Add-ons / Plugins Challenges Not Enterprise Ready ▪ Limited Reporting ▪ Test case versioning ▪ Non- Reusable test suites/plans ▪ Unknown change history Designed for ▪ Smaller teams ▪ Less mature teams Scalability ▪ Recreating tests ▪ Multiple testing approaches ▪ Licensing “Add-ons /plugins are not designed for enterprise class operations”
  • 20. Software Automation with Quality Delivery OTB Integration with other agile tools ▪ Automation ▪ CI 20 External Solutions Advantages Supports full Agile/DevOps ▪ Designed for continuous ▪ Exploratory ▪ TDD/BDD/ATDD Leverage JIRA ▪ Bi-directional ▪ Dedicated Testing Tool Enterprise Testing Features ▪ Test case reuse ▪ Test Plan Mgt ▪ Enterprise Reporting “DevOps teams struggle without the appropriate level of TCM automation”
  • 21. Software Automation with Quality Delivery Integration to agile tools ▪ Integration support ▪ 3rd party ▪ Open source 21 External Solutions Challenges Investment ▪ $$$ ▪ Longer Implementation Leverage JIRA ▪ DB Sync VS real-time Application Mappings ▪ Artifacts and permissions “External testing tools are not typically deployed in year 1 of DevOps/Agile transformation”
  • 22. Software Automation with Quality Delivery 22 Where to Start? Evaluate current state vs future state ▪ How soon? ▪ Maturity? ▪ How much tools/functions can I bring on today? ▪ Impact? ▪ Will my requirements change in 6 months?
  • 23. Software Automation with Quality Delivery DevOps Technology Use Case Atlassian Test Case Management Integrations Bob Ho - APM Consultant 23
  • 24. Software Automation with Quality Delivery Commit is pushed to Bitbucket – This triggers the CI / CD pipeline Delphix provisions a prod-like data for testing Automated testing from Cucumber Monitoring from AppDynamics Test results, and a Delphix Bookmark, are reported to qTest qTest opens a defect in Jira The Jira bug then allows a branch to be opened in Bitbucket or Github Commit is Pushed 1 2 3 4 5 6 7 Provision Test Data Test Results Automated Testing/Monitoring Bookmark Remediate Bug Tracking 1 2 3 4 5 6 7 Atlassian TCM Integrations
  • 25. Software Automation with Quality Delivery DevOps Technology Use Case Visibility of Code Releases 25
  • 26. Software Automation with Quality Delivery Improve code release visibility Performance Before Performance Today Who struggles with understanding how releases impact performance? My insurance customer lacked visibility into impacts from code releases
  • 27. Software Automation with Quality Delivery Identifying code release timeframes • Add custom events to the CI/CD pipeline ▪ REST call from IBM UrbanCode to AppD • Events are actionable within AppDynamics • Alert user when deployment occur
  • 28. Software Automation with Quality Delivery Identify performance issues vs. deployments By now correlate events to transaction score Easily identify if performance is related to application deployment Broader audience using AppD for release validation 28
  • 29. Software Automation with Quality Delivery Summary 29 ✓ Technical Debt exists in every DevOps Organization ✓ Technology Review and Roadmap Exercise ✓ Crawl-Walk-Run Journey
  • 30. Software Automation with Quality Delivery Further Reading 30 ✓ IDC Report: https://www.appdynamics.com/press-release/idc-releases-first-ever- devops-and-application-performance-survey/ ✓ Docker/Jenkins Continuous Delivery https://www.cloudbees.com/press/cloudbees- reports-on-state-of-docker-jenkins-and-continuous-delivery
  • 31. JIRAforbusinessThe Swiss Army Knife E T H A N F O U L K E S • V P O F D E L I V E R Y • C P R I M E B A T M A N • C R I M E F I G H T E R • G O T H A M
  • 32. Agenda cPrime Toolbox JIRA – From front to back Problems
  • 33. Problems JIRA – From front to back Toolbox
  • 34. 1,734
  • 35. I built a person…. AWESOME!!!
  • 40. Problems JIRA – From front to back Toolbox
  • 43. Only visible when resolved and reopen date is set. Clones and copies certain fields Clears reopen date field Sends e-mail on reopen date
  • 44. JIRA – From front to back cPrime Toolbox Problems Automating freight rate collection
  • 45. Support Services Logistics Vendor 1 Vendor 2 Vendor 3 Vendor 4 Vendor 5 Vendor 6 Vendor 7 Logistics Responsibilities • Follow-up • Data entry • Aggregate/Analyze Freight Requests
  • 47. • SQL Queries • API Calls • Due date forces workflow transition • Required fields based on selections • Dynamic fields External Source
  • 49. • Summary Renamer • Intelligent Routing
  • 50. SQL injected with field values 47 Vendors down to 18 Future: Intelligent sorting based on results (Knowledge Transfer) Each checkbox creates a sub-task 47
  • 51. • Creates sub-tasks for each checkbox • Copies all relevant info • Sets # of vendor field / Portal updates • API push to portal • Sends custom e-mail
  • 53. 3 Phase Project Phase 1: Collect e-mails / Automate reminders Phase 2: Portal for data entry Phase 3: (Future) Automated vendor selection
  • 54. • Triggers transition in JIRA • Adds comments to JIRA Request Info
  • 55. Fast forward 1-2 weeks Request Info 3 Lanes, 14 Rates Transitions Workflow Tacit to Codified
  • 57. $850 Initial $425 Recurring • Power Scripts • KCF Pro $7,050 Initial $3,525 Recurring • CCC Last Comment • Dynamic Forms • nFeed • Create on Transition • Update on Transition • Email This Issue • Workflow Toolbox • Misc Workflow Extensions • Automation
  • 58. Ethan Foulkes • VP of Delivery • cPrime Thank you!
  • 59. Power Scripts vs. Others SIL Script Groovy Script ABSTRACTION LAYER Others Power Scripts Jira Jira Dependencies Classes Packages Tech Debt Dependencies Classes Packages

Editor's Notes

  1. Drag Picture and Send to Back
  2. DevOps is unachievable without a high degree of automation. The velocity is too fast.
  3. DevOps is unachievable without a high degree of automation. The velocity is too fast.
  4. DevOps is unachievable without a high degree of automation. The velocity is too fast.
  5. DevOps is unachievable without a high degree of automation. The velocity is too fast.
  6. DevOps is unachievable without a high degree of automation. The velocity is too fast.
  7. DevOps is unachievable without a high degree of automation. The velocity is too fast.
  8. DevOps is unachievable without a high degree of automation. The velocity is too fast.