ELAG 2016: Going Live - The highs and lows of getting a project into service
•Download as PPTX, PDF•
1 like•176 views
Ciaran Talbot discusses the highs and lows of transitioning several library projects into service at the University of Manchester Library. The Alma implementation was a large consolidation project that had some data migration and devolvement successes but also unexpected staff user expectations. BookedIn was a medium collaboration project that faced timeline slippage issues. The CheckOut app was a small, unique project challenged by tech outpacing policy. Talbot concludes that the library is good at projects and transitions but could improve effectiveness by focusing more on the transition period and starting planning earlier.
Report
Share
Report
Share
Recommended
Engineering your culture how to keep your engineers happy
This document discusses engineering culture at different companies. It provides tips for building an engineering culture that focuses on autonomy, quick iterations, and testing. It also highlights the importance of onboarding and mentoring junior engineers.
Lessons from Branch's launch
This document discusses lessons learned from launching a Ruby on Rails application. Some key points include: using Resque for background jobs provides more control than DelayedJob; background jobs can significantly impact database load so it's important to monitor and optimize them; indexes can greatly improve database performance so don't let Rails generate inefficient queries; and serialization can hurt performance so use database relations instead of storing serialized objects. Overall, expect issues and don't get complacent - optimize asynchronously processed tasks and write efficient SQL.
Minimal Viable Architecture - Silicon Slopes 2020
This presentation introduces the idea of a "Minimal Viable Architecture". As a company and product evolves, its architecture should evolve as well. We talk about the different phases of a product -- from the idea phase, to the starting phase, scaling phase, and optimizing phase. For each phase, we discuss the goals and constraints on the business, and we suggest an appropriate software architecture to match. Throughout the presentation, we use examples from eBay, Google, StitchFix, and others.
Moving Fast at Scale
As the research in Accelerate and in the DevOps Handbook shows, high-performing organizations deliver more rapidly, more repeatably, and more reliably. And as an organization scales, it becomes more and more important to get the product development process right. Drawing on the speaker's experiences leading high-performing organizations at Google and eBay, this session discusses the upstream parts of that process, focusing on organization, problem definition, and prioritization. We will discuss forming small, cross-functional teams with clear areas of responsibility. Then we will discuss the importance of clearly defining the problem we are trying to solve as a team. Finally, we will cover focus and prioritization -- how we decide what to do when. You will take away actionable techniques you can apply in your own organization.
Reactive Streams and the Wide World of Groovy
The concept of Reactive Streams (aka Reactive Extensions, Reactive Functional Programming, or simply Rx) has become increasingly popular recently, and with good reason. The Reactive Streams specification provides a universal abstraction for asynchronously processing data received across multiple sources (e.g. database, user input, third-party services), and includes mechanisms for controlling the rate at which data is received. This makes it a powerful tool within a Microservice platform. And did we mention that the Groovy lang community is quite involved?
In this talk we’ll explore the various features and concepts of Reactive Streams. We’ll talk about some typical use cases for Rx and more importantly, how to implement them. We’ll focus primarily on RxGroovy and Ratpack, then provide example implementations that show you how to get started with this powerful technique.
ProductCamp RTP 2010 - What the H*ell! - Adam Covati
The document discusses the experience of a product manager launching a new social media management and analytics tool called Argyle. It provides details about the founder's background, Argyle's timeline from initial development to full launch in under a year, strategies used such as iterating with customers and experimenting with minimal investments, and notes on selling the vision and raising funds in the startup triangle area.
Scaling Your Architecture for the Long Term
This talk from the virtual 2020 CTO Summit (https://www.ctoconnection.com/summits) covers several architecture lessons to help you survive and thrive through the scaling phase of your company:
* Modular Architecture
* Event-Driven Communication
* Quality and Reliability
* Continuous Delivery
Testing The Legacy: Making Existing Applications Testable Without Epic Efforts
If you have an established product which came about before the widespread use of the unit and system testing, then you know the problem.
The old code cannot be made testable without a significant effort of throwing it away and writing it anew.
What does it mean for the QA? It means endless repetitions of manual test runs. Sounds like fun? Yeah.. Nah!
In this presentation you will find two ways to make legacy applications testable through automation: an easy one, and a good one. The main benefit they provide is a basis for the further refactoring of the application, without damaging it.
Think of it as a Catch-22: you can't make your old app code testable without severely changing it, and you can't be sure that your changes work because you have no tests to verify them.
If you are a QA and you work with older apps and systems doing a lot of manual testing, then this is the topic for you.
This talk was given at ITx 2016 in Wellington, New Zealand, for Testing Professionals Network.
Recommended
Engineering your culture how to keep your engineers happy
This document discusses engineering culture at different companies. It provides tips for building an engineering culture that focuses on autonomy, quick iterations, and testing. It also highlights the importance of onboarding and mentoring junior engineers.
Lessons from Branch's launch
This document discusses lessons learned from launching a Ruby on Rails application. Some key points include: using Resque for background jobs provides more control than DelayedJob; background jobs can significantly impact database load so it's important to monitor and optimize them; indexes can greatly improve database performance so don't let Rails generate inefficient queries; and serialization can hurt performance so use database relations instead of storing serialized objects. Overall, expect issues and don't get complacent - optimize asynchronously processed tasks and write efficient SQL.
Minimal Viable Architecture - Silicon Slopes 2020
This presentation introduces the idea of a "Minimal Viable Architecture". As a company and product evolves, its architecture should evolve as well. We talk about the different phases of a product -- from the idea phase, to the starting phase, scaling phase, and optimizing phase. For each phase, we discuss the goals and constraints on the business, and we suggest an appropriate software architecture to match. Throughout the presentation, we use examples from eBay, Google, StitchFix, and others.
Moving Fast at Scale
As the research in Accelerate and in the DevOps Handbook shows, high-performing organizations deliver more rapidly, more repeatably, and more reliably. And as an organization scales, it becomes more and more important to get the product development process right. Drawing on the speaker's experiences leading high-performing organizations at Google and eBay, this session discusses the upstream parts of that process, focusing on organization, problem definition, and prioritization. We will discuss forming small, cross-functional teams with clear areas of responsibility. Then we will discuss the importance of clearly defining the problem we are trying to solve as a team. Finally, we will cover focus and prioritization -- how we decide what to do when. You will take away actionable techniques you can apply in your own organization.
Reactive Streams and the Wide World of Groovy
The concept of Reactive Streams (aka Reactive Extensions, Reactive Functional Programming, or simply Rx) has become increasingly popular recently, and with good reason. The Reactive Streams specification provides a universal abstraction for asynchronously processing data received across multiple sources (e.g. database, user input, third-party services), and includes mechanisms for controlling the rate at which data is received. This makes it a powerful tool within a Microservice platform. And did we mention that the Groovy lang community is quite involved?
In this talk we’ll explore the various features and concepts of Reactive Streams. We’ll talk about some typical use cases for Rx and more importantly, how to implement them. We’ll focus primarily on RxGroovy and Ratpack, then provide example implementations that show you how to get started with this powerful technique.
ProductCamp RTP 2010 - What the H*ell! - Adam Covati
The document discusses the experience of a product manager launching a new social media management and analytics tool called Argyle. It provides details about the founder's background, Argyle's timeline from initial development to full launch in under a year, strategies used such as iterating with customers and experimenting with minimal investments, and notes on selling the vision and raising funds in the startup triangle area.
Scaling Your Architecture for the Long Term
This talk from the virtual 2020 CTO Summit (https://www.ctoconnection.com/summits) covers several architecture lessons to help you survive and thrive through the scaling phase of your company:
* Modular Architecture
* Event-Driven Communication
* Quality and Reliability
* Continuous Delivery
Testing The Legacy: Making Existing Applications Testable Without Epic Efforts
If you have an established product which came about before the widespread use of the unit and system testing, then you know the problem.
The old code cannot be made testable without a significant effort of throwing it away and writing it anew.
What does it mean for the QA? It means endless repetitions of manual test runs. Sounds like fun? Yeah.. Nah!
In this presentation you will find two ways to make legacy applications testable through automation: an easy one, and a good one. The main benefit they provide is a basis for the further refactoring of the application, without damaging it.
Think of it as a Catch-22: you can't make your old app code testable without severely changing it, and you can't be sure that your changes work because you have no tests to verify them.
If you are a QA and you work with older apps and systems doing a lot of manual testing, then this is the topic for you.
This talk was given at ITx 2016 in Wellington, New Zealand, for Testing Professionals Network.
Demystifying the Role of Management in Agile
Often when an organisation introduces agile, management can be left wondering what their role is and how they can contribute. While some might suggest management should “just get out of the way” in my experience this is not the answer. Managers definitely have a role to play and an important one at that!
In this session Em will share her journey to becoming an Agile Leader. You will hear what made her start, the real world challenges she faced, the mistakes she made along the way and the secrets she discovered. Attendees at this session are sure to walk away with a new appreciation of the role of managers in agile organisations and plenty of practical ideas that can be implemented in an organisation, regardless of whether they are agile or not!
Presentation at 1stConf 16th March 2015
An Introduction to jOOQ
Are you tired of Hibernate? Is GORM is too heavy for your current project? Do you like having more control over your SQL? Do you like flexible DSLs? Try JOOQ!
JOOQ (Java Object Oriented Querying) is light-weight alternative to classic data access solutions or ORMs like Hibernate, JPA, JDBC, and GORM. JOOQ's goal is to give the developer a flexible DSL for building typesafe, database agnostic SQL queries, and attempts to convince the developer of a ‘database-first’ approach to building their application. In this talk we’ll quickly present an introduction to JOOQ from a high level, discuss its features, and see several examples of how we’re using JOOQ to great effect with many Spring Boot and Ratpack apps within our platform.
Architecture & collaboration: The cornerstones of Continuous Delivery
The document discusses the importance of architecture, collaboration, and various patterns and anti-patterns related to continuous delivery. It notes that architecture and collaboration are cornerstones of continuous delivery. It then covers topics like evolutionary architecture, loose coupling, microservices, feature toggles, branch by abstraction, DevOps, value stream mapping, retrospectives, and more. Anti-patterns discussed include the big ball of mud, tight coupling, silos, and more.
Streaming ETL With Akka.NET
The document discusses building a streaming ETL pipeline using Akka.NET. It introduces the actor model as an alternative to shared state programming that allows building concurrent and distributed systems by modeling the system as actors that communicate asynchronously by message passing. The document provides an overview of Akka.NET and the actor model, demonstrating how actors can send and receive messages to process data streams in a reactive and resilient manner.
Introduction to Kanban
Kanban is a method for integrating lean principles into software project delivery. It focuses on visualizing workflow, limiting work-in-progress, and managing flow to improve the current process, reduce task switching, detect and address bottlenecks, and make priorities adaptable. Key aspects of Kanban include limiting WIP for each activity, exposing bottlenecks, measuring and tracking lead time and cycle time, and holding retrospectives to evaluate improvements and keep adjusting policies based on team feedback and data.
Web vitals are vitals - Aymen Loukil
The document discusses Google's Core Web Vitals metrics for measuring website performance. It covers the three metrics - Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. For each metric, it explains what the metric measures, how to measure it using lab and field tools, and provides optimizations to improve the metric such as reducing page size, prioritizing critical resources, and specifying element sizes. It also addresses frequently asked questions about the metrics and their impact on SEO and user experience. The overall message is that optimizing the Core Web Vitals will improve users' experience of a website which is important for both users and SEO.
Shifting is more than shifting left
Slides from Jesper Ottosen's 2017 Fall OnlineTestConf session – Shifting is more than shift left.
Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production.
This session was about a couple of other trends, changes, and shifts that are happening to testers and test managers.
– Shift-Coach, where It’s more about coaching teams.
– Shift-SME, where it’s more about business savvy.
– Shift-Deliver, where it’s more about the road to production
www.onlinetestconf.com
An Agile Approach to Machine Learning
Machine learning has become an important tool in the modern software toolbox, and high-performing organizations are increasingly coming to rely on data science and machine learning as a core part of their business. eBay introduced machine learning to its commerce search ranking and drove double-digit increases in revenue. Stitch Fix built a multibillion dollar clothing retail business in the US by combining the best of machines with the best of humans. And WeWork is bringing machine-learned approaches to the physical office environment all around the world. In all cases, algorithmic techniques started simple and slowly became more sophisticated over time. This talk will use these examples to derive an agile approach to machine learning, and will explore that approach across several different dimensions. We will set the stage by outlining the kinds of problems that are most amenable to machine-learned approaches as well as describing some important prerequisites, including investments in data quality, a robust data pipeline, and experimental discipline. Next, we will choose the right (algorithmic) tool for the right job, and suggest how to incrementally evolve the algorithmic approaches we bring to bear. Most fancy cutting-edge recommender systems in the real world, for example, started out with simple rules-based techniques or basic regression. Finally, we will integrate machine learning into the broader product development process, and see how it can help us to accelerate business results
Anatomy of Three Incidents -- Commonalities and Lessons
The best response to a system outage is not "What did you do?", but "What did we learn?" This session will walk through three system-wide outages at Google, at Stitch Fix, and at WeWork—their incidents, aftermaths, and recoveries. In all cases, many things went right and a few went wrong; also in all cases, because of blameless cultures, we buckled down, learned a lot, and made substantial improvements in the systems for the future. Looking back with the perspective of 20-20 hindsight, all of these incidents were seminal events that changed the focus and trajectory of engineering at each organization. You will leave with a set of actionable suggestions in dealing with customers, engineering teams, and upper management. You will also enjoy a few war stories from the trenches.
Concurrency, Without the Pain: An Intro to Akka.NET @ Bay.NET
This document contains the slides and notes from a presentation on Akka.NET and the actor model given by Andrew Skotzko to the Bay.NET User Group. It introduces the challenges of writing multithreaded and concurrent code, describes how the actor model addresses these issues through message passing between isolated actors, and provides an overview of Akka.NET's implementation of the actor model for .NET applications. The presentation includes examples of actor messaging and demonstrates Akka.NET's features like hierarchies, supervision, and behavior switching.
Dev productivity hacks - Cognitive Biases and Friction for Software Developers
This presentation talks about Cognitive Biases and Friction in programming. I provide some solutions to these common issues and propose how GrepPage can help solving some of them.
Akka.NET Fundamentals — #ProgNet15
The document is a presentation on Akka.NET and the actor model. It begins by introducing the speaker and stating the topics that will be covered, including an overview of the actor model and hands-on experience with Akka.NET fundamentals. It then discusses why concurrency is important and the challenges of traditional multithreaded programming. The bulk of the presentation focuses on explaining the actor model and how Akka.NET implements it on the .NET platform, including how actors communicate through message passing and how this addresses issues with shared state. Examples of where the actor model can be applied are provided.
Part of the pipeline-why continuous testing is essential - velocity conf
This document discusses the importance of continuous testing for software delivery at Capital One. Capital One has adopted a DevOps approach to software development, building its own software on public clouds using microservices and open source technologies. Continuous testing is essential to deliver high quality, secure software quickly at Capital One. It allows for testing at all stages of the development pipeline, including unit testing, security testing, and testing across lines of business and third parties. While continuous testing poses challenges related to test environments and dependencies, the document proposes solutions like using cloud infrastructure and service virtualization to address them. Strong visibility into the testing process and people resources are also important for scaling continuous testing.
Reactive All the Way Down the Stack
Reactive applications & reactive programming result in flexible, concise, performant code and are a superior alternative to the old thread-based programming model. The reactive approach has gained popularity for a simple reason: we need alternative designs and architectures to meet today’s demands. However, it can be difficult to shift one’s mind to think in reactive terms, particularly when one realizes that we must be Reactive up and down the entire programming stack.
In this talk we’ll explore what it means to be ‘Reactive’. We’ll examine some of the more interesting tools available to us, some of which come from the Groovy community. Specifically we’ll cover Ratpack, RxGroovy, React, and RabbitMq - along with examples and a sample implementation. We’ll demonstrate how effectively they can work together at each level of the stack - from the front end, to the back end, to handling http requests and message queue events - and how easy it can be to go Reactive all the way down.
DOES16 London - Amy Phillips - Is Your Gatekeeper Locking Out Quality?
Is Your Gatekeeper Locking Out Quality?
Amy Phillips, Head of Test, Songkick
Releasing software is scary. As a tester the fear of breaking things comes with the added pressure that you were responsible for the testing. Testers and people working with testers often expect that testing alone is the determiner of quality releases. When the product doesn’t meet expectations more safely checks get added to the testing and release process. Over time testers can easily become gatekeepers as they try to protect users from poor quality products.
Unfortunately quality is about far more than just testing.
In this experience report, Amy Phillips, with your help, will explore what quality is and look at the ways that Continuous Delivery can help deliver it. A look back over the last 6 years of Songkick development processes will show how removing gatekeepers allowed Songkick to unlock their release cycle and start shipping quality features multiple times a day.
DevOps Enterprise Summit London 2016
Lean Kanban India 2016 | Achieving the potential of Kanban: Use LEAN | Avinas...
- The document describes using Kanban to manage two IT projects, with mixed results. The first project was successful by stopping estimates and using a Kanban board, but applying the same approach to the second project led to issues.
- For the factory migration project, the Kanban board was underutilized at first due to low demand. Later, work piled up at testing due to insufficient testing resources. Applying WIP limits also increased development capacity needs.
- Realizing the issues, the team took stock and reviewed why Kanban improves throughput, such as averaging variability. The second implementation lacked a defined process, role clarity, and alignment on goals like the first successful project. Deep implementation of Kanban requires both political
Agile and waterfall tango dancing
In today's world developing complex projects is becoming more and more challenging.
I am a strong believer that switching to Agile is the right move to help deal with these challenges, But the question is "How?"
Doing the transition too dramatically may actually create the negative effect, and in order to change many years of corporate culture and we need to focus on working with the managers to do this.
In this talk i will present based on my own experience several tips on how an architect can assist in Agile transition by influencing the relevant managers.
A traditional team's agile transformation
This document summarizes a presentation about transforming a traditional team to agile. It discusses how the current environment requires more agility to address changing needs. It then contrasts the waterfall vs agile approaches. The presentation covers transforming the organization, processes, engineering practices and product management to be more agile. This includes shifting to a feature team structure, implementing scrum, continuous integration and emphasizing working software over documentation. Benefits of the agile transformation include delivering value earlier, receiving more feedback and adapting faster to change.
Transition network web service update 131113
The document summarizes a staff meeting at Transition Network to discuss updating their web service. It provides background on the history and growth of the web service. It then likens the current web service to an old apple tree that needs pruning to update outdated platforms and software. Ideas for pruning include focusing content around Transition Network's core roles and strategic vision, and developing a clear information architecture and support framework based on Transition principles. A tentative timeline is proposed to redesign the web service in phases over the next year through staff collaboration and stakeholder input.
Polymer State of the Union - Chrome Dev Summit 2014
Polymer is a library for building web applications using web components. The next major version, Polymer 0.8, has been optimized for performance and modularity - it is faster, lighter in size, and its features are organized into optional layers. The updates are aimed at making Polymer production-ready while maintaining the features developers enjoy. Polyfills are being moved to webcomponents.org to streamline Polymer's core functionality of enabling web components, and many companies are already using Polymer in their applications.
Transitioning to Kanban: From Theory to Practice
You're familiar with agile and, perhaps, practicing Scrum. Now you're curious about Kanban. Is it right for your project? How does Kanban differ from Scrum and other agile methodologies? From theory to practice, Gil Irizarry introduces Kanban principles and explains how Kanban's emphasis on modifying existing processes rather than upending them results in a smooth adoption. Instead of using time-boxed units of work, Kanban focuses on continuous workflow, allowing teams to incrementally improve and streamline product delivery. Explore how to move from Scrum to Kanban with new, practical techniques that can help your team quickly get better. Discover the use of cumulative flow diagrams, WIP (work-in-progress) limits, and classes of services. In a hands-on classroom exercise, you'll help create a value stream map, determine process efficiency, and experience techniques from the Kanban toolset. Come and grow your agile repertoire in the Kanban way.
Cross Platform Angular 2 and TypeScript Development
Jeremy Likness explains why Angular is a powerful front end web technology, then demonstrates a cross-platform approach to building Angular 2 apps using NodeJs, Visual Studio Code, and TypeScript.
More Related Content
What's hot
Demystifying the Role of Management in Agile
Often when an organisation introduces agile, management can be left wondering what their role is and how they can contribute. While some might suggest management should “just get out of the way” in my experience this is not the answer. Managers definitely have a role to play and an important one at that!
In this session Em will share her journey to becoming an Agile Leader. You will hear what made her start, the real world challenges she faced, the mistakes she made along the way and the secrets she discovered. Attendees at this session are sure to walk away with a new appreciation of the role of managers in agile organisations and plenty of practical ideas that can be implemented in an organisation, regardless of whether they are agile or not!
Presentation at 1stConf 16th March 2015
An Introduction to jOOQ
Are you tired of Hibernate? Is GORM is too heavy for your current project? Do you like having more control over your SQL? Do you like flexible DSLs? Try JOOQ!
JOOQ (Java Object Oriented Querying) is light-weight alternative to classic data access solutions or ORMs like Hibernate, JPA, JDBC, and GORM. JOOQ's goal is to give the developer a flexible DSL for building typesafe, database agnostic SQL queries, and attempts to convince the developer of a ‘database-first’ approach to building their application. In this talk we’ll quickly present an introduction to JOOQ from a high level, discuss its features, and see several examples of how we’re using JOOQ to great effect with many Spring Boot and Ratpack apps within our platform.
Architecture & collaboration: The cornerstones of Continuous Delivery
The document discusses the importance of architecture, collaboration, and various patterns and anti-patterns related to continuous delivery. It notes that architecture and collaboration are cornerstones of continuous delivery. It then covers topics like evolutionary architecture, loose coupling, microservices, feature toggles, branch by abstraction, DevOps, value stream mapping, retrospectives, and more. Anti-patterns discussed include the big ball of mud, tight coupling, silos, and more.
Streaming ETL With Akka.NET
The document discusses building a streaming ETL pipeline using Akka.NET. It introduces the actor model as an alternative to shared state programming that allows building concurrent and distributed systems by modeling the system as actors that communicate asynchronously by message passing. The document provides an overview of Akka.NET and the actor model, demonstrating how actors can send and receive messages to process data streams in a reactive and resilient manner.
Introduction to Kanban
Kanban is a method for integrating lean principles into software project delivery. It focuses on visualizing workflow, limiting work-in-progress, and managing flow to improve the current process, reduce task switching, detect and address bottlenecks, and make priorities adaptable. Key aspects of Kanban include limiting WIP for each activity, exposing bottlenecks, measuring and tracking lead time and cycle time, and holding retrospectives to evaluate improvements and keep adjusting policies based on team feedback and data.
Web vitals are vitals - Aymen Loukil
The document discusses Google's Core Web Vitals metrics for measuring website performance. It covers the three metrics - Largest Contentful Paint, First Input Delay, and Cumulative Layout Shift. For each metric, it explains what the metric measures, how to measure it using lab and field tools, and provides optimizations to improve the metric such as reducing page size, prioritizing critical resources, and specifying element sizes. It also addresses frequently asked questions about the metrics and their impact on SEO and user experience. The overall message is that optimizing the Core Web Vitals will improve users' experience of a website which is important for both users and SEO.
Shifting is more than shifting left
Slides from Jesper Ottosen's 2017 Fall OnlineTestConf session – Shifting is more than shift left.
Change is happening to the testing activities. Shift-left automates and codifies the testing activities. Shift-right does it for production.
This session was about a couple of other trends, changes, and shifts that are happening to testers and test managers.
– Shift-Coach, where It’s more about coaching teams.
– Shift-SME, where it’s more about business savvy.
– Shift-Deliver, where it’s more about the road to production
www.onlinetestconf.com
An Agile Approach to Machine Learning
Machine learning has become an important tool in the modern software toolbox, and high-performing organizations are increasingly coming to rely on data science and machine learning as a core part of their business. eBay introduced machine learning to its commerce search ranking and drove double-digit increases in revenue. Stitch Fix built a multibillion dollar clothing retail business in the US by combining the best of machines with the best of humans. And WeWork is bringing machine-learned approaches to the physical office environment all around the world. In all cases, algorithmic techniques started simple and slowly became more sophisticated over time. This talk will use these examples to derive an agile approach to machine learning, and will explore that approach across several different dimensions. We will set the stage by outlining the kinds of problems that are most amenable to machine-learned approaches as well as describing some important prerequisites, including investments in data quality, a robust data pipeline, and experimental discipline. Next, we will choose the right (algorithmic) tool for the right job, and suggest how to incrementally evolve the algorithmic approaches we bring to bear. Most fancy cutting-edge recommender systems in the real world, for example, started out with simple rules-based techniques or basic regression. Finally, we will integrate machine learning into the broader product development process, and see how it can help us to accelerate business results
Anatomy of Three Incidents -- Commonalities and Lessons
The best response to a system outage is not "What did you do?", but "What did we learn?" This session will walk through three system-wide outages at Google, at Stitch Fix, and at WeWork—their incidents, aftermaths, and recoveries. In all cases, many things went right and a few went wrong; also in all cases, because of blameless cultures, we buckled down, learned a lot, and made substantial improvements in the systems for the future. Looking back with the perspective of 20-20 hindsight, all of these incidents were seminal events that changed the focus and trajectory of engineering at each organization. You will leave with a set of actionable suggestions in dealing with customers, engineering teams, and upper management. You will also enjoy a few war stories from the trenches.
Concurrency, Without the Pain: An Intro to Akka.NET @ Bay.NET
This document contains the slides and notes from a presentation on Akka.NET and the actor model given by Andrew Skotzko to the Bay.NET User Group. It introduces the challenges of writing multithreaded and concurrent code, describes how the actor model addresses these issues through message passing between isolated actors, and provides an overview of Akka.NET's implementation of the actor model for .NET applications. The presentation includes examples of actor messaging and demonstrates Akka.NET's features like hierarchies, supervision, and behavior switching.
Dev productivity hacks - Cognitive Biases and Friction for Software Developers
This presentation talks about Cognitive Biases and Friction in programming. I provide some solutions to these common issues and propose how GrepPage can help solving some of them.
Akka.NET Fundamentals — #ProgNet15
The document is a presentation on Akka.NET and the actor model. It begins by introducing the speaker and stating the topics that will be covered, including an overview of the actor model and hands-on experience with Akka.NET fundamentals. It then discusses why concurrency is important and the challenges of traditional multithreaded programming. The bulk of the presentation focuses on explaining the actor model and how Akka.NET implements it on the .NET platform, including how actors communicate through message passing and how this addresses issues with shared state. Examples of where the actor model can be applied are provided.
Part of the pipeline-why continuous testing is essential - velocity conf
This document discusses the importance of continuous testing for software delivery at Capital One. Capital One has adopted a DevOps approach to software development, building its own software on public clouds using microservices and open source technologies. Continuous testing is essential to deliver high quality, secure software quickly at Capital One. It allows for testing at all stages of the development pipeline, including unit testing, security testing, and testing across lines of business and third parties. While continuous testing poses challenges related to test environments and dependencies, the document proposes solutions like using cloud infrastructure and service virtualization to address them. Strong visibility into the testing process and people resources are also important for scaling continuous testing.
Reactive All the Way Down the Stack
Reactive applications & reactive programming result in flexible, concise, performant code and are a superior alternative to the old thread-based programming model. The reactive approach has gained popularity for a simple reason: we need alternative designs and architectures to meet today’s demands. However, it can be difficult to shift one’s mind to think in reactive terms, particularly when one realizes that we must be Reactive up and down the entire programming stack.
In this talk we’ll explore what it means to be ‘Reactive’. We’ll examine some of the more interesting tools available to us, some of which come from the Groovy community. Specifically we’ll cover Ratpack, RxGroovy, React, and RabbitMq - along with examples and a sample implementation. We’ll demonstrate how effectively they can work together at each level of the stack - from the front end, to the back end, to handling http requests and message queue events - and how easy it can be to go Reactive all the way down.
DOES16 London - Amy Phillips - Is Your Gatekeeper Locking Out Quality?
Is Your Gatekeeper Locking Out Quality?
Amy Phillips, Head of Test, Songkick
Releasing software is scary. As a tester the fear of breaking things comes with the added pressure that you were responsible for the testing. Testers and people working with testers often expect that testing alone is the determiner of quality releases. When the product doesn’t meet expectations more safely checks get added to the testing and release process. Over time testers can easily become gatekeepers as they try to protect users from poor quality products.
Unfortunately quality is about far more than just testing.
In this experience report, Amy Phillips, with your help, will explore what quality is and look at the ways that Continuous Delivery can help deliver it. A look back over the last 6 years of Songkick development processes will show how removing gatekeepers allowed Songkick to unlock their release cycle and start shipping quality features multiple times a day.
DevOps Enterprise Summit London 2016
What's hot (15)
Architecture & collaboration: The cornerstones of Continuous Delivery
Architecture & collaboration: The cornerstones of Continuous Delivery
Anatomy of Three Incidents -- Commonalities and Lessons
Anatomy of Three Incidents -- Commonalities and Lessons
Concurrency, Without the Pain: An Intro to Akka.NET @ Bay.NET
Concurrency, Without the Pain: An Intro to Akka.NET @ Bay.NET
Dev productivity hacks - Cognitive Biases and Friction for Software Developers
Dev productivity hacks - Cognitive Biases and Friction for Software Developers
Part of the pipeline-why continuous testing is essential - velocity conf
Part of the pipeline-why continuous testing is essential - velocity conf
DOES16 London - Amy Phillips - Is Your Gatekeeper Locking Out Quality?
DOES16 London - Amy Phillips - Is Your Gatekeeper Locking Out Quality?
Similar to ELAG 2016: Going Live - The highs and lows of getting a project into service
Lean Kanban India 2016 | Achieving the potential of Kanban: Use LEAN | Avinas...
- The document describes using Kanban to manage two IT projects, with mixed results. The first project was successful by stopping estimates and using a Kanban board, but applying the same approach to the second project led to issues.
- For the factory migration project, the Kanban board was underutilized at first due to low demand. Later, work piled up at testing due to insufficient testing resources. Applying WIP limits also increased development capacity needs.
- Realizing the issues, the team took stock and reviewed why Kanban improves throughput, such as averaging variability. The second implementation lacked a defined process, role clarity, and alignment on goals like the first successful project. Deep implementation of Kanban requires both political
Agile and waterfall tango dancing
In today's world developing complex projects is becoming more and more challenging.
I am a strong believer that switching to Agile is the right move to help deal with these challenges, But the question is "How?"
Doing the transition too dramatically may actually create the negative effect, and in order to change many years of corporate culture and we need to focus on working with the managers to do this.
In this talk i will present based on my own experience several tips on how an architect can assist in Agile transition by influencing the relevant managers.
A traditional team's agile transformation
This document summarizes a presentation about transforming a traditional team to agile. It discusses how the current environment requires more agility to address changing needs. It then contrasts the waterfall vs agile approaches. The presentation covers transforming the organization, processes, engineering practices and product management to be more agile. This includes shifting to a feature team structure, implementing scrum, continuous integration and emphasizing working software over documentation. Benefits of the agile transformation include delivering value earlier, receiving more feedback and adapting faster to change.
Transition network web service update 131113
The document summarizes a staff meeting at Transition Network to discuss updating their web service. It provides background on the history and growth of the web service. It then likens the current web service to an old apple tree that needs pruning to update outdated platforms and software. Ideas for pruning include focusing content around Transition Network's core roles and strategic vision, and developing a clear information architecture and support framework based on Transition principles. A tentative timeline is proposed to redesign the web service in phases over the next year through staff collaboration and stakeholder input.
Polymer State of the Union - Chrome Dev Summit 2014
Polymer is a library for building web applications using web components. The next major version, Polymer 0.8, has been optimized for performance and modularity - it is faster, lighter in size, and its features are organized into optional layers. The updates are aimed at making Polymer production-ready while maintaining the features developers enjoy. Polyfills are being moved to webcomponents.org to streamline Polymer's core functionality of enabling web components, and many companies are already using Polymer in their applications.
Transitioning to Kanban: From Theory to Practice
You're familiar with agile and, perhaps, practicing Scrum. Now you're curious about Kanban. Is it right for your project? How does Kanban differ from Scrum and other agile methodologies? From theory to practice, Gil Irizarry introduces Kanban principles and explains how Kanban's emphasis on modifying existing processes rather than upending them results in a smooth adoption. Instead of using time-boxed units of work, Kanban focuses on continuous workflow, allowing teams to incrementally improve and streamline product delivery. Explore how to move from Scrum to Kanban with new, practical techniques that can help your team quickly get better. Discover the use of cumulative flow diagrams, WIP (work-in-progress) limits, and classes of services. In a hands-on classroom exercise, you'll help create a value stream map, determine process efficiency, and experience techniques from the Kanban toolset. Come and grow your agile repertoire in the Kanban way.
Cross Platform Angular 2 and TypeScript Development
Jeremy Likness explains why Angular is a powerful front end web technology, then demonstrates a cross-platform approach to building Angular 2 apps using NodeJs, Visual Studio Code, and TypeScript.
Addressing the DevOps Resilience Challenge
This document discusses the need for software systems to be resilient to change and failures in order to support business agility. It argues that traditional notions of quality focus too much on preventing defects rather than automatic recovery from problems. A key principle is that software should be built with resilience and flexibility in mind from the start rather than just to meet current needs, as the latter approach leads to brittle systems. The document also examines how DevOps practices aim to balance quality, agility, and resilience through continuous integration, testing more in production environments, and managing technical debt.
Scrum & Kanban Introduction
This document provides an overview of Agile development methods Scrum and Kanban. It defines Scrum roles like Product Owner and Scrum Master, and processes like sprints, daily stand-ups, and retrospectives. Sprints are time-boxed iterations where a cross-functional team works on user stories to deliver working software. Kanban uses visual boards and limits work-in-progress to manage workflow and continuously improve processes through small experiments. While Scrum is more prescriptive, both are empirical and aim to deliver value continuously through feedback loops.
From the Trenches: Building the Accessible Web
Jon Reid, Senior Developer at EffectiveUI, presented "From the Trenches: A Practical Approach to Building the Accessible Web" at Accessing Higher Ground 2010, an accessible media, web and technology conference hosted by the University of Colorado at Boulder.
Microservices - Scaling Development and Service
This document discusses microservices and provides recommendations for developing microservice architectures. It begins by comparing experiences developing large and small systems. Microservices are then defined as independently deployable services that communicate via lightweight mechanisms like HTTP. Examples are provided of companies that pioneered microservices like Amazon and Netflix. The document concludes by recommending developers start small with microservices, focus on principles over specific technologies, and address challenges of distributed systems through monitoring, resilience patterns, and infrastructure support.
From the Trenches: Building the Accessible Web
The document discusses building accessible websites from a practical perspective. It addresses how accessibility can fall by the wayside due to roadblocks from stakeholders, designers, and developers. It advocates keeping goals realistic and using progressive enhancement, where the basic accessible content and structure is provided first before other enhancements. An example project for the Blue Angels website is described where progressive enhancement was applied during the definition, design, and development phases while maintaining an audit trail.
Carpe Digital
The document outlines the history of connecting various initiatives to create the Norwick Center for Digital Services at Southern Methodist University. It discusses how the center was formed by (1) creating a student multimedia center and library digital projects division, (2) implementing strategic digital collections, and (3) reducing non-library services over time. It then describes obstacles faced and strategies used to overcome them, including leveraging resources, thinking creatively, promoting the new center, and paying ongoing attention to ensure its success.
3.28.18 "Open Source Repository Upgrades: Top Advice from Practitioners" Pres...
This document summarizes advice from practitioners on open source repository upgrades and migrations. The advice falls into four categories: planning, metadata normalization, migration, and verification. Planning and metadata normalization are emphasized as the most complex parts of the process. Effective planning involves stakeholder communication, team building, testing tools, and defining requirements and scope. Metadata normalization through enrichment projects is recommended before migrating to improve data quality. During migration, an iterative approach and flexibility are advised. Verification includes checksum validation, object and identifier checks, and manual reviews. Thorough documentation, reflection, and knowledge sharing are also stressed.
Microservices and APIs
The document discusses microservices and APIs. It covers how microservices optimize for speed by shedding dependencies and having dependencies on demand through services and APIs. It discusses consumer contracts for APIs and service versioning. It also discusses using an API gateway pattern for scalability, security, monitoring and more. It promotes API management for benefits like access control, analytics, and monetization of microservices.
Surviving in a Microservices environment -abridged
Many presentations on Microservices offer a high-level view; rarely does one hear what it’s like to work in such an environment. Individual services are somewhat trivial to develop, but now you suddenly have countless others to track. You’ll become obsessed over how they communicate. You’ll have to start referring to the whole thing as “the Platform”. You will have to take on some considerable DevOps work and start learning about deployment pipelines, metrics, and logging.
Don’t panic. In this presentation we’ll discuss what we learned over the past four years by highlighting our mistakes. We’ll examine what a development lifecycle might look like for adding a new service, developing a feature, or fixing bugs. We’ll see how team communication is more important than one might realize. Most importantly, we’ll show how - while an individual service is simple - the infrastructure demands are now much more complicated: your organization will need to introduce and become increasingly dependent on various technologies, procedures, and tools - ranging from the ELK stack to Grafana to Kubernetes. Lastly, you’ll come away with the understanding that your resident SREs will become the most valued members of your team.
Service Architectures at Scale
How do effective large-scale service ecosystems work? Keynote Presentation at Istanbul Tech Talks 2018
How to Design Services
* Systems of record
* Interface specification
* Interface backward / forward compatibility
Service Ecosystems
* Layered services
* "Standardization" through encouragement
* Vendor-customer relationships between teams
Operating and Deploying Services
* Data Migration
* Automated Pipelines
* Incremental Deployment
* Feature Flags
Scrum is good - but kanban is better
Scrum is a great way to start practising Agile. But it's not perfect. Are you struggling to get stories tested within the sprint? I sprint planning taking hours and making everyone miserable? These are the slides from the session I presented at Agile Cymru 2016, describing the experience of one team that moved from Scrum to Kanban.
Scaling Agile in the Enterprise
The document discusses scaling agile practices in large enterprises. It begins by outlining the origins of agile in 2001 as an alternative to documentation-heavy processes. It then discusses challenges that enterprises face in scaling agile, including process/documentation cultures, underestimating planning efforts, and complex infrastructure. The document proposes a 3-step approach: setting up an agile implementation team, having IT management lead by example, and continuously solving impediments. It recommends using tools like JIRA and SAFe to plan at the portfolio, program, and team levels to help scale agile practices across large organizations.
A Journey Through Agile in the Government
This document summarizes Richard Cheng's experience helping various government agencies adopt Agile practices. It describes projects from 2008-2011 at the Office of Personnel Management, USAJOBS, and establishing the Agile Delivery for Agencies, Programs, and Teams community. Key challenges discussed are contracts and procurement, governance, scaling Agile, and overcoming legacy culture and processes. The document advocates for incremental delivery, empirical process control, and building communities to foster transformation to Agile in government.
Similar to ELAG 2016: Going Live - The highs and lows of getting a project into service (20)
Lean Kanban India 2016 | Achieving the potential of Kanban: Use LEAN | Avinas...
Lean Kanban India 2016 | Achieving the potential of Kanban: Use LEAN | Avinas...
Polymer State of the Union - Chrome Dev Summit 2014
Polymer State of the Union - Chrome Dev Summit 2014
Cross Platform Angular 2 and TypeScript Development
Cross Platform Angular 2 and TypeScript Development
3.28.18 "Open Source Repository Upgrades: Top Advice from Practitioners" Pres...
3.28.18 "Open Source Repository Upgrades: Top Advice from Practitioners" Pres...
Surviving in a Microservices environment -abridged
Surviving in a Microservices environment -abridged
Recently uploaded
How to Fix [Errno 98] address already in use
This slide will represent the cause of the error “[Errno 98] address already in use” and the troubleshooting steps to resolve this error in Odoo.
skeleton System.pdf (skeleton system wow)
🔥🔥🔥🔥🔥🔥🔥🔥🔥
إضغ بين إيديكم من أقوى الملازم التي صممتها
ملزمة تشريح الجهاز الهيكلي (نظري 3)
💀💀💀💀💀💀💀💀💀💀
تتميز هذهِ الملزمة بعِدة مُميزات :
1- مُترجمة ترجمة تُناسب جميع المستويات
2- تحتوي على 78 رسم توضيحي لكل كلمة موجودة بالملزمة (لكل كلمة !!!!)
#فهم_ماكو_درخ
3- دقة الكتابة والصور عالية جداً جداً جداً
4- هُنالك بعض المعلومات تم توضيحها بشكل تفصيلي جداً (تُعتبر لدى الطالب أو الطالبة بإنها معلومات مُبهمة ومع ذلك تم توضيح هذهِ المعلومات المُبهمة بشكل تفصيلي جداً
5- الملزمة تشرح نفسها ب نفسها بس تكلك تعال اقراني
6- تحتوي الملزمة في اول سلايد على خارطة تتضمن جميع تفرُعات معلومات الجهاز الهيكلي المذكورة في هذهِ الملزمة
واخيراً هذهِ الملزمة حلالٌ عليكم وإتمنى منكم إن تدعولي بالخير والصحة والعافية فقط
كل التوفيق زملائي وزميلاتي ، زميلكم محمد الذهبي 💊💊
🔥🔥🔥🔥🔥🔥🔥🔥🔥
How to Setup Default Value for a Field in Odoo 17
In Odoo, we can set a default value for a field during the creation of a record for a model. We have many methods in odoo for setting a default value to the field.
HYPERTENSION - SLIDE SHARE PRESENTATION.
IT WILL BE HELPFULL FOR THE NUSING STUDENTS
IT FOCUSED ON MEDICAL MANAGEMENT AND NURSING MANAGEMENT.
HIGHLIGHTS ON HEALTH EDUCATION.
Geography as a Discipline Chapter 1 __ Class 11 Geography NCERT _ Class Notes...
Geography as discipline
How to Download & Install Module From the Odoo App Store in Odoo 17
Custom modules offer the flexibility to extend Odoo's capabilities, address unique requirements, and optimize workflows to align seamlessly with your organization's processes. By leveraging custom modules, businesses can unlock greater efficiency, productivity, and innovation, empowering them to stay competitive in today's dynamic market landscape. In this tutorial, we'll guide you step by step on how to easily download and install modules from the Odoo App Store.
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...
Andreas Schleicher, Director of Education and Skills at the OECD presents at the launch of PISA 2022 Volume III - Creative Minds, Creative Schools on 18 June 2024.
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 8 - CẢ NĂM - FRIENDS PLUS - NĂM HỌC 2023-2024 (B...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 8 - CẢ NĂM - FRIENDS PLUS - NĂM HỌC 2023-2024 (B...Nguyen Thanh Tu Collection
https://app.box.com/s/nrwz52lilmrw6m5kqeqn83q6vbdp8yzpTHE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...
The recent surge in pro-Palestine student activism has prompted significant responses from universities, ranging from negotiations and divestment commitments to increased transparency about investments in companies supporting the war on Gaza. This activism has led to the cessation of student encampments but also highlighted the substantial sacrifices made by students, including academic disruptions and personal risks. The primary drivers of these protests are poor university administration, lack of transparency, and inadequate communication between officials and students. This study examines the profound emotional, psychological, and professional impacts on students engaged in pro-Palestine protests, focusing on Generation Z's (Gen-Z) activism dynamics. This paper explores the significant sacrifices made by these students and even the professors supporting the pro-Palestine movement, with a focus on recent global movements. Through an in-depth analysis of printed and electronic media, the study examines the impacts of these sacrifices on the academic and personal lives of those involved. The paper highlights examples from various universities, demonstrating student activism's long-term and short-term effects, including disciplinary actions, social backlash, and career implications. The researchers also explore the broader implications of student sacrifices. The findings reveal that these sacrifices are driven by a profound commitment to justice and human rights, and are influenced by the increasing availability of information, peer interactions, and personal convictions. The study also discusses the broader implications of this activism, comparing it to historical precedents and assessing its potential to influence policy and public opinion. The emotional and psychological toll on student activists is significant, but their sense of purpose and community support mitigates some of these challenges. However, the researchers call for acknowledging the broader Impact of these sacrifices on the future global movement of FreePalestine.
Recently uploaded (20)
SWOT analysis in the project Keeping the Memory @live.pptx
SWOT analysis in the project Keeping the Memory @live.pptx
220711130088 Sumi Basak Virtual University EPC 3.pptx
220711130088 Sumi Basak Virtual University EPC 3.pptx
spot a liar (Haiqa 146).pptx Technical writhing and presentation skills
spot a liar (Haiqa 146).pptx Technical writhing and presentation skills
REASIGNACION 2024 UGEL CHUPACA 2024 UGEL CHUPACA.pdf
REASIGNACION 2024 UGEL CHUPACA 2024 UGEL CHUPACA.pdf
Geography as a Discipline Chapter 1 __ Class 11 Geography NCERT _ Class Notes...
Geography as a Discipline Chapter 1 __ Class 11 Geography NCERT _ Class Notes...
How to Download & Install Module From the Odoo App Store in Odoo 17
How to Download & Install Module From the Odoo App Store in Odoo 17
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...
Andreas Schleicher presents PISA 2022 Volume III - Creative Thinking - 18 Jun...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 8 - CẢ NĂM - FRIENDS PLUS - NĂM HỌC 2023-2024 (B...
BÀI TẬP BỔ TRỢ TIẾNG ANH LỚP 8 - CẢ NĂM - FRIENDS PLUS - NĂM HỌC 2023-2024 (B...
THE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...
THE SACRIFICE HOW PRO-PALESTINE PROTESTS STUDENTS ARE SACRIFICING TO CHANGE T...
ELAG 2016: Going Live - The highs and lows of getting a project into service
- 2. Ciaran Talbot @ciaran_talbot Library Systems Manager The University of Manchester Library Going live? The highs and lows of getting a project into service
- 4. CC BY 2.0 Image courtesy of Bill Ward on Flickr https://www.flickr.com/photos/billward/3413627084/ Build
- 5. CC BY 2.0 Image courtesy of Mike on Flickr https://www.flickr.com/photos/pmiaki/4371642740/ Run
- 6. Build it Run it
- 10. The Alma implementation project • Project size: pretty big • Drivers: consolidation, rationalisation
- 11. Jan ‘13 Feb March Apr May Jun Jul Aug Sep Oct Nov The Alma implementation project Project Service?
- 12. How did the transition go? What went well? • Data migration • Devolvement
- 13. How did the transition go? What did not go so well? • Staff user expectations
- 14. How do we evaluate the effectiveness of transitions?
- 18. How did the transition go? What did not go so well? • Staff user expectations • Unexpected consequences
- 20. The Alma implementation project Project Service Too much concentration here Go Live But, not enough here
- 22. BookedIn
- 23. BookedIn • Project size: medium, collaboration • Drivers: “innovation”
- 24. BookedIn Project Timeline • Kick-off 5th June 2013 BookedIn June July August September October Novembe
- 25. BookedIn Project Timeline • Launch January 2014 BookedIn June July August September October Novembe
- 26. BookedIn Project Timeline • Slippage BookedIn June 2013 July August September October November December January 2014 February
- 27. BookedIn Project Timeline • Slippier BookedIn Jun ‘13 Jul Aug Sep Oct Nov Dec Jan ‘14 Feb March Apr May Jun
- 28. BookedIn Project Timeline • Reality BookedIn Jan ‘14 Feb March Apr May Jun Jul Aug Sep Oct Nov
- 32. How did the transition go? What went well? • Collaboration • Trying something a bit different
- 33. How did the transition go? What did not go so well? • Project and support = same people • The eternal pilot • Did we transition?
- 34. CheckOut App
- 35. CheckOut App Project size: quite small Drivers: curiosity, disruption
- 36. CheckOut App
- 39. How did the transition What went well? • Launching something pretty unique
- 40. How did the transition What did not go so well? • Tech outpaces policy
- 41. Does this all matter?
- 42. The challenge faced by the Library professional CC BY-NC-SA 2.0 Image courtesy of Jameson Gagnepain on Flickr https://www.flickr.com/photos/jameson42/4209575299
- 43. Central IT 3rd Party Supplier Stakeholders Library You are here
- 44. Central IT
- 45. Central IT
- 47. Conclusion Project Service 1. We’re not bad at this Transition 3. But, to make this more effective 2. Or this 4. We should think about what to do here 5. Starting here!
- 48. Build it Run itEffective transition Conclusion = happier people, happier ser
- 49. Potential bonus round Exit self-service machines? (CheckOut demo)
- 50. @ciaran_talbot CC0 images sourced from Pixabay or Pexels Thanks & questions