Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Navvia's DevOps journey

773 views

Published on

Navvia is always looking for ways to improve how we do things and we’ve come to see DevOps as our compass on the road to continual improvement. However, DevOps means different things to different people.

To our company, it has become the rallying cry for organizational change. It is the standard that leads us on a path towards better alignment across teams, enhanced agility, higher quality and the elimination of waste.

What you will learn:
- Why Navvia embarked on DevOps
- An overview of DevOps including common misconceptions
- A case study entitled “a tale of two apps”
- How Navvia is implementing DevOps
- What we’ve learned so far

It’s an exciting journey with the destination being improved customer experience, higher rates of innovation and a faster path to business value.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Navvia's DevOps journey

  1. 1. Navvia’s DevOps Journey Evolution – not revolution
  2. 2. DevOps – Evolution not revolution Cecile Hurley Customer Success Manager churley@navvia.com Twitter: @cecile_hurley Welcome to the Webinar!
  3. 3. DevOps – Evolution not revolution 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
  4. 4. DevOps – Evolution not revolution Software & Services to design & document IT and Business Processes
  5. 5. DevOps – Evolution not revolution Recognized by… Used by…
  6. 6. DevOps – Evolution not revolution 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
  7. 7. DevOps – Evolution not revolution Housekeeping @mainville
  8. 8. DevOps – Evolution not revolution • 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
  9. 9. DevOps – Evolution not revolution What makes Navvia qualified to speak? @mainville
  10. 10. DevOps – Evolution not revolution We’re living it… @mainville
  11. 11. DevOps – Evolution not revolution • 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
  12. 12. DevOps – Evolution not revolution A faster path to business value DevOps The rallying cry for organizational change @mainville
  13. 13. DevOps – Evolution not revolution What does DevOps mean to you? It’s your turn to talk J @mainville
  14. 14. DevOps – Evolution not revolution DevOps is a misnomer It extends well beyond Development and Operations But BizDevOpsSupCust is too much of a mouthful… Defining DevOps @mainville
  15. 15. DevOps – Evolution not revolution • 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
  16. 16. DevOps – Evolution not revolution 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
  17. 17. DevOps – Evolution not revolution Defining DevOps System of Record System of Innovation Source: Gartner DevOps can co-exist in your environment Bimodal IT DevOps Stabilization & Maintenance @mainville
  18. 18. DevOps – Evolution not revolution 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
  19. 19. DevOps – Evolution not revolution 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
  20. 20. DevOps – Evolution not revolution DevOps is not new DevOps evolved from well known disciplines such as ESM, Lean, Agile… @mainville
  21. 21. DevOps – Evolution not revolution DevOps is predicated on Organizational Maturity Encompassing people, process and technology @mainville
  22. 22. DevOps – Evolution not revolution 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
  23. 23. DevOps – Evolution not revolution When the lightbulb came on for me! A tale of two DevOps applications Defining DevOps @mainville
  24. 24. DevOps – Evolution not revolution A tale of two “DevOps” apps Online meeting application Team collaboration application @mainville
  25. 25. DevOps – Evolution not revolution 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
  26. 26. DevOps – Evolution not revolution 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
  27. 27. DevOps – Evolution not revolution How are we implementing DevOps @mainville
  28. 28. DevOps – Evolution not revolution 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
  29. 29. DevOps – Evolution not revolution Step 1 – Creating the climate for change @mainville
  30. 30. DevOps – Evolution not revolution 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
  31. 31. DevOps – Evolution not revolution Step 2 – Re-evaluate everything we do High Priority Medium Priority Medium Priority Low Priority High client impact Easy Difficult Lower client impact @mainville
  32. 32. DevOps – Evolution not revolution 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
  33. 33. DevOps – Evolution not revolution 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
  34. 34. DevOps – Evolution not revolution 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
  35. 35. DevOps – Evolution not revolution Step 4– Sustainability and continual improvement @mainville
  36. 36. DevOps – Evolution not revolution DevOps isn’t new folks! It evolved from other disciplines – with a renewed focus on organization @mainville
  37. 37. DevOps – Evolution not revolution 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
  38. 38. Thank-you DevOps – Evolution not revolution @mainville
  39. 39. NAVVIA.COM/TRIAL 15 business days – no obligation Navvia Process Designer START FREE TRIAL

×