The increasing importance of our tooling, the rely on their ability to automate and potential damage when they don’t work properly should make us think about repositioning your tooling strategy. Nowadays tools are an essential part and getting more important every day for delivering high quality productivity, but why are we still handle them as non critical parts?
We can all agree that it’s seems such simple thing selecting your favourite tools, but that it’s actually a complex undertaking, by avoiding pitfalls and select your Swiss knife. Most companies are still struggling to find their best fitted tools for their organisation, processes and technology stack, caused by various legitimate reasons, but end up with no beneficial use or even not used at all. Think that we all recognize this situation?
During this presentation I will take you on the journey of defining and refining your end goal, effectively learn from the things that matter and define your Enterprise Tooling strategy. We will explore some typical pitfalls and practices that help you to identify their strengths and opportunities for your organisation to leverage from. After all we want to get productive as early as possible.
2. @DevMonOps
WHO’S THAT GUY
•DevOps consultant with great passion
for Architecture and Automation
Tooling
•15+ years working experience with
automating IT
•Father of three kids
•Full time Tooling Geek J
Ø Automation
Ø Monitoring,tasted them all
Ø Predictive Analytics
Ø Infrastructure-as-Code
Arnold
Van Wijnbergen
Principal Consultant @
4. #DevOpsDays @DevMonOps
This talk is not about tool preferences,
nor popular technology (as most of you already know),
just a rich set of experiences to share
5. #DevOpsDays @DevMonOps
üSetting the scene ”Are Tools the Answer”
üThe Radical Evolutionof the Tooling market
ü Define your Tooling Strategy
üCommon Pitfalls that will ruin your Tooling Strategy
üSummary - key takeaways
Topic outline
16. #DevOpsDays @DevMonOps
Any organization that designs a system
(defined broadly) will produce a design
whose structure is a copy of the
organization's communication structure.
Conway's law comes in
Reference
https://en.wikipedia.org/wiki/Conway%27s_law
19. #DevOpsDays @DevMonOps
they deliver crucial automation,support and
housekeeping capabilities,
from the manufactory till software industry
Reference
Twitter@elonmusk,https://blog.coolblue.nl/pakketjesmachine
21. #DevOpsDays @DevMonOps
Market demand changed for IT automation tooling
from Best in Suite to Best in Breed and focuses on
flexibility of the solution
27. #DevOpsDays @DevMonOps
üStore enterprise Knowledge
üAct as a Proxy for the Enterprise processes
to activate and execute
üGenerate valuable Information about enterprise
assets
Business needs to fulfill
28. #DevOpsDays @DevMonOps
IT needs to fulfill
üStore everything underVersion control
üRepeatable & reliable process for software delivery
üAutomate handovers and repeatable tasks
üDeliver high quality releases to production
35. #DevOpsDays @DevMonOps
Dev Ops
Bus
“Toolchain is a set or combination
of tools that aid in the delivery,
development, and management of
applications throughout the
software development lifecycle, as
coordinated by an organisation with
goals to increase application
quality and resiliency,that
preferably uses DevOps practices“
Reference
https://en.wikipedia.org/wiki/DevOps_toolchain
36. #DevOpsDays @DevMonOps
“Toolchain is a set or combination
of tools that aid in the delivery,
development, and management of
applications throughout the
software development lifecycle, as
coordinated by an organisation with
goals to increase application
quality and resiliency,that
preferably uses DevOps practices“
Technology that
supports your
Toolchain
Use cases that
build the lifecycle
Objectives that
drives growth and
success
Important metrics
to improve
Reference
https://en.wikipedia.org/wiki/DevOps_toolchain
46. #DevOpsDays @DevMonOps
Observe the tools that teams like
and
drive adoption by innovationof your fellow teams
evolve by learning and adoption
47. #DevOpsDays @DevMonOps
Don’t forget education
& support
ü Introduce a Tooling
engineering team with correct
ownership
ü Smooth on-boarding with
supporting bootcamps
ü Self supporting FAQ,manuals
and examples
Reference
https://en.wikipedia.org/wiki/Grady_Booch
53. #DevOpsDays @DevMonOps
Don’t waste all the
interesting data
SHARE !!
Use operational data for
further
intelligent automation
leverage machine learning capabilities
triggers
RUNBOOK
RESPOND
INTERACT
NOTIFY
55. #DevOpsDays @DevMonOps
Technology push without adoption,
top-down approach for implementation,
Technology push from ivory tower,
no input from key users
1
59. #DevOpsDays @DevMonOps
üTooling strategy is an important accelerator.
üIdentify use cases,Tools are there to support the teams.
üFellow teams are important during tool selection, learn from them.
üTooling engineering team must unburden the product teams with
toolchain compliancy and maintenance work.
üTools are self-supportable and have easy approachable
documentation.
üTake benefits of the collected metrics to improve support and quality.
Summary - key takeaways