Agile and DevOps are both common buzzwords and lots of organizations are “doing” them. Implementing frameworks such as Scrum/Kanban sometimes can make changes within an area of the company, but instituting DevOps essentials such as continuous integration, continuous deployment, and continuous monitoring often require greater collaboration across teams in companies with functional structures. Find out how implementing Agile and DevOps practices at your organization can cause changes in mindsets, people, processes and tools, often leading to real organizational change and improved agility. After attending, listeners will leave with an understanding of the journeys we have seen to get there and the key drivers for a successful transformation.
Heidi Araya, BrightLogic, Agile Leader
Heidi is an Agile Coach and Trainer who has been working with remote teams since 1999. She aims to show teams and enterprises the value of a cohesive vision and mission, systems thinking, and self-organizing teams. An active member of the Agile community, she trains and speaks at events and conferences worldwide. With over 20 years of experience in software & technology in roles ranging from Agile Coach, Scrum Master, Product Owner, Project Manager, and Business Analyst, she brings her diverse background to develop companies improve business processes and create teams that deliver value to customers. Heidi is currently Agile Leader at PhishMe, Inc., the leading provider of threat management software for organizations concerned about human susceptibility to advanced targeted attacks.
https://www.linkedin.com/in/heidiaraya/
https://twitter.com/HeidiAraya ;
Esteban Garcia, Nebbia Technology, Infrastructure Architect
Esteban Garcia is the Founder and Chief Technologist of Nebbia Technology, a DevOps consulting and Azure-powered technology company. With almost 20 years of experience building enterprise software, Esteban has a passion for application lifecycle management, Azure, and DevOps best practices. He mentors, trains, and works closely with teams to help them implement automation and get the most out of their tools and processes. Esteban enjoys working with the software community, is the president of the Orlando .NET user group, and has been designated as a Microsoft Visual Studio ALM MVP. Read his blog at ALMGuide.com.
Strategies for Landing an Oracle DBA Job as a Fresher
DevOps - A catalyst to enterprise agility - Heidi Araya & Esteban Garcia
1. DevOps: A Catalyst for
Enterprise Agility
Esteban Garcia, Nebbia Technology
Heidi Araya, BrightLogic Group
Level: Intermediate
2. Esteban Garcia
2
§ DevOps Consultant
§ 20+ years in Software Development
§ Automates everything
§ Scrum Master
§ Microsoft MVP
§ Pluralsight Author
§ Agile Transformation Coach
§ 20+ years in technology
§ People over process
§ Systems thinker
§ Process improvement aficionado
Heidi Araya
BrightLogic Group
3. Introduction to UnicornCo
3
§ 40 Agile teams across several products and
initiatives
§ No continuous integration, not all SaaS
“our environments are unique and
complicated….”
§ Some automation for testing, but many
deployment processes are still manual
§ Environments are unstable or unavailable, and
not representative of Production environments
@EstebanFGarcia @HeidiAraya
4. Learning Objectives
§ Typical challenges implementing Agile and DevOps in
enterprise settings
§ Some ideas for overcoming typical challenges
§ Key drivers for a successful transformation
§ How can I get started?
4 @EstebanFGarcia @HeidiAraya
H
5. What initiatives do you have going on at work?
• Starting Agile Transformation
• Following Agile practices
• Agile mindset
• Starting DevOps
• Following DevOps practices
• DevOps team
6. Enterprise Agile and DevOps
Enterprise Agile –
§ Multiple agile teams working in conjunction on the same product,
project or initiative
§ Teams should own “develop to deployment” process end to end
(typically is not the case)
DevOps –
§ It’s about people, process & technology... not just tools & automation
6 @EstebanFGarcia @HeidiAraya
7. Why do we need this conversation?
§ Why does an Agile
organization need to
consider DevOps?
§ Why does Agile matter to
the DevOps people in the
room?
H +E
8. How are Agile & DevOps Similar?
8 @EstebanFGarcia @HeidiAraya
9. Released… not just potentially shippable
Scrum Guide:
§ “The heart of Scrum is a Sprint, … during which a
“Done”, useable, and potentially releasable
product Increment is created.”
§ “Purpose of each Sprint is to deliver Increments of
potentially releasable functionality …”
§ “Incremental deliveries of “Done” product ensure a
potentially useful version of working product
is always available.”
9 @EstebanFGarcia @HeidiAraya
10. Outcomes & principles over practices
10
§ Agile ... is about
delivering value to
customers frequently
to get feedback so
we can make better
decisions
§ DevOps … helps us
get releasable!
@EstebanFGarcia @HeidiAraya
H
12. Should we do Agile or DevOps First?
§ Start with the vision and
outcome desired
§ Create cross functional
teams around that vision
§ Develop the pipeline around
the vision and teams
E
13. Different priorities & lack of holistic view
§ Get everyone on the same page
around mission and vision
§ One list of organizational priorities
§ Align metrics to organizational and
team goals
§ Make visible & transparent to all
13 @EstebanFGarcia @HeidiAraya
14. Handoffs and manual processes waste time…
14 @EstebanFGarcia @HeidiAraya
§ …But actual
impact is not
visible!
§ Measure wait
times; share
the data with
leadership
15. Differing processes & tools
§ Dev and ops teams
collaborate together so that
the deployment solution is
aligned end to end
§ Dev and QA should
collaborate so that
environments meets QA’s
needs
15 @EstebanFGarcia @HeidiAraya
E
16. Building the wrong thing
16 @EstebanFGarcia @HeidiAraya
§ Long cycles encourage more
features to be requested/
added…
§ Don’t ask how much, ask
how little of a feature can be
delivered to customers
§ Don’t forget the feedback
loop!
H
17. Is anyone using that feature?
§ Don’t be a feature factory! Measure customer
usage patterns, errors, exceptions, performance
17 @EstebanFGarcia @HeidiAraya
H + E
18. Lack of good practices impedes delivery
§ Solution - Know where
code will reside
§ Solution - Create CI
build as early as
possible (build delivery
pipeline before start
coding, keep it up!)
18 @EstebanFGarcia @HeidiAraya
E
19. DevOps only practiced by a special team
§ DevOps is more than just
automation
§ DevOps can be enabled
by a team but practiced
by everyone
§ Start by focusing on
capabilities
E
20. Optimization by team, not for product
§ Have a multi-team
strategy to support a
scalable infrastructure
§ Assess branching
strategy, release pipelines
§ Make it easy to opt in to
automation
20 @EstebanFGarcia @HeidiAraya
H + E
21. We don’t know where to start...
§ Find the items that will bring
the biggest ROI
§ Dedicate people or time to
improving things little by little
§ Sprinkle DevOps fairy dust
amongst the teams
21 @EstebanFGarcia @HeidiAraya
H + E
23. What did we want to get out of the transformation?
§ Stay ahead of the
competition
§ Release features that
customers want
§ Happy, engaged people
J
H
24. Engage people in the process
§ Share the vision & desired outcomes
§ Use invitation to increase
engagement
§ Experiments – find willing early
adopters or internal advocates
§ Publicize wins
§ Ask detractors why it won’t work
25. Identify challenges and opportunities
§ Ask the teams to identify
their pain points and
opportunities
§ “If I had a magic wand,
what would you ask for?”
§ What would it take to get
to a “10”?
25 @EstebanFGarcia @HeidiAraya
26. Don’t ask permission to do the right thing
§ Code quality,
TDD, unit tests,
etc.
§ Prioritize tech
debt reduction
26 @EstebanFGarcia @HeidiAraya
H +E
27. Experiment
§ Try small experiments to
get buy in
§ Sprinkle cross-functional
teams with DevOps fairy
dust
27 @EstebanFGarcia @HeidiAraya
H + E
29. Cross-functional teams
§ Reduce handoffs
and dependencies
end to end
§ Measure & reduce
wait time where
handoffs can’t be
removed
29 @EstebanFGarcia @HeidiAraya
30. Communicate vision & mission
30 @EstebanFGarcia @HeidiAraya
§ Share the “why”
so teams
understand how
their work fits into
the bigger picture
H
32. Roadmap of problems to be solved
§ Roadmap of features & capabilities we are considering
§ Problems to be solved in the future
H
Strategic Theme 1
Q1 Quarterly Goal
Inc. paying users by 20%
Q2 Quarterly Goal Q3 Quarterly Goal Q4 Quarterly Goal
Features we are
considering
Features we are
considering
Features we are
considering
Features we are
considering
¯_( )_/¯
Unicorn locator
Subscription service
Pampered Unicorn
Send fairy dust to a friend
How can we…?
Upload Unicorn pics
Experiment 3
Chart inspiration: Jeff Gothelf
33. Feedback loops - customer
33 @EstebanFGarcia @HeidiAraya
E + H
Suggest a feature for UnicornCo.co
Integrate with Waze
Send fairy dust to a friend
Horn designer performance
improvements
Upload unicorn sighting pics
Auto add pics to map
according to GPS location
Upload unicorn sighting pics
* What’s coming?
* Releases
* Roadmap
34. Portfolio Transparency
§ Create Kanban board for all open initiatives
New Idea Business Case Approved Done –
90 days
In ProgressReady
Super
Secret idea
Unicorns on
Kilimanjaro
Upload
unicorn pics
Mobile alert
for active
sighting
Pampered
Unicorn
Upload pics
w GPS data
Integrate w
Waze
Horn
designer
upgrade
Send fairy
dust
Digital
magic
wands
Project Om
Display icon
for pics
35. Unified priorities & teams
§ One backlog
that includes
everything
needed for
that product
35 @EstebanFGarcia @HeidiAraya
36. Limit work in process (WIP)
§ Stop
starting,
start
finishing
§ Measure
throughput
36 @EstebanFGarcia @HeidiAraya
37. Outcomes over output
§ Don’t optimize for
keeping people
busy, optimize for
delivering value to
the customer
§ How does what
you’re working on
make your company
successful?
37 @EstebanFGarcia @HeidiAraya
Graphic:infoQ
Features 1, 2, 3
completed
Feature 1 Feature 2 Feature 3
Feature 1 Feature 2 Feature 3
38. Value stream mapping
§ Visualize entire workflow; look for bottlenecks, queues, opportunities for
improvement
38 @EstebanFGarcia @HeidiAraya
H
39. Focus on capabilities
• Continuous Delivery
• Architecture
• Product Process
• Lean management &
monitoring
42. Some time later…
42
§ 40 Agile teams working cohesively on the
most important things
§ Continuous Delivery and feedback from
customers
§ Fully automated and instrumented
§ Stable and automated environment
creation
@EstebanFGarcia @HeidiAraya
H + E
44. Agile Manifesto* & DevOps ... Meant to be together
1 Satisfy the customer through early and
continuous delivery of valuable software
2 Welcome changing requirements, even
late in development
3 Deliver working software frequently
4 Business people and developers work
together daily throughout the project
5 Build projects around motivated individuals
and trust them
6 Convey information face-to-face where
possible
7 Working software is the primary measure of
progress
8 Agile processes promote sustainable
development
9 Continuous attention to technical excellence and
good design enhances agility
10 Simplify: Maximize the amount of work not done
11 The best architectures, requirements, and
designs emerge from self-organizing teams
12 Team reflects, inspects and adapts to become
more effective
*12 principles
H
