An agile introduction to DevOps

Oct 3, 2016Download as pptx, pdf4 likes633 views

This document discusses DevOps principles and practices. It introduces DevOps as a culture emphasizing collaboration between software developers and IT professionals to automate software delivery and infrastructure changes. It then covers various DevOps topics like continuous integration, deployment, monitoring and product validation practices. It also provides examples of applications that could benefit from a DevOps pipeline and asks the reader to design such pipelines.

@gil_zilberfeld
An agile introduction
to DevOps

@gil_zilberfeld
Hello!
I AM GIL ZILBERFELD
www.gilzilberfeld.com
www.everydayunittesting.com
www.fastee.im
@gil_zilberfeld

@gil_zilberfeld
DevOps
A culture, movement or practice that
emphasizes the collaboration and
communication of both software
developers and other information-
technology professionals while
automating the process of software
delivery and infrastructure changes.

@gil_zilberfeld
The new stuff
New complex problems (Cloud, Serverless)
Environments all the way down
Governance and risk (“You can’t do that!”)
We trust automation
Better tools (Docker, Puppet, Chef)

@gil_zilberfeld
New questions
What is release management?
What is a version?
What is a feature?
What is an environment?
When is it ready for release?
How do we fix it when it fails?

@gil_zilberfeld
Working software
Developed
Tested
Does what we want
Does what the user wants
Incrementally adds value

@gil_zilberfeld
PRINCIPLES
Minimize risk
Minimize waste
Early feedback
You can also split your content
PRACTICES
Source control
Branching
Continuous integration
Unit and integration tests
How do we do develop it?

@gil_zilberfeld
PRINCIPLES
Minimize risk
Minimize waste
Early feedback
You can also split your content
PRACTICES
Branching
Separate environments
Continuous integration
Automated sanity tests
Automatic package
Automatic deploy
Functional tests
E2E tests
“Non-functional” tests
How do we do test it?

@gil_zilberfeld
The App
Manual test suite takes a week to run
Data preparation for testing takes 7 hours
Single development environment
No actual customers
Everyone steps on everyone else

@gil_zilberfeld
The App
Design a pipeline from development to pre-
production with the following goals:
Quickest feedback
Reliability

@gil_zilberfeld
PRINCIPLES
Minimize risk
Early feedback
You can also split your content
PRACTICES
Version management
“Side by side” deploy
Continuous deployment
Canary releases
Post-deployment testing
Rollback and roll-forward
How do we do ship it?

@gil_zilberfeld
PRINCIPLES
Minimize risk
Minimize waste
You can also split your content
PRACTICES
Production monitoring
Chaos monkeys
Reports on KPIs
How do we do monitor it?

@gil_zilberfeld
PRINCIPLES
Minimize risk
Minimize waste
Early feedback
You can also split your content
PRACTICES
Feature toggles
Versioning
MVPs
Data extraction
A/B testing
How do we do product validation?

@gil_zilberfeld
The App
The App is live!
We think people interested in hi-tech gadgets will
bring us the big bucks
We want to run a bucket load of experiments
We also have mobile versions, not just web

@gil_zilberfeld
The App
Design the pipeline from dev to production with the
goals:
Quick feedback
Do not interrupt production
Describe risks mitigations, capabilities, and issues

@gil_zilberfeld
Thanks!
ANY QUESTIONS?
You can find me at:
@gil_zilberfeld
http://www.GilZilberfeld.com
http://www.EverydayUnitTesting.com
http://www.fastee.im

Gil Zilberfeld introduces himself and provides an overview of DevOps. DevOps emphasizes collaboration between software developers and IT professionals while automating the process of software delivery and infrastructure changes. The document discusses new challenges with cloud, serverless environments, and governance. It also covers DevOps practices like source control, continuous integration, testing, deployment, monitoring, and product validation.

A Principles Based Approach to SAFeEm Campbell-Pretty

Presentation to the Agile Nashville User Group, January 2015. Are you working with multiple agile teams on a single software application? Are you looking for help with making agile work for you at the program level? Have you considered leveraging the Scaled Agile Framework (SAFe) but been scared off by its prescriptive nature? Are you confused about how program level SAFe applies in your context? Every organisation is different and what works for one organisation may not work for another. One of the benefits of a framework, is that they can and should be adapted to your context. Based on learnings derived from practical experience, this session will illustrate how focusing on principles can help you design a pragmatic approach to program level SAFe suitable for your unique situation.

Design Systems and Your ProductMark Wolfe

Design Systems are a valuable asset to product teams of all sizes. They unify applications, creating a single “source of truth” for UI elements, UX principles, content strategy guidelines, and re-usable code for the components. Design Systems also add business value by reducing redundancy, outlining a strategic product vision, and keeping design and development in sync across products. Integrating the Design System and building collaboration into the product development process is key to the success for the lifetime of the products. Learning Outcomes: - Define the Design System - Learn to sell the Design System to business leaders - Integrate the Design System into an Agile development process - Design an application and build a Design System

Stayin' Alive! Feature Disco Your Way to PI PlanningEm Campbell-Pretty

devopsdays Riga 2018 - Chaos while deploying AI and making sure it doesn’t hu...Thiago de Faria

Presentation + Demo at devopsdays Riga 2018 - September 28th. AI is such a buzzword, with its futuristic implementations and sophisticated machine learning algorithms (Hello, Deep learning!). We are using ML when we need external data to reach a working product because it would be impossible to solve it with the regular for/if/loops. What are the next steps? Moreover, what about Test, Release, and Deployment? We always value data and call our organizations “data-driven,” but now the impact is even more significant. If you are using an ML component, misused/dirty/problematic data will affect not your internal reports as before… but your application deployment and quality of service. Let’s hear discuss some AI implementations stories (its advantages/problems) finding common mistakes and future challenges for such a hyped theme.

Failing @ Scaling: Don’t panic, and carry a towel!Em Campbell-Pretty

Struggling with Agile at scale? Thinking about scaling Agile beyond the team? Want to learn from others’ mistakes? Well don’t panic, and carry a towel. After all, “any man who can hitch the length and breadth of the Galaxy, rough it, slum it, struggle against terrible odds, win through and still know where his towel is, is clearly a man to be reckoned with.” There is a lot to be learnt from those who have successfully hitchhiked their way to the galaxy of Scaled Agile, but there is also much to learn from those who have gotten a little lost upon the way. This session celebrates the scaled Agile hitchhiker, the people who tried and failed, with ideas that were occasionally brilliant but often plain stupid. You will laugh, you will cry but you will also walk away will a nice long list of ideas not to try when scaling Agile!

devopsdays Kiel 2018 - Can the AI hype & ML algorithms harm your devops initi...Thiago de Faria

This document discusses how machine learning and artificial intelligence hype can potentially harm DevOps initiatives. It notes examples of company executives making unrealistic claims about AI capabilities. It also summarizes key aspects of machine learning like supervised vs unsupervised learning. The document emphasizes that the data pipeline is crucial for machine learning and emphasizes applying software engineering best practices to the data pipeline. It also stresses the importance of continuous delivery for machine learning models and monitoring for issues after models are put into production.

Telstra’s Journey to SAFe - RallyON - June 2013Em Campbell-Pretty

Telstra has been scaling its agile practices since 2011, starting with 5 teams and growing to over 7 teams and 24 concurrent projects. They implemented an Agile Release Train model with 5-12 self-organizing teams delivering solutions every 8-12 weeks. Key aspects of their scaled agile approach include establishing an Agile Release Train structure, scaling sprint planning, using program increment planning, establishing servant leadership, and fostering a learning culture. The results have included decreased delivery cycle times, increased frequency of delivery, lower costs, fewer defects, and on-time on-budget deliveries along with improved team and customer satisfaction.

DOES SFO 2016 - Greg Padak - Default to OpenGene Kim

MylynOliver Gierke

Mylyn is a plug-in for Eclipse that focuses the IDE on the active task. It allows developers to define the context of a task, including related artifacts and conversations. Mylyn then filters IDE views and searches to only show information relevant to the current task, reducing information overload. It integrates with task management tools like JIRA and Bugzilla to link tasks and code changes for improved traceability of work.

Agile Data Warehousing at Telstra, TDWI Melbourne, October 2013Em Campbell-Pretty

This document summarizes a presentation given by Em Campbell-Pretty at TDWI Melbourne Chapter in October 2013 about implementing an agile approach to data warehousing at Telstra. The key results of adopting agile methods included reducing delivery cycle times from 12 months to 3 months, increasing delivery frequency to fortnightly, decreasing costs by 50%, and achieving on-time and on-budget deliveries with high customer satisfaction and team morale. Campbell-Pretty outlined how Telstra structured their teams, implemented Scrum practices, and embraced lean principles like respect for people, continuous process flow, and continuous improvement to successfully transition their large enterprise data warehouse to an agile model.

Atlassian: The latest and greatest - May/June 2013Sven Peters

This document discusses new features in software versions 5 and 6 of JIRA, a project management tool. It highlights improvements like increased speed, a more modern and mobile-friendly interface, and more flexible reporting. Additionally, it presents templates and blueprints as new ways to structure documents in JIRA. The rest of the document focuses on code collaboration tools and features, including distributed version control with Git, code review via pull requests, and code security with branch permissions and review/build rules. It suggests some teams may need additional integrations like hooks or add-ons to further customize their workflow.

Adopting Leffingwell's Scaled Agile Framework: the theory and the practice - ...Em Campbell-Pretty

This document discusses adopting the Scaled Agile Framework (SAFe) for agile development. It provides examples of benefits from implementing SAFe at an organization including reduced delivery time, increased frequency of releases, lower costs, fewer defects, and happier teams. It describes key elements of SAFe like the Agile Release Train, which coordinates multiple agile teams. It also discusses training, release planning, product backlogs, demonstrations, and other practices for scaling agile through SAFe.

2016 - IGNITE - Rugged Enterprise DevSecNetQAGovOpsdevopsdaysaustin

This document traces the evolution of DevOps from its origins to increasingly specialized and expanded forms over time. It starts with "RIP DevOps" and a headstone picture, then lists Twitter handles incorporating terms like "Agile Infrastructure", "Cloud", "Developers Operating", and "Operators Developing". These eventually expand into longer terms incorporating additional concerns from different parts of organizations like "Enterprise", "Legal", "HR", "Finance", "Security", "Networking", "Government", and "Customers". The document concludes that DevOps is now a cultural movement focused on building high velocity organizations, and that everyone can be considered DevOps practitioners as specialists working together across roles.

Api Days Berlin - Continuous UpdatingRobert Reiz

The document discusses the importance of continuous updating of software libraries and dependencies to ensure applications have the latest bug fixes and security updates. It notes that with agile development, the software development lifecycle has accelerated, but dependencies are still often overlooked. Left unmanaged, outdated dependencies can introduce security vulnerabilities and breakages over time. The document advocates using a tool like VersionEye to automatically detect outdated libraries, track used licenses, and ensure continuous integration of updates through automated migration paths. This prevents issues and saves developers time and money from manual updating processes.

Leading the Transformation: Stories from the TrenchesDevOps.com

This document summarizes the journey of Optum, a health services company, in transforming their development process for Medicare and Retirement portals from a primarily waterfall approach to an agile DevOps model over several years from 2015-2019. It describes their initial issues with long test cycles and bugs found late, their adoption of practices like automated testing, continuous integration, and shifting work left. It outlines their progress in areas like adding DevOps engineers, implementing Jenkins pipelines and Selenium for testing, and moving to OpenShift and Kubernetes. Their goals were to achieve full test and validation automation, reduce bugs found after sprints, and allow more of the team to stay on each release.

Git Branching for Agile TeamsSven Peters

Moving to Git opens up a whole new level of agility for software teams. Freed from the clunky code freezes and monolithic mega-merges that plague centralized version control, developers can isolate work in progress and build in narrow vertical slices with ease. Branching is so painless with Git that many teams are making new branches for each user story or bug fix they implement. This model is quickly becoming the new gold standard for agile teams – and for good reason!

DOES SFO 2016 - Cornelia Davis - DevOps: Who Does What?Gene Kim

Within the IT organizational structures that have dominated the last several decades roles and responsibilities are fairly standardized. But with the dramatic changes that DevOps practices and supporting toolsets bring, many are left feeling a bit off balance - it’s no longer clear who is responsible for even things as “straight-forward” as development or operations. In this talk I will take traditional roles that are distributed across fairly standard IT structures and sort them into a new organizational context. What is the role of the Enterprise Architect? Who does capacity planning and how? How can change management step out of the way all while still satisfying the requirements of safe deployments? How do agile teams interface with personnel responsible for maintaining legacy systems? I’ll leave the audience with a blueprint for a new organizational structure.

Six Things to Consider Before You Try Agile at Scale - Agile Business Forum -...Em Campbell-Pretty

1. The document discusses six things to consider before trying Agile at scale: adopting a scaled framework, having the right culture as a foundation, using communication and visualization, understanding your system of work, finding the right product owner, and not neglecting extreme programming practices. 2. It describes the company's journey to scaling Agile from 5 teams working on 4 large projects to 7 teams working on 24 concurrent projects using an Agile Release Train approach. 3. Implementing Agile at scale provided results like reducing average delivery cycle time from 12 months to 3 months, increasing frequency of delivery from quarterly to fortnightly, lowering costs by 50%, and achieving on-time and on-budget deliveries

Oops-Less OperationChristoph Engelbert

The document discusses creating resilient applications and systems. It defines resiliency as the ability to withstand failures from power outages, hardware failures, network issues, human errors, or software bugs. The document outlines some basic rules for resiliency, including having no single point of failure, embracing failures, and using back-off algorithms and idempotency. It also discusses the roles of developers, DevOps, operations, infrastructure, and cloud computing in building resiliency.

Git with t for teamsSven Peters

Git is not just a version control system. Git can change the way you interact with your team members. Lot’s of teams don’t think about reflecting their development workflow in Git and just use it out-of-the-box. Git, however, can be much more powerful, giving your team a boost in productivity, protecting your delivery pipeline and helping you to work better together. In this session we will start with a central workflow that is used by a lot of Subversion teams. You will learn how to practically integrate ALM solutions like continuous deployment, code reviews, change tracking and much more into your individual workflow. You will find out how to protect your master branch from accidental commits, broken builds and unreviewed code. This presentation will help you discover the best way to work together as a team – whether you’re yet to migrate to Git or even an experienced Git user.

Makers and Menders: Putting the Right Developers on the Right ProjectsAndrea Goulet

As presented at the PhillyETE conference in April 2017. When you think of a developer what comes to mind? A brogrammer living in San Francisco working 23 hours a day on the next Facebook? If so, you wouldn’t be alone. Like so many industries, software development is rife with stereotypes. And one that is particularly pervasive is the idea that all developers, if given the chance, would opt for a complete rewrite of an application. While it’s true that there are many software developers who do enjoy starting with a clean slate, there is also a group who loves working on making existing applications better. Rather than starting from scratch and building an 80% solution, these developers are ideal for taking over a project once it’s become stable, and nurturing it for a long time. Neither developer is better. Both are needed in the software world. In this talk, you’ll learn what motivates the small but passionate group of “menders” — people who love taking an existing project and making it better over time.

devopsdays Amsterdam 2018 - Chaos while deploying AI and making sure it doesn...Thiago de Faria

Presentation + Demo at devopsdays Amsterdam 2018 - June 29th. AI is such a buzzword, with its futuristic implementations and sophisticated machine learning algorithms (Hello, Deep learning!). We are using ML when we need external data to reach a working product because it would be impossible to solve it with the regular for/if/loops. What are the next steps? Moreover, what about Test, Release, and Deployment? We always value data and call our organizations “data-driven,” but now the impact is even more significant. If you are using an ML component, misused/dirty/problematic data will affect not your internal reports as before… but your application deployment and quality of service. Let’s hear discuss some AI implementations stories (its advantages/problems) finding common mistakes and future challenges for such a hyped theme.

A Software Engineer's Guide to DevOpsLaurie Barth

DOES SFO 2016 - Sam Guckenheimer & Ed Blankenship "Moving to One Engineering ...Gene Kim

This document introduces Sam Guckenheimer and Ed Blankenship and discusses Microsoft's goal of creating a single engineering system (1ES). The purpose is to enable any developer to access and reuse source code across the company, get rewarded for creating popular components, and have changes instantly visible. In practice, this means scaling Git for enterprise use, promoting a live site culture, and creating a common telemetry pipeline to measure usage and engineering metrics. The goal is to have self-forming teams and determine if 1ES is achieving its goals like supporting 4x user growth.

Atlassian - The Latest & Greatest April 2014Sven Peters

Sven Peters provides an overview of upcoming Atlassian events in September, June, and April-May in various cities. The document also summarizes new features for Confluence, including improved task management with the ability to mention people, add tasks to lists from different sources, and generate task reports. It notes that some slides contain restricted content and are not for public discussion.

Communication Artifacts: What's Your Code's Legacy?Andrea Goulet

Presented at the Agile Alliance Technical Conference, April 2017 in Boston, MA. Legacy code. It's those dirty brownfield applications that no one wants to work on. How do you make sure that your project never becomes one of those dreaded projects? And if you’ve inherited a dirtfield app, how do you turn it back around into a gorgeous greenfield? The answer to both of these questions may surprise you: seeding your app with good communication artifacts. In this talk, Andrea Goulet, the CEO of Corgibytes, a shop that specializes in working on legacy code bases, will give you specific and immediately actionable ideas to ensure the legacy of your codebases stays as green as possible. You’ll learn how to: ● Avoid interruptions by effectively “seeding” artifacts throughout your work ● End the dreaded git blame game ● Create code that continues to provide value years after you write it. If you’re ready to take your code legacy to the next level, this is one talk you won’t want to miss!

Understanding Technical Debt: A Primer for Product Owners and FoundersAndrea Goulet

As presented at ProductCamp Boston June 2017. Technical debt gets accrued when you move fast and break things, which is awesome in the early stages of a startup. Left unchecked, technical debt can slow a development team to a grinding halt, frustrating founders and product owners. In this session, we'll demystify technical debt. You'll leave with a good understanding of what it is, when to accrue it, and how to pay it down.

NoOps != No OperationsDavid Tesar

Going Serverless: The Best Ops is NoOps.PolarSeven Pty Ltd

More Related Content

What's hot (20)

DOES SFO 2016 - Greg Padak - Default to OpenGene Kim

MylynOliver Gierke

Agile Data Warehousing at Telstra, TDWI Melbourne, October 2013Em Campbell-Pretty

Atlassian: The latest and greatest - May/June 2013Sven Peters

Adopting Leffingwell's Scaled Agile Framework: the theory and the practice - ...Em Campbell-Pretty

2016 - IGNITE - Rugged Enterprise DevSecNetQAGovOpsdevopsdaysaustin

Api Days Berlin - Continuous UpdatingRobert Reiz

Leading the Transformation: Stories from the TrenchesDevOps.com

Git Branching for Agile TeamsSven Peters

DOES SFO 2016 - Cornelia Davis - DevOps: Who Does What?Gene Kim

Six Things to Consider Before You Try Agile at Scale - Agile Business Forum -...Em Campbell-Pretty

Oops-Less OperationChristoph Engelbert

Git with t for teamsSven Peters

Makers and Menders: Putting the Right Developers on the Right ProjectsAndrea Goulet

devopsdays Amsterdam 2018 - Chaos while deploying AI and making sure it doesn...Thiago de Faria

A Software Engineer's Guide to DevOpsLaurie Barth

DOES SFO 2016 - Sam Guckenheimer & Ed Blankenship "Moving to One Engineering ...Gene Kim

Atlassian - The Latest & Greatest April 2014Sven Peters

Communication Artifacts: What's Your Code's Legacy?Andrea Goulet

Understanding Technical Debt: A Primer for Product Owners and FoundersAndrea Goulet

DOES SFO 2016 - Greg Padak - Default to OpenGene Kim

MylynOliver Gierke

Agile Data Warehousing at Telstra, TDWI Melbourne, October 2013Em Campbell-Pretty

Atlassian: The latest and greatest - May/June 2013Sven Peters

Adopting Leffingwell's Scaled Agile Framework: the theory and the practice - ...Em Campbell-Pretty

2016 - IGNITE - Rugged Enterprise DevSecNetQAGovOpsdevopsdaysaustin

Api Days Berlin - Continuous UpdatingRobert Reiz

Leading the Transformation: Stories from the TrenchesDevOps.com

Git Branching for Agile TeamsSven Peters

DOES SFO 2016 - Cornelia Davis - DevOps: Who Does What?Gene Kim

Six Things to Consider Before You Try Agile at Scale - Agile Business Forum -...Em Campbell-Pretty

Oops-Less OperationChristoph Engelbert

Git with t for teamsSven Peters

Makers and Menders: Putting the Right Developers on the Right ProjectsAndrea Goulet

devopsdays Amsterdam 2018 - Chaos while deploying AI and making sure it doesn...Thiago de Faria

A Software Engineer's Guide to DevOpsLaurie Barth

DOES SFO 2016 - Sam Guckenheimer & Ed Blankenship "Moving to One Engineering ...Gene Kim

Atlassian - The Latest & Greatest April 2014Sven Peters

Communication Artifacts: What's Your Code's Legacy?Andrea Goulet

Understanding Technical Debt: A Primer for Product Owners and FoundersAndrea Goulet

Viewers also liked (8)

NoOps != No OperationsDavid Tesar

Going Serverless: The Best Ops is NoOps.PolarSeven Pty Ltd

Ops, DevOps, NoOps and AWS LambdaMatthew Boeckman

This document provides a history of computing from 20 years ago to the present, describing how infrastructure management has evolved from physical servers to virtualization to cloud computing. It then introduces Amazon Lambda as the logical conclusion of this progression, describing Lambda as an event-driven compute service that automatically manages infrastructure. Key details about Lambda include that it is stateless and scales automatically, and can be used for real-time log processing, media manipulation, ETL functions, and other stateless, event-driven tasks. Cost and pricing models for Lambda are also summarized.

DevOps and Continuous Delivery Reference Architectures - Volume 2Sonatype

CONTINUOUS DELIVERY REFERENCE ARCHITECTURES Including Sonatype Nexus and other popular DevOps tools Derek E. Weeks (@weekstweets) VP and DevOps Advocate Sonatype. Continuous Delivery and DevOps Reference Architectures include many common tool choices. The most common tool choices we find in these reference architectures are: Eclipse, git, Cloudbees Jenkins / Atlassian Bamboo, Sonatype Nexus, Atlassian JIRA, SonarQube, Puppet, Chef, Rundeck, Maven / Ant / Gradle, Subversion (svn), Junit, LiveRebel, ServiceNow

DevOps 101Ernest Mueller

This document provides an overview of DevOps concepts and practices. It defines DevOps as development and operations engineers collaborating throughout the entire service lifecycle, from design to production support. Key principles discussed include automating infrastructure, measuring everything, and fostering a culture of collaboration between teams. The document outlines DevOps practices like continuous integration/delivery and monitoring, and provides checklists for starting a DevOps initiative at both the grassroots and management levels.

Accenture DevOps: Delivering applications at the pace of businessAccenture Technology

DevOps and Continuous Delivery Reference Architectures (including Nexus and o...Sonatype

Keynote at CloudExpo and DevOps Summit 2014, Silicon ValleyVictoria Livschitz

Purpose-Defined Computing is the next frontier in automation where complete computing systems emerge in response to business needs. This will bring more change in the next 10 years than the last 50 years combined. Purpose-Defined Computing defines "magic buttons" that allow non-technical users to fulfill their computing needs while developers focus on coding. It treats all computing resources as policy-driven and adaptive to optimize for different environments and configurations.

NoOps != No OperationsDavid Tesar

Going Serverless: The Best Ops is NoOps.PolarSeven Pty Ltd

Ops, DevOps, NoOps and AWS LambdaMatthew Boeckman

DevOps and Continuous Delivery Reference Architectures - Volume 2Sonatype

DevOps 101Ernest Mueller

Accenture DevOps: Delivering applications at the pace of businessAccenture Technology

DevOps and Continuous Delivery Reference Architectures (including Nexus and o...Sonatype

Keynote at CloudExpo and DevOps Summit 2014, Silicon ValleyVictoria Livschitz

Similar to An agile introduction to DevOps (20)

The New AgileGil Zilberfeld

We know that agile methodologies work at the team level, and there is now even an effort to scale into whole organizations. There is a clear reason behind this: we found ways to improve performance, by analyzing situations better, and making better decision. Every organization wants to apply this in every level. Like in the late 90s, new ideas are coming out that challenge the way we think, and this time they don't just answer development. Ideas like Beyond Budgeting, Lean Startup, Cynefin, Real Options, Feature Injection, SAFe, Design Thinking, #NoEstimates, Cost of Delay and others are spreading out, and while we know not all will last, you never know which might fit your situation. In this session, I'll give a summary of what's hot around the agile world, with some criticism and application in the real world. 13 years after the original manifesto, organizations start to experiment again. I always wished I was there when the first conversations took place. I encourage you to join in on current conversations. Let's start.

Continuous Delivery - The Next 10 yearsDave Farley

The document discusses continuous delivery over the next 10 years. It begins by referencing the direct intellectual forebears of continuous delivery, including the Unix philosophy of building software. It then provides an example continuous delivery process diagram. The document notes that what has changed in continuous delivery over the last 10 years includes a focus on testing microservices. It expresses few regrets about continuous delivery but notes areas that could have been communicated better like culture and security. The document concludes by stating continuous delivery is about continuously delivering ideas.

The New Agile IIGil Zilberfeld

Continuous Testing in DevOpsTechWell

This document provides an overview of continuous testing in DevOps presented by Michael Hackett of LogiGear Corporation. It discusses what DevOps is and how testing fits into the continuous delivery pipeline. It emphasizes the need for testing at every step of development and deployment through test automation. It also provides examples of challenges companies face in implementing continuous testing and DevOps practices.

Customer Presentation: Digital Globe's road to Continuous DeliveryXebiaLabs

The document discusses DigitalGlobe's initiative to implement continuous delivery of software updates. It aims to reduce downtime and improve availability through full automation of deployments using Deployit. Key steps included standardizing environments across development, test, and production; reducing build dependencies; and establishing metrics to ensure quality and efficiency of the delivery process. The pilot program started with deployments to non-production environments and aims to expand to full automation of updates to ground systems by end of 2014.

DevOps - the Future of Agile - Why/What/How - from Enterprise DevOps Israel 2015Yuval Yeret

Mobile App Feature Configuration and A/B Experimentslacyrhoades

The document discusses feature configuration and A/B testing in mobile apps. It describes how Etsy uses feature flags and continuous experimentation to iteratively develop and test new features. Features can be enabled or disabled for certain users or groups. Experiments follow a process of setting up a feature flag, determining user eligibility, coding the feature, internal testing, then launching the feature to a percentage of users while collecting analytics. This allows gathering feedback to improve products and user experience.

Devops & Agility - Build the Culture, Get the Tools, Win the Day - Dundee Tec...David Walker

DevOps involves development and operations engineers collaborating throughout the entire service lifecycle from design to deployment and support. It builds upon agile principles by applying them throughout the entire workflow. Implementing DevOps requires cultural changes across the entire organization where teams work together towards shared goals. Automation, lean principles, continuous monitoring and improvements are key aspects of DevOps.

GeeCON 2015 DevOps and the dark side Steve Poole

In Toggle, We TrustPuneet Arora

Practical Devops and Continous DeliveryAnuraj S.L

This document provides an agenda and overview for a presentation on continuous testing, integration, and delivery in an Agile/DevOps environment. The summary includes: 1. The presentation covers the history and concepts of DevOps, how it differs from traditional development practices, and its benefits in allowing for more frequent code integration and delivery. 2. When adopting Agile and DevOps practices, testing must also be continuous and aligned with the new development process, with testing occurring more regularly and closely following development. 3. Continuous integration, delivery, and deployment involve automating the integration and testing of code changes, allowing teams to detect issues early and rapidly release updates that pass testing. Automated testing is key to supporting

Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony

Many companies are currently going through Agile Transformation or thinking about making the transition to agile. While moving to agile can create great opportunity for organizations, the journey to get there can be highly challenging. If you don’t have the right people, process and tools in place, the true benefits of agile may not be recognized. In this webinar, Andrew Stickland, Head of Client Services, for Clearvision and Kevin Dunne, VP of Business Development and Strategy for QASymphony will discuss the best practices for making the agile transformation. In this webinar, we will try to answer the following questions: - Who are the people I need in place? - What are the core processes that I need to change? - What tools do I need? View the On-Demand webinar here: http://pi.qasymphony.com/agile-transformation-best-practices-webinar-lp060?utm_source=slideshare&utm_medium=slideshare&utm_campaign=Agile%20Transformation%20Webinar

BrainQuest-DevOpsEric Phan

The document discusses the evolution of DevOps practices from earlier software development approaches. It outlines four stages of DevOps maturity: (1) identifying manual processes for automation, (2) automating processes for repeatability, (3) adding metrics for monitoring, and (4) using metrics to continuously improve processes. The document also provides examples of tools that support DevOps practices at different stages.

Continuous delivery is more than dev opsAgile Montréal

Continuous Delivery for Agile TeamsMike Bowler

The document discusses the principles and practices of continuous delivery in an agile context. It emphasizes automating the entire software delivery process from code commits through deployment to production to minimize risks and ensure fast, reliable software updates. This includes having automated tests, continuous integration, monitoring systems, and the ability to rollback changes. It also stresses the importance of collaboration across teams to establish a shared goal of delivering value to customers through working software.

Tools Won't Fix Your Broken DevOpsNicole Forsgren

This document appears to be a slide presentation on DevOps practices and culture. Some key points discussed include: - High-performing IT organizations are twice as likely to exceed goals in areas like profitability and customer satisfaction. - DevOps focuses on continuous delivery, quality, lean processes, effective collaboration, and a culture of learning from failures. - Culture can be measured and influenced by providing employees the tools and training to do their jobs successfully. - Adopting DevOps practices may lead to improved lead times, release frequency, change fail rates, and service restoration times.

Another Copernican Revolution: maintenance first, projects second (European D...Eugenio Minardi

The document discusses the need for a "Copernican revolution" in how websites are built and maintained. Specifically, it argues that big projects are prioritized over maintenance, leading to technical debt. It proposes prioritizing ongoing maintenance over large one-time projects through iterative development, allocating more resources to maintenance, and educating clients and colleagues on its importance for long-term sustainability. Breaking large projects into smaller pieces and focusing on sites' lifetimes rather than launch dates could help drive this change.

SplunkLive! London 2015 - DevOps BreakoutSplunk

This document discusses how Splunk can help with DevOps challenges by providing visibility across the product development lifecycle. It notes common challenges like lack of visibility, pressure to increase velocity, and limited insights from application logs. The document outlines how Splunk collects log data from various DevOps tools and environments to enable searching, visualizing, and monitoring logs. This allows issues to be identified and resolved faster, improving agility and time to market. Key benefits are listed as reduced time to market, increased agility, and insights into application performance from centralized log access.

DevOps & the Dark Side 10 ways to convince your team DevOps is a force for goodSteve Poole

Agile Development Practices - ProductivityAlex Moore

The New AgileGil Zilberfeld

Continuous Delivery - The Next 10 yearsDave Farley

The New Agile IIGil Zilberfeld

Continuous Testing in DevOpsTechWell

Customer Presentation: Digital Globe's road to Continuous DeliveryXebiaLabs

DevOps - the Future of Agile - Why/What/How - from Enterprise DevOps Israel 2015Yuval Yeret

Mobile App Feature Configuration and A/B Experimentslacyrhoades

Devops & Agility - Build the Culture, Get the Tools, Win the Day - Dundee Tec...David Walker

GeeCON 2015 DevOps and the dark side Steve Poole

In Toggle, We TrustPuneet Arora

Practical Devops and Continous DeliveryAnuraj S.L

Agile Transformation: People, Process and Tools to Make Your Transformation S...QASymphony

BrainQuest-DevOpsEric Phan

Continuous delivery is more than dev opsAgile Montréal

Continuous Delivery for Agile TeamsMike Bowler

Tools Won't Fix Your Broken DevOpsNicole Forsgren

Another Copernican Revolution: maintenance first, projects second (European D...Eugenio Minardi

SplunkLive! London 2015 - DevOps BreakoutSplunk

DevOps & the Dark Side 10 ways to convince your team DevOps is a force for goodSteve Poole

Agile Development Practices - ProductivityAlex Moore

More from Gil Zilberfeld (20)

Dirty tests and How To Clean ThemGil Zilberfeld

This document introduces Gil Zilberfeld, the founder of TestinGil, and discusses clean code and clean tests. It provides Gil's contact information and links to TestinGil's website and social media profiles. It also lists some characteristics of clean tests, such as showing intent, being focused, and doing exactly what they say. Finally, it discusses test smells like god classes and methods, comments, uncommunicative names, and embedded constants, and how refactoring can help address these smells.

Unit testing for Grown-upsGil Zilberfeld

Zen and the art of Test Maintenance - #TestIL Meetup Tel AvivGil Zilberfeld

Zen And the Art of Test Maintenance PresentationGil Zilberfeld

Spock: It's Only LogicalGil Zilberfeld

Better Estimation and PlanningGil Zilberfeld

Dependency injection and Why It Matters to TestersGil Zilberfeld

Zen and the Art of Test MaintenanceGil Zilberfeld

This document discusses strategies for test maintenance. It emphasizes the importance of aligning tests with product focus and risks. It provides examples of how to evaluate tests and identifies common issues like uninformative, unreliable, and misleading tests. The document also covers testability, refactoring, behavior-driven development, and techniques like test reviews and pair programming. Exercises are included to help learn test maintenance practices.

Spring Testing FeaturesGil Zilberfeld

This document discusses strategies for testing Spring applications. It recommends starting with unit tests that inject mocks and configure test data. Integration tests can use the SpringRunner to load Spring Boot applications in tests. MockMVC allows testing controller layers by calling APIs and asserting responses. The document provides examples of configuring tests, injecting mocks, using in-memory databases, and testing client-side code. It emphasizes managing test code and configurations like regular code.

Better Estimation and PlanningGil Zilberfeld

This document discusses estimation techniques for software development projects. It presents different approaches to estimating such as planning poker, using complexity scales to assess confidence, and using historical velocity to project future progress. While estimation is inherently uncertain, having a variety of techniques can help produce realistic targets and control over projects. Recording past performance allows for more statistical projection over singular point estimates. Ultimately, the goal is to make informed decisions rather than predict outcomes exactly.

The Untold User StoryGil Zilberfeld

Real Life Test MaintenanceGil Zilberfeld

The document discusses test maintenance and provides guidance on developing a maintenance plan. It suggests starting by understanding what is important to the product, associated risks, and areas of focus. Examples are then given for Facebook and Candy Crush Saga to illustrate how this framework can be applied. The document also provides suggestions for evaluating existing tests, cleaning up test suites, addressing problematic tests, and conducting code reviews to support effective test maintenance.

The Whole Story - Mapping, Slicing and Figuring things outGil Zilberfeld

This document discusses user stories and how to write them effectively. It defines stakeholders, goals, and capabilities, and emphasizes that user stories should provide enough context for a productive discussion on implementation. Stories work best when they describe a specific goal from the perspective of a stakeholder. The document also introduces story mapping as a technique to organize user stories and visualize the overall user experience as a set of interconnected stories.

Fractal test planningGil Zilberfeld

This document discusses test planning from different perspectives, including the product life cycle, development life cycle, and risk and value. It also covers Kent Beck's concepts of explore, expand, and extract, and how testing roles may differ in each phase. Parameters like existing automation, feedback mechanisms, and technical debt are presented as influencing test planning. The document proposes examining these parameters at different levels, such as development phases or zoom levels. Overall it promotes taking a nuanced, multifaceted approach to test planning that considers various contexts and perspectives.

Beter code for better testsGil Zilberfeld

The fastest BDD crash-course everGil Zilberfeld

This document provides an introduction to Behavior Driven Development (BDD). It discusses how BDD combines techniques from test-driven development, domain-driven design, and object-oriented analysis and design to facilitate collaboration between teams. It emphasizes that BDD is focused on conversations between stakeholders to understand requirements before automating tests. The document then demonstrates how to identify stakeholders and their goals, prioritize capabilities and risks, write user stories and acceptance criteria, and automate tests using Gherkin syntax with tools like Cucumber or SpecFlow.

Playing games remotelyGil Zilberfeld

The document discusses challenges and strategies for remote agile teams. It notes that cultural differences, lack of trust, communication issues, and different mental models can make remote work difficult. However, remote teams can still follow agile principles by focusing on individuals and interactions over processes; collaboration with customers; and responding to change. Effective remote tools, methods, and culture are needed. Strategies proposed include developing team culture even remotely, using video conferencing and remote boards, and establishing ground rules for remote meetings.

A Horror StoryGil Zilberfeld

This document discusses slicing user stories to make them smaller and more manageable for testing. It recommends slicing stories based on stakeholders, capabilities, acceptance criteria, and edge cases. Stories should be written to describe a desired outcome or capability without rigid templates. The goal of slicing is to have independent, negotiable, valuable, and testable stories that provide short feedback cycles for continuous learning and improvement.

Why TDD is Important for EveryoneGil Zilberfeld

Creating A Unit Testing StrategyGil Zilberfeld

Dirty tests and How To Clean ThemGil Zilberfeld

Unit testing for Grown-upsGil Zilberfeld

Zen and the art of Test Maintenance - #TestIL Meetup Tel AvivGil Zilberfeld

Zen And the Art of Test Maintenance PresentationGil Zilberfeld

Spock: It's Only LogicalGil Zilberfeld

Better Estimation and PlanningGil Zilberfeld

Dependency injection and Why It Matters to TestersGil Zilberfeld

Zen and the Art of Test MaintenanceGil Zilberfeld

Spring Testing FeaturesGil Zilberfeld

Better Estimation and PlanningGil Zilberfeld

The Untold User StoryGil Zilberfeld

Real Life Test MaintenanceGil Zilberfeld

The Whole Story - Mapping, Slicing and Figuring things outGil Zilberfeld

Fractal test planningGil Zilberfeld

Beter code for better testsGil Zilberfeld

The fastest BDD crash-course everGil Zilberfeld

Playing games remotelyGil Zilberfeld

A Horror StoryGil Zilberfeld

Why TDD is Important for EveryoneGil Zilberfeld

Creating A Unit Testing StrategyGil Zilberfeld

Recently uploaded (20)

Orion Context Broker introduction 20250509Fermin Galan

Gojek Clone App for Multi-Service BusinessXongoLab Technologies LLP

How to avoid IT Asset Management mistakes during implementation_PDF.pdfvictordsane

IT Asset Management (ITAM) is no longer optional. It is a necessity. Organizations, from mid-sized firms to global enterprises, rely on effective ITAM to track, manage, and optimize the hardware and software assets that power their operations. Yet, during the implementation phase, many fall into costly traps that could have been avoided with foresight and planning. Avoiding mistakes during ITAM implementation is not just a best practice, it’s mission critical. Implementing ITAM is like laying a foundation. If your structure is misaligned from the start—poor asset data, inconsistent categorization, or missing lifecycle policies—the problems will snowball. Minor oversights today become major inefficiencies tomorrow, leading to lost assets, licensing penalties, security vulnerabilities, and unnecessary spend. Talk to our team of Microsoft licensing and cloud experts to look critically at some mistakes to avoid when implementing ITAM and how we can guide you put in place best practices to your advantage. Remember there is savings to be made with your IT spending and non-compliance fines to avoid. Send us an email via [email protected]

Interactive odoo dashboards for sales, CRM , Inventory, Invoice, Purchase, Pr...AxisTechnolabs

Interactive Odoo Dashboard for various business needs can provide users with dynamic, visually appealing dashboards tailored to their specific requirements. such a module that could support multiple dashboards for different aspects of a business ✅Visit And Buy Now : https://bit.ly/3VojWza ✅This Interactive Odoo dashboard module allow user to create their own odoo interactive dashboards for various purpose. App download now : Odoo 18 : https://bit.ly/3VojWza Odoo 17 : https://bit.ly/4h9Z47G Odoo 16 : https://bit.ly/3FJTEA4 Odoo 15 : https://bit.ly/3W7tsEB Odoo 14 : https://bit.ly/3BqZDHg Odoo 13 : https://bit.ly/3uNMF2t Try Our website appointment booking odoo app : https://bit.ly/3SvNvgU 👉Want a Demo ?📧 [email protected] ➡️Contact us for Odoo ERP Set up : 091066 49361 👉Explore more apps: https://bit.ly/3oFIOCF 👉Want to know more : 🌐 https://www.axistechnolabs.com/ #odoo #odoo18 #odoo17 #odoo16 #odoo15 #odooapps #dashboards #dashboardsoftware #odooerp #odooimplementation #odoodashboardapp #bestodoodashboard #dashboardapp #odoodashboard #dashboardmodule #interactivedashboard #bestdashboard #dashboard #odootag #odooservices #odoonewfeatures #newappfeatures #odoodashboardapp #dynamicdashboard #odooapp #odooappstore #TopOdooApps #odooapp #odooexperience #odoodevelopment #businessdashboard #allinonedashboard #odooproducts

Top Magento Hyvä Theme Features That Make It Ideal for E-commerce.pdfevrigsolution

Adobe Media Encoder Crack FREE Download 2025zafranwaqar90

🌍📱👉COPY LINK & PASTE ON GOOGLE https://dr-kain-geera.info/👈🌍 Adobe Media Encoder is a transcoding and rendering application that is used for converting media files between different formats and for compressing video files. It works in conjunction with other Adobe applications like Premiere Pro, After Effects, and Audition. Here's a more detailed explanation: Transcoding and Rendering: Media Encoder allows you to convert video and audio files from one format to another (e.g., MP4 to WAV). It also renders projects, which is the process of producing the final video file. Standalone and Integrated: While it can be used as a standalone application, Media Encoder is often used in conjunction with other Adobe Creative Cloud applications for tasks like exporting projects, creating proxies, and ingesting media, says a Reddit thread.

WinRAR Crack for Windows (100% Working 2025)sh607827

Why Tapitag Ranks Among the Best Digital Business Card ProvidersTapitag

Discover how Tapitag stands out as one of the best digital business card providers in 2025. This presentation explores the key features, benefits, and comparisons that make Tapitag a top choice for professionals and businesses looking to upgrade their networking game. From eco-friendly tech to real-time contact sharing, see why smart networking starts with Tapitag. https://tapitag.co/collections/digital-business-cards

Building Apps for Good The Ethics of App DevelopmentNet-Craft.com

sequencediagrams.pptx software Engineeringaashrithakondapalli8

Best Accounting Practice Management Software Guide for 2025Tidyflow

This slide deck, “Best Accounting Practice Management Software Guide for 2025,” is designed for solo CPAs, small accounting firms, and growing mid-sized practices looking to navigate the crowded and sometimes overwhelming world of accounting practice management tools. In 2025, the pressure on accounting firms is higher than ever. Clients expect fast, clear communication. Teams are often working remotely or in hybrid setups. Deadlines are tight, and regulations are constantly changing. Choosing the right practice management software can make all the difference — helping firms stay organized, automate repetitive work, collaborate smoothly, and ultimately deliver better service to clients. This presentation offers a clear, unbiased comparison of seven of the most popular practice management platforms used by accounting firms today, including: Tidyflow — a lean, no-bloat tool built for small and growing firms; Karbon — a powerful platform with integrated email and advanced team workflows; TaxDome — a robust system designed especially for tax-focused firms; Canopy — a modular, flexible solution for firms that want to mix and match tools; Financial Cents — a simple, budget-friendly option for small firms; Jetpack Workflow — a lightweight workflow tracker great for solo practitioners and small teams; Pixie — a client-focused platform offering unlimited users at a flat price. Each software is broken down with key details on pricing, best-fit firm type, notable features, integrations, pros, and cons. We’ve also included a quick comparison table upfront to help busy practitioners scan for top-line differences. What you’ll learn from this slide deck: ✅ Which tools are best suited for your firm’s size and growth stage ✅ What features (client portals, time tracking, automation, integrations) matter most ✅ How pricing models compare across popular providers ✅ Where each software excels — and where it might fall short The final slides offer guidance on how to choose the right software for your unique needs, with a checklist covering firm size, required features, ease of use, integrations, and budget considerations. Whether you’re looking for an affordable, scalable option like Tidyflow or a powerful enterprise-level solution like Karbon, this guide will help you make a more informed, confident decision for 2025 and beyond. For more details, visit tidyflow.com — a modern practice management platform designed specifically for small and growing accounting firms that want a simple, affordable solution without enterprise-level complexity.

Robotic Process Automation (RPA) Software Development Services.pptxjulia smits

Autodesk Inventor Crack (2025) LatestGoogle

Digital Twins Software Service in Belfastjulia smits

Not So Common Memory Leaks in Java WebinarTier1 app

This SlideShare presentation is from our May webinar, “Not So Common Memory Leaks & How to Fix Them?”, where we explored lesser-known memory leak patterns in Java applications. Unlike typical leaks, subtle issues such as thread local misuse, inner class references, uncached collections, and misbehaving frameworks often go undetected and gradually degrade performance. This deck provides in-depth insights into identifying these hidden leaks using advanced heap analysis and profiling techniques, along with real-world case studies and practical solutions. Ideal for developers and performance engineers aiming to deepen their understanding of Java memory management and improve application stability.

AI in Business Software: Smarter Systems or Hidden Risks?Amara Nielson

AI in Business Software: Smarter Systems or Hidden Risks? Description: This presentation explores how Artificial Intelligence (AI) is transforming business software across CRM, HR, accounting, marketing, and customer support. Learn how AI works behind the scenes, where it’s being used, and how it helps automate tasks, save time, and improve decision-making. We also address common concerns like job loss, data privacy, and AI bias—separating myth from reality. With real-world examples like Salesforce, FreshBooks, and BambooHR, this deck is perfect for professionals, students, and business leaders who want to understand AI without technical jargon. ✅ Topics Covered: What is AI and how it works AI in CRM, HR, finance, support & marketing tools Common fears about AI Myths vs. facts Is AI really safe? Pros, cons & future trends Business tips for responsible AI adoption

Surviving a Downturn Making Smarter Portfolio Decisions with OnePlan - Webina...OnePlan Solutions

When budgets tighten and scrutiny increases, portfolio leaders face difficult decisions. Cutting too deep or too fast can derail critical initiatives, but doing nothing risks wasting valuable resources. Getting investment decisions right is no longer optional; it’s essential. In this session, we’ll show how OnePlan gives you the insight and control to prioritize with confidence. You’ll learn how to evaluate trade-offs, redirect funding, and keep your portfolio focused on what delivers the most value, no matter what is happening around you.

Requirements in Engineering AI- Enabled Systems: Open Problems and Safe AI Sy...Lionel Briand

Wilcom Embroidery Studio Crack 2025 For WindowsGoogle

The Elixir Developer - All Things OpenCarlo Gilmar Padilla Santana

Orion Context Broker introduction 20250509Fermin Galan

Gojek Clone App for Multi-Service BusinessXongoLab Technologies LLP

How to avoid IT Asset Management mistakes during implementation_PDF.pdfvictordsane

Interactive odoo dashboards for sales, CRM , Inventory, Invoice, Purchase, Pr...AxisTechnolabs

Top Magento Hyvä Theme Features That Make It Ideal for E-commerce.pdfevrigsolution

Adobe Media Encoder Crack FREE Download 2025zafranwaqar90

WinRAR Crack for Windows (100% Working 2025)sh607827

Why Tapitag Ranks Among the Best Digital Business Card ProvidersTapitag

Building Apps for Good The Ethics of App DevelopmentNet-Craft.com

sequencediagrams.pptx software Engineeringaashrithakondapalli8

Best Accounting Practice Management Software Guide for 2025Tidyflow

Robotic Process Automation (RPA) Software Development Services.pptxjulia smits

Autodesk Inventor Crack (2025) LatestGoogle

Digital Twins Software Service in Belfastjulia smits

Not So Common Memory Leaks in Java WebinarTier1 app

AI in Business Software: Smarter Systems or Hidden Risks?Amara Nielson

Surviving a Downturn Making Smarter Portfolio Decisions with OnePlan - Webina...OnePlan Solutions

Requirements in Engineering AI- Enabled Systems: Open Problems and Safe AI Sy...Lionel Briand

Wilcom Embroidery Studio Crack 2025 For WindowsGoogle

The Elixir Developer - All Things OpenCarlo Gilmar Padilla Santana

An agile introduction to DevOps

1. @gil_zilberfeld An agile introduction to DevOps

2. @gil_zilberfeld Hello! I AM GIL ZILBERFELD www.gilzilberfeld.com www.everydayunittesting.com www.fastee.im @gil_zilberfeld

3. @gil_zilberfeld

4. @gil_zilberfeld DevOps A culture, movement or practice that emphasizes the collaboration and communication of both software developers and other information- technology professionals while automating the process of software delivery and infrastructure changes.

5. @gil_zilberfeld

6. @gil_zilberfeld

7. @gil_zilberfeld

8. @gil_zilberfeld DevOps A culture, movement or practice that emphasizes the collaboration and communication of both software developers and other information- technology professionals while automating the process of software delivery and infrastructure changes.

13. @gil_zilberfeld The new stuff New complex problems (Cloud, Serverless) Environments all the way down Governance and risk (“You can’t do that!”) We trust automation Better tools (Docker, Puppet, Chef)

14. @gil_zilberfeld

15. @gil_zilberfeld New questions What is release management? What is a version? What is a feature? What is an environment? When is it ready for release? How do we fix it when it fails?

16. @gil_zilberfeld

17. @gil_zilberfeld Working software Developed Tested Does what we want Does what the user wants Incrementally adds value

18. @gil_zilberfeld

19. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Early feedback You can also split your content PRACTICES Source control Branching Continuous integration Unit and integration tests How do we do develop it?

20. @gil_zilberfeld

21. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Early feedback You can also split your content PRACTICES Source control Branching Continuous integration Automatic package Automatic deploy Unit and integration tests E2E tests “Non-functional” tests How do we do test it?

22. @gil_zilberfeld

23. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Early feedback You can also split your content PRACTICES Branching Separate environments Continuous integration Automated sanity tests Automatic package Automatic deploy Functional tests E2E tests “Non-functional” tests How do we do test it?

24. @gil_zilberfeld

25. @gil_zilberfeld The App Manual test suite takes a week to run Data preparation for testing takes 7 hours Single development environment No actual customers Everyone steps on everyone else

26. @gil_zilberfeld The App Design a pipeline from development to pre- production with the following goals: Quickest feedback Reliability

27. @gil_zilberfeld

28. @gil_zilberfeld

29. @gil_zilberfeld

30. @gil_zilberfeld PRINCIPLES Minimize risk Early feedback You can also split your content PRACTICES Version management “Side by side” deploy Continuous deployment Canary releases Post-deployment testing Rollback and roll-forward How do we do ship it?

31. @gil_zilberfeld

32. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste You can also split your content PRACTICES Production monitoring Chaos monkeys Reports on KPIs How do we do monitor it?

33. @gil_zilberfeld

34. @gil_zilberfeld PRINCIPLES Minimize risk Minimize waste Early feedback You can also split your content PRACTICES Feature toggles Versioning MVPs Data extraction A/B testing How do we do product validation?

35. @gil_zilberfeld

36. @gil_zilberfeld The App The App is live! We think people interested in hi-tech gadgets will bring us the big bucks We want to run a bucket load of experiments We also have mobile versions, not just web

37. @gil_zilberfeld The App Design the pipeline from dev to production with the goals: Quick feedback Do not interrupt production Describe risks mitigations, capabilities, and issues

42. @gil_zilberfeld Thanks! ANY QUESTIONS? You can find me at: @gil_zilberfeld http://www.GilZilberfeld.com http://www.EverydayUnitTesting.com http://www.fastee.im

Editor's Notes

#8: Simple to explain, hard to implement

An agile introduction to DevOps

Recommended

More Related Content

What's hot (20)

Viewers also liked (8)

Similar to An agile introduction to DevOps (20)

More from Gil Zilberfeld (20)

Recently uploaded (20)

An agile introduction to DevOps

Editor's Notes