Pedro Gonçalves - Partner & Chief Technology Officer, @Xpand IT, during the presentation of Xpand IT & Atlassiam Jam Sessions 2016

1. PEDRO GONÇALVES • CTO • XPAND IT
Deliver Fast and Reliably
with DevOps and Atlassian

2. DEVOPS OVERVIEW
TODAY’S SITUATION
DEVOPS VALUES
Agenda
DEVOPS AND ATLASSIAN

3. Today’s situation

4. Rising business expectations
??
Stability
Today’s situation

5. MobileCloudBig data
New technologies
Virtualization
Agile development
Today’s situation

6. Lots of changes, not deployed quickly enough
Ops, QA, Testing, Support not aligned with development
Deployment failures have risk of downtime
Development and ops must work together
What about IT Operations?
Today’s situation

7. IT
Challenges
Visibility
Continuing pressure to improve
relevance of services.
Balance
IT must balance the rate of change
with stability.
Pressure
Scattered data or lack of data at all
limits incident and problem
understanding.

8. Support
Challenges of all incidents are due to changes
85%-87%

9. Support
Challenges Support is often unaware of changes
being made to services they support.
What changes?

10. Support
Challenges Support is hidden from developers,
product owners and product
managers.
Silo’d

11. DevOps Overview

12. ReliableAgile
High-Performing IT Organizations:
Winning
• 60x fewer failures
• Recover 168x faster
• Deploy 30x faster
• Lead times 200x
shorter
• 2x more likely to
exceed profitability,
market share and
productivity goals
Source: Puppet Labs 2014 and 2015 State of DevOps reports

13. Reliability
What do customers care about?
New functionality

14. Enabling the business and their customers by providing more
reliable services. When there’s an interruption, they’re able to
recover faster and minimize impact to the business.
High-performing IT organizations are

15. Enabling the business
High-Performing IT Organizations:

16. What is
DevOps?
DevOps is a movement that
advocates a collaborative working
relationship between development
and IT operations.

17. Development Operations
Everyone involved in developing
software products and services.
Everyone involved in delivering,
managing and supporting the
products and services.
Agile working relationship

18. Where did DevOps come from?
•Processes in place today aren’t meeting business needs.
•Response to bureaucratic processes

19. Notable DevOps practitioners:

20. DevOps Principles: The Three Ways

21. DevOps Principles
Dev Ops
Business Customer
The first way: systems thinking

22. DevOps Principles
Dev Ops
The second way: amplify feedback loops

23. DevOps Principles
The third way: continual experimentation and learning
Dev Ops

24. DevOps Values

25. Keep C.A.L.M.S.
and DevOps On

26. Automation
Measurement
Lean
Sharing
Culture

27. Culture
Focus on results
Understand behaviors
Good communication
• Standups
• Kanban boards
• Hack days
• Chatrooms or sharing space

28. Knowledge management
• Known errors at deployment
• Link articles to problems
Automation
End-to-end linking
• Link incidents, problems and requests
to changes and releases
Reliable deployment
• Continuous integration, continuous
delivery and continuous deployment
Testing
• Support requirements
Proactive monitoring
• Visibility to support

29. Lean
Eliminate waste
• What am I doing that doesn’t add value?
Pull vs. Push
• Driven by customer demand
Continuous improvement
• Small iterations
Failure is normal
• What was learned?

30. MTSR
• Mean-time-to-restore
• Did it increase or decrease?
Metrics
MTTR
• Mean-time-to-repair
• Did it increase or decrease?
Repetitive issues
• Did it increase or decrease?
SLAs/OLAs
• Service level agreements and
operational level agreements
• What is the impact of deployments
to achievements of service level
targets?
Cost per incident
Total cost of support
Cost of downtime

31. Sharing
Views
Goals Priorities
Process Knowledge
systems
Communication
Codebase
Toolsets
Ownership
Success
Workflow
Learnings

32. DevOps and Atlassian

33. Tasks &
projects
Messages &
calls
Requests &
SLAs
Code &
reviews
Pages &
files
Builds, Tests &
Deployment
Deliver fast and reliably
with DevOps and Atlassian

34. Culture
Focus on results
Understand behaviors
Good communication
• Standups
• Kanban boards
• Hack days
• Chatrooms or sharing space

35. MTSR
Metrics
MTTR
Repetitive issues
SLAs/OLAs
Cost per incident
Total cost of support
Cost of downtime

36. Knowledge management
• Known errors at deployment
• Link articles to problems
Automation
End-to-end linking
• Link incidents, problems and requests
to changes and releases
Reliable deployment
• Continuous integration, continuous
delivery and continuous deployment
Testing
• Support requirements
Proactive monitoring
• Visibility to support

37. Sharing
Views
Goals Priorities
Process Knowledge
systems
Communication
Codebase
Toolsets
Ownership
Success
Workflow
Learnings
Tasks &
projects
Pages &
files
Messages &
calls
Requests &
SLAs
Code &
reviews
Builds, Tests &
Deployment

38. More about DevOps and Atlassian
https://www.atlassian.com/devops/

39. Thanks!