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.
Upcoming SlideShare
What to Upload to SlideShare
Next
Download to read offline and view in fullscreen.

3

Share

Download to read offline

Four Keys to Efficient DevOps

Download to read offline

Every DevOps implementation is unique, but certain challenges are the same. Establishing fast feedback loops, formulating a better definition of done, and anticipating technical gaps to delivery are all milestones to transformation.

In this session, our panel of experts will share their experiences in DevOps transformation. Learn how to:
-Improve your team’s definition of done to cut down rework
-Identify automation gaps that lead to later holding patterns
-Inject fast feedback to catch bugs as early as possible
-Establish autonomy and ownership over winning customer-focused experiences

Related Books

Free with a 30 day trial from Scribd

See all

Related Audiobooks

Free with a 30 day trial from Scribd

See all

Four Keys to Efficient DevOps

  1. 1. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile 4 Keys to Efficient DevOps Patterns to Enable Transformation in Enterprise Development Web: perfectomobile.com Twitter: @perfectomobile
  2. 2. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile ● Session is being recorded ● Presentation will be shared ● Questions and conversation ○ Twitter: #DevOpsMilestones ○ WebEx chat panel ○ Q&A at the end of the webinar Housekeeping
  3. 3. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Today’s Panel Carlo Cadet Director, Product Marketing & Evangelism Perfecto Tzvika Shahaf Director, Product Management Perfecto Sean Williams Principal Software Engineer Prism Tech Studios James Brown Director, Enterprise Solutions VisionIT Raj Subramanian Senior UI Automation Engineer CSG International
  4. 4. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile What We’ll Cover 1. Improving your team’s Definition of Done 2. Addressing automation gaps early 3. Fast feedback in your pipelines 4. Autonomy for Customer-focused Experiences
  5. 5. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Poll: Where are you on your DevOps Journey? ● We fully embrace DevOps across our organization ● Many teams have re-organized and built efficient tool chains ● There are a few pilots underway to implement DevOps ● We talk about DevOps a lot, but haven’t quite started ● Not going there
  6. 6. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Improving Your Team’s Definition of Done 4 Milestones on the Path to Efficient DevOps Patterns to Enable Transformation in Enterprise Development
  7. 7. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Predictable flow ● Clock speed mismatch ○ Business needs to innovate ○ Development needs to deliver ● Delivering predictably ○ Establish cadence that business can rely on ● The “real” flow of our teams ○ Leftover work impacts next sprint’s bandwidth ○ Confidence in go / no-go Waterfall (months) Agile (weeks) DevOps (days)
  8. 8. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile What goes into a Definition of Done? Constructing: ● Common criteria ● Previous RCA on re-work ● Go/no-go blockers Improving: ● Retros: rejected work ● Minimize tech debt ● Better DoD fit per story https://www.scrumalliance.org/community/articles/2008/september/definition-of-done-a-reference
  9. 9. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Examples of tailoring Definition of Done ● Code produced (all ‘to do’ items in code completed) ● Built without errors ● Unit tests written and passed ● Peer reviewed and corrected ● Deployed to system test environment and passed system tests ● Passed UAT (User Acceptance Testing) ● Any build/deployment/configuration changes documented and communicated Perfecto: ‘Done is DONE: (partial list) ● Builds without warnings/lint? ● Automated tests ● Feature flags ● Peer code review ● Acceptance / UI review ● Feature documentation ● Code samples DoD ~ AC =Story Design & code Code pushed / JIRA updated
  10. 10. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile
  11. 11. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Addressing Automation Gaps Early 4 Milestones on the Path to Efficient DevOps Patterns to Enable Transformation in Enterprise Development
  12. 12. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Areas of Automation “gaps” ● CI ● Device/Simulators ● Maintenance ● Test Coverage ● Performance From the Digital Quality Handbook (pg. 70): ● Android 6: Fingerprint ● Android 7: Split screen ● iOS 9: 3D Touch ● iOS 10: Voice commands bit.ly/digqual
  13. 13. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Why to find them early? The Key is... ● Quick Feedback ● Better Visibility ● Building “Trust” for the automated tests
  14. 14. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile How to find them early? ● Plan automation as a team ○ What areas need to be automated? ○ What areas are more stable? ○ Cost vs Value ● Treat automation as separate stories/requirements ● Do estimation with “buffer time” in mind
  15. 15. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Fast Feedback in Your Pipelines 4 Milestones on the Path to Efficient DevOps Patterns to Enable Transformation in Enterprise Development
  16. 16. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Enhanced Quality Visibility Throughout Your Pipeline
  17. 17. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Meet Velocity Release Goals Increase efficiency & Optimize UX Focus more on feature development and validation, less on analysis Empower continuous quality while eliminating flaky tests for faster cycles
  18. 18. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Tools & processes must deliver value
  19. 19. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Shortening the Feedback Loop cycle in CI
  20. 20. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile My Build failed – but why?
  21. 21. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile My Build failed – but why?
  22. 22. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Autonomy for Customer-focused Experiences 4 Milestones on the Path to Efficient DevOps Patterns to Enable Transformation in Enterprise Development
  23. 23. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Autonomy Process Autonomy Cultural Autonomy
  24. 24. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Process Autonomy Automated Builds and Deployments Dev,QA and Staging Environments Documentation … and more
  25. 25. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Cultural Autonomy Empower your team to do what’s best for the end user ● Share end user data ● Share business goals and priorities ● Nurture an owner mindset
  26. 26. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Takeaway: The definition of done is a fundamental communication of success, both within the DevOps team and out to the larger enterprise. Build “Trust” and “Respect” the automated tests Necessity of quality visibility across the entire pipeline to support timely decision making Teams are more motivated and make better decisions when development teams stay close to the real customer experience
  27. 27. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile What We’ve Covered 1. Improving your team’s Definition of Done 2. Addressing automation gaps early 3. Fast feedback in your pipelines 4. Autonomy for Customer-focused Experiences
  28. 28. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Q&A (open ended question about “what have you seen works?”)
  29. 29. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Additional Resources ● List of links from the group (1 per) ● The Path to Releasing Confidently in DevOps: http://info.perfectomobile.com/release-confidently-in-devops.html ● Peopleware: Productive Projects and Teams: https://www.amazon.com/Peopleware-Productive-Projects-Teams- 3rd/dp/0321934113/
  30. 30. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Appendix
  31. 31. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Abstract Title: 4 Milestones on the Path to Efficient DevOps How many new initiatives does it take to transform an organization? Answer: as many as it takes to drive change. Every DevOps implementation is unique but certain challenges are the same. In our experience with enterprises, establishing fast feedback loops over your code commits, formulating a better definition of done on features, anticipating technical gaps to delivery, and fostering a culture of autonomy are milestones to transformation. In this session, Perfecto Developer Advocate Paul Bruce will host a dialog with a panel of development experts, sharing their experiences in DevOps transformation. We will discuss: · Improving your team’s definition of done to cut down rework · Identify automation gaps in planning that lead to later holding patterns · Inject fast feedback throughout your pipelines to catch bugs as early as possible · Establish autonomy and ownership over winning customer-focused experiences
  32. 32. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile What you don’t know...hurts. Examples of automation “gaps”... ● Existing functionality ○ Appium on iOS 10 ○ Low platform coverage in CI ● New features ○ Hardware dependencies (camera, location, BLE) ○ Test coverage in DoD [Panelist attests, offer example] From the Digital Quality Handbook (pg. 70): ● Android 6: Fingerprint ● Android 7: Split screen ● iOS 9: 3D Touch ● iOS 10: Voice commands bit.ly/digqual
  33. 33. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile Who’s in the planning room? ● Idea in backlog (PM / PO) ● Prioritization / grooming (PO) ● Defining (PO / dev) ● Scoping (dev / test / ops) ● Estimation (dev / test / ops) ● Signoff (all) [panelist example of who’s in planning sessions]
  34. 34. 4 Milestones on the Path to Efficient DevOps Web: perfectomobile.com Twitter: @perfectomobile A tale of two features [panelist] ● Feature 1: didn’t have the right people in the room ○ Subsequently, later automation was delayed due to technical gap ○ Impact on business was x ● Feature 2: all members in planning (DevOps) ○ Planning included domain knowledge of all delivery aspects ○ Potential gaps in automation were identified early ○ Estimation included this work ○ Delivery dates were met
  • eayoub

    Oct. 25, 2018
  • ErShivaKShrestha

    Jun. 20, 2017
  • giovannimaggini

    Jun. 19, 2017

Every DevOps implementation is unique, but certain challenges are the same. Establishing fast feedback loops, formulating a better definition of done, and anticipating technical gaps to delivery are all milestones to transformation. In this session, our panel of experts will share their experiences in DevOps transformation. Learn how to: -Improve your team’s definition of done to cut down rework -Identify automation gaps that lead to later holding patterns -Inject fast feedback to catch bugs as early as possible -Establish autonomy and ownership over winning customer-focused experiences

Views

Total views

508

On Slideshare

0

From embeds

0

Number of embeds

2

Actions

Downloads

37

Shares

0

Comments

0

Likes

3

×