Navvia's DevOps journey

Navvia’s DevOps Journey
Evolution – not revolution

DevOps – Evolution not revolution
Cecile Hurley
Customer Success Manager
churley@navvia.com
Twitter: @cecile_hurley
Welcome to the Webinar!

Housekeeping
Let’s keep this interactive!
• Use the control panel to ask questions
• Can you see & hear us?
• enter your name & city to confirm
Type Your Questions Here

Software & Services
to design & document IT and Business Processes

Recognized by… Used by…

What is Navvia
Navvia is a Powerful and easy-to-use tool to
design & document processes
RACI
Auto generate and synchronize over 17
different process artifacts
Process Guides
Technical Requirements
And more…
Create

Housekeeping
@mainville

• Why our organization embarked on DevOps
• Defining DevOps
• Case Study: A tale of two apps
• How we are implementing DevOps (building blocks)
• Summary / Q&A
Agenda
@mainville

What makes Navvia qualified to speak?
@mainville

We’re living it…
@mainville

• Better alignment across teams
• From product management through to support
• Enhanced agility / improved time-to-market
• Continuously reviewing customer needs
• Smaller & more frequent releases – each adding value
• Evaluating success / not afraid to change course
• Higher quality
• Better capabilities with fewer defects / more automation
• All predicated on adding value / removing waste
• To our customers and our company
I’m living it…
Our goal - A faster path to business value
@mainville

A faster path to business value
DevOps
The rallying cry for organizational change
@mainville

What does DevOps mean to you?
It’s your turn to talk J
@mainville

DevOps is a misnomer
It extends well beyond Development and Operations
But BizDevOpsSupCust is too much of a mouthful…
Defining DevOps
@mainville

• It is a skill, position or department
• DevOps is a technology
• It’s all about automation
• It’s about “x” deployments a day
• It’s about learning a new language
• It’s only for modern tools / developers
• DevOps clashes with processes / ITIL
Defining DevOps
There are many misconceptions
• It’s a silver bullet
• DevOps is new
• DevOps doesn’t apply to us
• We don’t need DevOps, we do Agile
• DevOps only relates to development
• Big bang is best – all or nothing
• It means no planning – just do it
Source:
• Smit Patel www.scriptrock.com/blog/devops-myths
• Peter Measey www.computerweekly.com/opinion/The-top-10-myths-about-agile-development
@mainville

Defining DevOps
Source: DevOps ReferenceArchitecture, Source: IBM
Steer
Develop
/ Test
Deploy
Operate
DevOps
Continuous Business
Planning
Collaborative
Development
Continuous
Testing
Continuous Release
& Deployment
Continuous
Monitoring
Continuous Customer
Feedback &
Optimization
Continuous
Feedback
@mainville

Defining DevOps
System of Record System of Innovation
Source: Gartner
DevOps can co-exist in your environment
Bimodal IT DevOps
Stabilization &
Maintenance
@mainville

Defining DevOps
You can practice DevOps
with the tools you have
No tool(s) will turn you into
a DevOps shop
DevOps is a practice – a discipline
@mainville

Defining DevOps
And there is a lot of hype!
Source: Hype Cycle for Application Development, July 2015 - Gartner
DevOps is at the top of the Gartner Hype Cycle
@mainville

DevOps is not new
DevOps evolved from well known disciplines such as ESM, Lean, Agile…
@mainville

DevOps is predicated on Organizational Maturity
Encompassing people, process and technology
@mainville

DevOps is predicated on organizational maturity
• How do we define and document the business requirements and
outcomes?
• How do teams collaborate and what tools support collaboration?
• What are the processes and tools to define and manage work?
• What processes and tools do we need to managesource code?
• How do we automatethe build, testing and deployment of code?
• How do we ensure things are working in production?
• What processes are in place to listen to the voice of the
customer?
@mainville

When the lightbulb came on for me!
A tale of two DevOps applications
Defining DevOps
@mainville

A tale of two “DevOps” apps
Online meeting application Team collaboration application
@mainville

A tale of two “DevOps” apps
Online meeting application
Team collaboration application
• UI seems to change at random
• Previously working functionality breaks
• Different behavior across platforms
• Poor support / help
• Zero advance warning or communication
• Plenty of advanced communication
• Excellent reliability
• No surprises
• Built-innotifications,walkthroughs and help
• Excellent customer feedback program
@mainville

Lessons learned
Online meeting application
Questions I would ask the team…
• What drove the changes?
• The app used to work great, lots of change with little
improvement to functionality
• Why is the application so unstable?
• Was there a focus on functionality and speed over quality?
• Was user experience considered?
• The app worked differently from day to day
• What are the broader ramifications of all this disruption?
• We openly complained to anyonewho would listen
@mainville

How are we implementing DevOps
@mainville

Step 1 – Creating the climate for change
• Articulate the vision
• Improve value, eliminate wasteand improve time-to-market
• Emphasize the why
• “Start With Why – How Great Leaders Inspire Everyone to
Take Action” – Simon Sinek
• Collaborate on the tactical approach
• Fosters buy-in and support
• Give permission to fail
• As long as you figure out what went wrong, fix it and identify
ways to prevent it from happening again
• Communicate, communicate and communicate
@mainville

Step 1 – Creating the climate for change
@mainville

Step 2 – Re-evaluate everything we do
• We looked at how we were organized
• Remove duplication and streamline tasks
• We looked at all our relevant processes
• Simplify work and eliminate waste
• Improve time-to-market, quality and satisfaction
• We looked at how we communicate internally
• Where does communication breakdown / add complexity
• We evaluated our tools
• With goal of improving automation and efficiency
@mainville

Step 2 – Re-evaluate everything we do
High
Priority
Medium
Priority
Medium
Priority
Low
Priority
High client impact
Easy Difficult
Lower client impact
@mainville

Step 3– Looked for ways to automate
• We are starting with three specific areas
• Requirements Management
• Vision, strategy, requirements and roadmap
• Everyone on same page
• Automated testing
• Automate the mundane to improve efficiency
• User Support
• Create in-line manuals and guided walk-throughs
@mainville

Step 3– Looked for ways to automate
Aha! Telerik Test Suite Inline Manual
User Support
• Interactive and contextual help
• Guided walkthroughs
• Analyze user behavior for CSI
• Engage our users
Automated Testing
• Visual recorder for UI tests
• Cross Browser testing
• Build, chain and reuse scripts
• Run tests concurrently in multiple environments
• Minimize need for developer involvement
Requirements Management
• Establish vision
• Establish and track goals
• Prioritize features and releases
• Track business value
• Collaborate
@mainville

Step 4– Sustainability and continual improvement
Don’t settleDon’t take our eye off the prize
• Remain focused
• Constantly communicate the vision
• Frequent measurements
• Quality, time-to-market and customer satisfaction
• Frequent course corrections
• Don’t be afraid to shake things up
• Throw away what isn’t working
• Continued buy-in and adoption
• Hold folks accountable
• Are you on the bus? (Good to Great – James Collins)
@mainville

Step 4– Sustainability and continual improvement
@mainville

DevOps isn’t new folks!
It evolved from other disciplines – with a renewed focus on organization
@mainville

Takeaways
What we’ve learned about DevOps
• It’s a lot of what you already know!
• Small changes, each adding value – not afraid to change course
• It is a cross-functional discipline that spans the organization
• It is a scalable approach suited to organizations of any size
• It’s not ”all or nothing” – it can apply to one app or all projects
• It requires organizational maturity and defined process
• Automation and tools will help drive velocity – but not without
process!
• It requires focus, discipline and continual improvement
@mainville

Thank-you
DevOps – Evolution not revolution @mainville

NAVVIA.COM/TRIAL
15 business days – no obligation
Navvia Process Designer
START FREE TRIAL

Navvia's DevOps journey

More Related Content

What's hot

Viewers also liked

Similar to Navvia's DevOps journey

More from Navvia

Recently uploaded

Navvia's DevOps journey