asas 2015 - benito de miranda

DevOps for Architects- Benito de Miranda

1

Everyone :-)

Benito de MirandaBusiness/Information Analyst, Scrum stuff, DevOps stuff, Coach, Trainer

06 304 3317

[email protected]

nl.linkedin.com/in/benitodemiranda

@bdemiranda, @devopsNL

We know the current system is not working. We know there must be a better way.

So what are we waiting for?

4

Painful outages

5

Poor incremental value

6

Perception

of

slow

IT

7

Us -vs- Them

So is DevOps THE answer? 9

BizDevOps

DevQaOps

SecOps

DevSecOps

BusQaSecNetOps

So what is DevOps?

DevOps is about Developers and Operations people working collaboratively to release software to users. – Dave Farley

10

Highly effective, daily collaboration between software developers and IT Operations people to produce relevant, working systems. – Matthew Skelton

DevOps means a culture where Developers and Web operations Engineers communicate and work together, as opposed to a siloed organization where developers trow code over the wall to operations and expect web operations engineers to make sure it runs in production. – Anna ShipmanI’m afraid I’m a tester…so have pretty much no idea what DevOps is about. – Amy Phillips

DevOps is an alternate model for the creation of business value from the software development life-cycle that encompasses a product-centric view across the entire product life-cycle and recognizes the value in close collaboration, experimentation and rapid feedback. - TheOpsMgr

DevOps is the practice of operations and development engineers participating together in the entire service lifecycle, from design through the development process to production support. – Theagileadmin.com

So what is DevOps? 11

Underpinning DevOps is the philosophy found in the Agile Manifesto, which emphasizes people (and culture) and seeks to improve collaboration between operations and development teams. DevOps implementers also attempt to better utilize technology, especially automation tools that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective. - Gartner

DevOps (a portmanteau of "development" and "operations") is a software development method that stresses communication, collaboration and integration between software developers and Information Technology(IT) professionals. DevOps is a response to the interdependence of software development and IT operations. - Wikipedia

DevOps is a set of practices to reduce the time between committing a change to a system and the change being placed into normal production, while ensuring high quality.- Bass, Weber, Zhu

So what is DevOps?

DevOps is... an umbrella concept that refers to anything that smoothens out the interaction between development and operations.- Damon Edwards

DevOps typically refers to the emerging professional movement that advocates a collaborative working relationship between Development and IT Operations, resulting in the fast flow of planned work (i.e., high deploy rates), while simultaneously increasing the reliability, stability, resilience and security of the production environment. -Gene Kim

12

DevOps models 13

CAMS

CALMS

CALMSS

Gene Kim

John Willis Damon Edwards Forrester research Patrick Dubois

DevOps shared points

DevOps▪ DevOps aims to help the business win!▪ Optimize the whole (business to customer = value chain) and not the individual

silos▪ Collaboration & optimization across the whole organization▪ Automation helps but is not the focus▪ Culture is important▪ Theoretical foundations (Deming, TPS, Lean, ToC)▪ DevOps is a journey, not an end-state

DevOps Light ▪ Focus only on Dev & Ops collaboration, metrics, tools, etc.

14

15

Deming• Father of Quality • System of Profound Knowledge

Lean Software Development (Poppendieck) Theory of Constraints (Eliyahu Goldratt) Improving something anywhere not at the constraint is an illusion.Eliminat

e waste

Amplify learning

Decide as late

as possibl

e

Deliver as fast

as possibl

e

Empower the team

Build quality

in

See the whole

Toyota Production System (Toyoda, Ohno, Shingo)• Just-in-Time (JIT), Pull, Eliminate waste • Basis for Lean & Kanban

Culture – the way you think, act & interact 16

▪ Empowerment: can I stop the delivery without blame, no individual victims

▪ Responsibility: fail often & early, collective responsibility, early focus on quality

▪ Teamwork: no silo’s, never passing known defects, no us -vs- them

▪ Learn: continuous improvement, different look on ‘learning’, brown paper bag sessions

▪ Trust: being successful means trust in every aspect of the organization, more trust = happier employees

Tooling 17

“It’s the way you use technology that makes the difference”

Areas Collaboration, Planning, Issue Tracking, Monitoring, Configuration Management, Source Control, Environments, Continuous Integration, Deployment.

Be critical and keep an open mind▪ Are the teams ready for tools? ▪ Technology must contribute to “continuous improvement” ▪ Essential: sharing knowledge, ownership, responsibility and empowerment

Trends 19

In 2016 about 25% of 2000 global IT companies will adopt DevOps. Tools associated with DevOps toolchain will have a market of $2.3 billion.

Trends 20

▪ High-performing IT organizations experience 60 times fewer failures and recover from failure 168 times faster than their lower-performing peers. They also deploy 30 times more frequently with 200 times shorter lead times.

▪ It doesn’t matter if your apps are greenfield, brownfield or legacy - as long as they are architected with testability and deployability in mind, high performance is achievable.

▪ Deployment pain can tell you a lot about your IT performance.

Cloud infrastructure acts as a backbone for continuous integration, deployment and release that is supported by DevOps. The survey also states that, DevOps adoption is expected to increase 66% in 2015 from 6% in 2014.

Of the respondents who set business-related goals, 66% set a goal of increasing customer satisfaction. With the potential to make software rollouts more agile, a DevOps plan can reduce delays for customers and solve problems more quickly, as long as a team is willing to embrace the new strategy.

Architect in a DevOps world 21

The best architectures, requirements, and designs emerge from self-organizing teams (Agile Manifesto).



Learn to program so you can experiment with architecture as code (and more…).

Don’t rely only on quality and security posters. Improvements must be made visible in the daily work.

Focus on the team(s) you’re working with, don’t let them wait.

Watch out for waste (motion, transport, waiting) when demanding to approve changes/documents.

Try to experiment, resistance is ok but keep an open mind.

Facilitate & coach the team members.

Take a look at this new role “Service Owner”.

Think about where your work adds value to the overall flow of the system.

Architect in a DevOps world 22

Help building a culture of trust & continuous improvement.



Plan & design for change as software evolves.

Continuous deployment can have a large impact on the architecture.

Local optimizations are not always a way to solve the customer problem. Think end-to-end.

Architecture is part of teamwork.

Learn Japanese: Gemba, Kanban, Kaizen, Kata, Muda, Mura, Muri, Poka-yoke.

What is your vision and is it clear for all your colleagues?

Short feedback loops can also help to improve the architecture.

You can help with tackling technical debt by adding architectural epics in the backlog.

Start tomorrow 23

Put your architecture on the wall and make sure that it shows the added value for the customer.



Keep DevOps simple & fun.

Really sit together with the teams you’re working with.

What would you change if you had a magic wand?

Make your work visible with a Kanban board.

Draw simple pictures and always keep a sharp focus on the customer value.

You need slack time, otherwise WIP will get stuck in the system

Some key thinkers

Andrew Schafer @littleideaBridget Kromhout @bridgetkromhoutDamon Edward @damonedwardsGene Kim @realgenekimHeather Mickman @hmmickmanHelen Beal @helenranger4Jesse Robbins @jesserobbinsJez Humble @jezhumbleJohn Allspaw @allspawJohn Willis @botchagalupePatrick DuBois @patrickduboisRosalind Radcliffe @RosalindRadTerri Potts @Raytheon

24

25Thank you! Questions? Always, Anytime!

The Secret of Change Is to Focus All of Your Energy, Not on Fighting the Old, But on Building the New. - Dan Millman

26

www.ordina.nl