In today’s fast paced marketplace, the demand for product quality and incremental updates is continually increasing. Competing industry goals such as rapid feature development and continual deployment create an environment where release management and risk mitigation can become tenuous. DevOps – a contraction of “Development and Operations" – allows companies to unify the two facets of an organization’s technology department. This presentation covers how DevOps allows companies developing complex systems to integrate their development, testing and deployment processes. We believe in product innovation through rapid software development, and we lived DevOps through our experience as IBM Rational Developers. Presented by: Matthew Clement, Senior Consultant, PacGenesis Matt joined PacGenesis in 2014 as a senior software consultant. Previously he was employed with IBM for twelve years as a software engineer working on enterprise development products across several organizations. Most recently he was a member of the development team for Rational Team Concert with a focus on enterprise extensions and build. Matt graduated with his M.S and B.S from Virginia Tech in 2002 where he majored in Computer Science. Scott Pecnik, Senior Consultant, PacGenesis Scott has been working with IBM Software for more than eight years. He is a former IBM employee where he held various positions throughout the organization, stemming from development to product innovation to pre-sales. Most recently, he was a developer on the Rational Team Concert Enterprise Edition product. Since leaving IBM in 2010, Scott has been consulting for many of the IBM Rational products for customers of all sizes across all industries, focusing specifically on Rational Team Concert. Scott holds two B. S. degrees from North Carolina State University where he majored in Computer Science and Business Management – Finance. Jim Sullivan, Principal and Tech Lead, Arcisphere Technologies Jim Sullivan is the Principal partner of Arcisphere Technologies. Jim was with IBM for 9 years during which Jim supported global clients with ALM, Agile and DevOps solutions. Since forming Arcisphere Technologies Arcisphere is a firm that serves client with products and services for software development, including tools, services, training, and Agile transformations. Jim has achieved certifications in the IBM CLM and DevOps product line. Jim has also achieved Certified Scrum Professional (CSP), and Scaled Agile Program Consultant (SPC) certification for the Scaled Agile Framework (SAFe). Arcisphere was recently accepted into IBM Rational’s SAFe partner ecosystem, and will have a booth at Innovate. Jim has a B.S. in Engineering from NJIT, a Ma

1. Join the Community
www.rational-ug.org
Tweet with Us @RationalUC #rationaluc
www.twitter.com/rationaluc
Join Our Group on LinkedIn: Global Rational User Community
https://www.linkedin.com/groups/Global-Rational-User-Community-GRUC-120486/about
Connect with Us on Google+
https://plus.google.com/+RationalugOrgGlobal/posts

2. Increasing Product Quality
through DevOps
Matthew Clement & Jim Sullivan

3. Agenda
1. DevOps: An Introduction
2. DevOps vs. Agile
3. DevOps Inspired Agile
4. Why DevOps?
5. A “Rational” DevOps Solution
6. DevOps++

4. DevOps: An Introduction
Development and Operations
• Contraction of Development and Operations
• Industry History
• “DevOps Days” in 2009 in Belgium
• Response to growing interdependence between IT operations and software development
• Associated with lean startup methodologies (JIT Manufacturing)
• What it’s not
• A position—you can’t *be* a DevOp
• It’s not a straight forward mix of developer and operations roles—it’s less like granola and more
like soufflé
• Everyone enjoys a good meme…

5. DevOps: An Introduction
Development and Operations

6. DevOps: An Introduction
Development and Operations
• What is DevOps?
• “... Stresses communication & collaboration … aims to help an organization rapidly produce
software products and services…” –Wikipedia
• “The DevOps movement was born of the need to improve IT Service delivery agility…” –Gartner
• “DevOps is an approach to bridge the gap between agile software development and operations”
–agileweboperations.com
• No standard definition
• “SOA is not a technology, but only a style of architecture, or an approach to building software
products” –Mike Liu, 2009
• DevOps is to operations what Agile is to software development.

7. Agenda
1. DevOps: An Introduction
2. DevOps vs. Agile
3. DevOps Inspired Agile
4. Why DevOps?
5. A “Rational” DevOps Solution
6. DevOps++

8. DevOps vs. Agile
• Development is Agile
• Create change
• Add or modify features
• Operations are Static
• Value stability
• Enhance services
• DevOps grown out of Agile
• Agile accelerates development and operations
• DevOps coordinates them

9. DevOps vs. Agile
Agile Customers
Product
Management
Developers
QA
DevOps
Service
Delivery
System
Interaction

10. DevOps vs. Agile
• Adaptive Software Development (ASD)
• Agile Modeling
• Agile Unified Process (AUP)
• Extreme Programming (XP)
• Feature Driven Development (FDD)
• Lean software development
• Scrum
• Acceptance test-driven development (ATDD)
• Agile Modeling
• Backlogs (Product and Sprint)
• Behavior-driven development (BDD)
• Cross-functional team
• Continuous integration (CI)
• Iterative and incremental development (IID)
• Pair programming
• Planning poker
1. Customer satisfaction
2. Welcome changing requirements
3. Working software delivered frequently
4. Close, daily cooperation
5. Projects built around individuals
6. Face-to-face conversation
7. Working software as metric
8. Sustainable development
9. Continuous attention to design
10. Simplicity is essential
11. Self-organizing teams
12. Regular adaptation to change
•Individuals and interactions over
Processes and tools
•Working software over
Comprehensive documentation
•Customer collaboration over
Contract negotiation
•Responding to change over
Following a plan
Values Principles
MethodsPractices

11. DevOps vs. Agile
•DevOps methods
are currently being
defined in the
industry
•DevOps practices
are, like Agile
practices, specific
techniques of
implementing
DevOps ideals.
•DevOps principles
wide the agile
definition to
encompass system
and operations
•Some call this
“infrastructure as
code”
•DevOps values are
service driven
whereas Agile
values are software
development centric
Values Principles
MethodsPractices

12. Agenda
1. DevOps: An Introduction
2. DevOps vs. Agile
3. DevOps Inspired Agile
4. Why DevOps?
5. A “Rational” DevOps Solution
6. DevOps++

13. DevOps Inspired Agile

14. Agenda
1. DevOps: An Introduction
2. DevOps vs. Agile
3. DevOps Inspired Agile
4. Why DevOps?
5. A “Rational” DevOps Solution
6. DevOps++

15. Why DevOps?
Raw Materials
Manufacturing
Consumers
Widget Factory

16. DevOps vs. Agile
Agile Customers
Product
Management
Developers
QA
DevOps
Service
Delivery
System
Interaction

17. Why DevOps?
Procurement
Distribution
Market Feedback
Shipping

18. Why DevOps?

19. Why DevOps?
• Addressing the “Execution Gap”

20. Why DevOps?

21. Why DevOps?
• Addressing the “Execution Gap”
• Adversarial development interests
• Systems of Record (Back End Systems, Databases, etc.) value
stability and usually develop using Waterfall.
• Systems of Engagement (Mobile Apps, Web UI, Distributed systems,
etc.) value time to market and typically develop using Agile Methods
• Coordinate efforts between teams
• Closer connection between technology and processes
• Seize market opportunity
• Shorten time to customer feedback

22. Why DevOps?

23. Why DevOps?

24. Why DevOps?

25. Why DevOps?

26. Why DevOps?
• Manual processes can be a bottleneck to product
quality
• Fundamentally error prone
• Break down
• Create Waste
• Slow feedback loop
• Add individual resource—this is the brute force
approach.
• Technology on its own is only part of the solution

27. Why DevOps?
• Complex deployment topology
• Problems get introduced during the deploy of
an application
• Incorrect deployment
• Deploy in a different way
• Undeployed code is loss of revenue

28. Agenda
1. DevOps: An Introduction
2. DevOps vs. Agile
3. DevOps Inspired Agile
4. Why DevOps?
5. A “Rational” DevOps Solution
6. DevOps++

29. “Rational” DevOps
Quality team collaboration
Rational
Quality Manager
Coordinate quality assurance
plans, processes, and
resources
Business expert collaboration
Elicit, capture, elaborate, discuss,
and review requirements
Rational
Requirements
Composer
Rational
Team Concert
Core team collaboration
"Think and work" in unison and
provide real-time project status
Architect
Developer
REST API
Quality
management
REST API
Requirements
management
Change and
configuration
management
REST API
AssociationChanges and notification
Tester finds defects,
generates work item
Defect statusDefects closed
against
requirements
Requirement linked
to work item
Analyst Tester
UrbanCode

30. Agenda
1. DevOps: An Introduction
2. DevOps vs. Agile
3. DevOps Inspired Agile
4. Why DevOps?
5. A “Rational” DevOps Solution
6. DevOps++

31. DevOps++ : More Reliable Cloud Testing
Flight.java
Hotel.java
recent.java
airReport.java
payPal.java
dataDrivenPrice.java
Price.sql
Continuously Deliver and Build
Continuously Deliver and Build
Cloud Test Environments:
Functional, Security, Performance

32. DevOps++
• Traditional View
• Looking Ahead
• Governance practices
• Security and Compliance
• Lines of Business
• Software Suppliers
• Of course, end users!

33. Jim Sullivan is the President
of Arcisphere Technologies.
Arcisphere help clients with
the best of DevOps, Agile,
Tools and Development.
www.arcisphere.com
Matt Clement is a Senior
Software Consultant at
PacGenesis, Inc—the
Authority on RTC; leaders in
CLM.
www.pacgenesis.com
Thanks!

34. Join the Community
www.rational-ug.org
Tweet with Us @RationalUC #rationaluc
www.twitter.com/rationaluc
Join Our Group on LinkedIn: Global Rational User Community
https://www.linkedin.com/groups/Global-Rational-User-Community-GRUC-120486/about
Connect with Us on Google+
https://plus.google.com/+RationalugOrgGlobal/posts