Why DevOps questions, discussions and visions can be so confusing and why that might be a good thing...to talk about.

1. DevOps Rubik's Cube of Confusion
Paul Peissner
DevOps Enthusiast

2. DevOps questions…consider the Evolution of a vision…

3. 3
HOW
Systems-driven DevOps Visions and Discussions
Start with WHY!
And address the CORE questions and issues related to…
the external Market and internal Processes/Culture/Tools for the best Business Outcomes!
HOW
WHAT
WHY
Simon Sinek’s
Golden Circle

4. I can see (perceive) it…
- Silo vs. System concept
I see ways for you to do
better via feedback & data
- System improvements
via visibility, feedback
and data-driven decisions
Systems Thinking
The 3 Ways: The principles underpinning DevOps
Blog by Gene Kim
Culture Of Continual Experimentation And Learning
With a common vision,
everyone can see and is
empowered to adapt!
- Mastery and adaptability
- Continuous exploring,
risk/learning tolerance…
The1stWay:The2ndWay:The3rdWay:
Amplify Feedback Loops

5. DevOps questions…consider the Who and What…

6. DevOps Layers of Enterprise-IT Discussions
People
& Culture
Process
& Flows
Products,
Technologies
& Tools
Conversations gravitate towards and blend 3 different areas that impact adoption

7. Practitioners
(Engineer, etc..)
Managers &
Team leaders
Executives
Line of Bus.
DevOps Roles in Enterprise-IT Discussions
Conversations have very different focuses depending on the role/responsibility

8. Layers & Roles in Enterprise DevOps
Managers &
Team leaders
Executives &
Line of Bus.
Practitioners
(Engineer, etc..)
People
& Culture
Process
& Flows
Products,
Technologies
& Tools

9. DevOps Stages in Enterprise Adoption
Getting Started
Getting Buy-in
Pulling Together
Aligning for
Business Outcomes
AgileTechnologies & ToolsCollaboration

10. Example…
DevOps questions…consider a Dev tool challenge…

11. • Natively incorporates your tools/technologies/methodologies
• Common user experience with reusable project templates
• Search integration for sharing code, artifacts and docs
• Any process, location, project type, governance…
• Lifecycle traceability (code indexing and mapping)
• Workflow extensions and automation integrations
CollabNet’s Eco-System – Open, Friendly, Adaptable…
Developer & Code Mgt
for Enterprise Project flows
to support Business Outcomes

12. Subversion
and/or Git
Junit/Sonar/
Cobertura
CollabNet Adapts to Dev and DevOps Agendas
Example of CollabNet‘s TeamForge adaptability...
Collaboration - Traceability
Continuous Improvement
Desired Business Outcomes
Agile or Waterfall or Srcumfall or…
IT Silos or DevOps Pilots, or Hybrid IT , or…
Seasons of Innovation/Optimization/Transitions
Developer & Code Mgt for Enterprise Project flows
Ops

13. DevOps questions…consider 4 defining discussions…

14. DevOps Defining Discussions
- Cultural Transformation
1. HOW – Provides logical process guidelines – Efficiency & skills mastery
2. WHAT – Empowers ownership and innovation – Effectiveness & collaboration
3. WHY – Evokes emotion and vision loyalty – Motivation & significance
Types of Work
- Business vs. Internal
- Planned vs. Un-planned
Types of Methodologies
- Agile vs. Waterfall (Scrumfall)
- Scum - Kanban - Lean…

15. 1. Change-inevitable evolutions - Software, Tech, Methods, Processes, Markets…
2. Change-resistant (org) tendencies - Routine, legacy, policies, old paradigms…
3. Change-balancing tensions - Business-driven new potential vs. needed stability
Managing Transitions
- Supporting Established and Emerging teams
- Moving “power & control” without alienating
- Seasons of innovation vs. seasons of optimization
Defining Core values
- Setting shared goals and rewards
- Creating integrated processes
- Empower social leaders & owners
DevOps Defining Discussions
- Balancing Change & Stability

16. 1. Corporate Vision – Value in Software, Agile and development to help drive business outcomes
2. Team Leader – Commitment to team mastery and shared Corp. goals with best-practices
3. Participants – ‘High-value” role (significance) and new skills that benefit their career path
Innovation and Improvements
- Any empowered team member can contribute
- Process and technology changes are welcome
Reward Systems
- Definition of Done needs a discussion
- How do you pay for business success
DevOps Defining Discussions
- Getting Community Buy-in

17. Corporate Effort
Org support needed
Business ROI
Business benefits
Initial effortInitial effort
Pilot
Pilot
Growth Growth
Standardization Standardization
1) Agile IT culture enablement
– Open Source & Tools, Collaboration, EDU. & Vision
2) IT process alignment
– Integrations, Training, Process & Standardization
3) IT performance optimization
– Multi-team efforts, Coaching, Simplify Platforms/System flows
4) Business Value and/or Business Outcome
- Dev Code re-use, project templates, process optimization …
- Ops automation, monitoring, standardization & simplification…
DevOps Defining Discussions
- Setting Adoption Expectations

18. DevOps summary…work the puzzle one side at a time

19. Solving the DevOps Rubik's Cube
The Evolving vision…The Why…
Everyone’s Why, What and How… Managing Expectations and Transitions
Practitioner Team Leader Exec / Bus Leader
Tech/ToolsProcessCulture

20. Questions
Paul Peissner
DevOps Enthusiast