DevOps is an emerging set of principles, methods, and practices that enable the rapid deployment of software systems. DevOps focuses on lowering barriers between development, testing, security, and operations in support of rapid iterative development and deployment. Many organizations struggle when implementing DevOps because of its inherent technical, process, and cultural challenges. Bob Aiello shares DevOps best practices starting with its role early in the application lifecycle and bridging the gap with testing, security, and operations. Bob explains how to implement DevOps using industry standards and frameworks such as ITIL v3 (IT Service Management) in both agile and non-agile environments, focusing on automated deployment frameworks that quickly deliver value to the business. DevOps includes server provisioning essential for cloud computing in what is becoming known as Infrastructure as Code. Bob equips you with practical and effective DevOps practices—automated application build, packaging, and deployment—essential for meeting today's business and technology demands.
Continuous Delivery: Rapid and Reliable Releases with DevOps PracticesTechWell
DevOps is an emerging set of principles, methods, and practices that empower teams and organizations to rapidly deploy systems and application updates while maintaining—and even improving—quality. By lowering barriers between development, testing, and operations, DevOps practices can add tremendous business value to software projects and systems. Bob Aiello explains how to prepare for and implement continuous delivery—in both agile and non-agile environments—employing industry standard processes and automated frameworks. Bob shares DevOps best practices starting with its role early in the application lifecycle through release and application maintenance. He introduces the emerging “Infrastructure as Code” concept that automates server and system provisioning within cloud computing environments. Learn ways to overcome technical, process, and cultural challenges with DevOps. Take back a set of practical and proven practices—for automated application build, automated packaging, and automated deployment—that will put your organization on the path to rapid and reliable releases.
This document discusses how Kanban and DevOps are related. It describes how Kanban practices like visualizing workflow, limiting work-in-progress, and creating feedback loops can help optimize flow and continuous improvement in DevOps. The document provides examples of applying Kanban techniques to problems in areas like flow, feedback, and risk management. It argues that Kanban is a natural fit for facilitating incremental changes in DevOps initiatives over time.
WTF: Where To Focus when you take over a Drupal projectSymetris
Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards.
During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.
Microservices - Scaling Development and ServicePaulo Gaspar
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.
Flight checks -QA for Releases that Prevent Disasters from Escaping into the ...Brie Hoblin
The document discusses flight checks and quality assurance for software releases to prevent disasters. It provides examples of past software disasters like the Mars Climate Orbiter that exploded due to using the wrong measurement units. The document defines a disaster as a bug that significantly harms a client or users. It discusses scenarios to determine if they constitute disasters and outlines factors to consider for deployment decisions, rollback vs hotfixing, and preventing disasters through quality assurance.
DOES15 - Randy Shoup - Ten (Hard-Won) Lessons of the DevOps TransitionGene Kim
Randy Shoup, Consulting CTO
DevOps is no longer just for Internet unicorns any more. Today many large enterprises are transitioning from the slow and siloed traditional IT approach to modern DevOps practices, and getting substantial improvements in agility, velocity, scalability, and efficiency. But this transition is not without its challenges and pitfalls, and those of us who have led this journey have the scar tissue to prove it.
A successful transition to DevOps practices ultimately involves changes to organization, to culture, and to architecture. Organizationally, we want to create multi-skilled teams with end-to-end ownership and shared on-call responsibilities. Culturally, we want to prioritize solving problems and improving the product over closing tickets. Architecturally, we want to move to an infrastructure with independently testable and deployable components.
The ten practical lessons outlined in this session synthesize the speaker’s experiences leading teams at eBay, Google, and KIXEYE, as well as from his current consulting practice.
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019Codemotion
Coolblue is a proud Dutch company, with a large internal development department; one that truly takes CI/CD to heart. Empowerment through automation is at the heart of these development teams, and with more than 1000 deployments a day, we think it's working out quite well. In this session, Pat Hermens (a Development Managers) will step you through what enables us to move so quickly, which tools we use, and most importantly, the mindset that is required to enable development teams to deliver at such a rapid pace.
Continuous Delivery: Rapid and Reliable Releases with DevOps PracticesTechWell
DevOps is an emerging set of principles, methods, and practices that empower teams and organizations to rapidly deploy systems and application updates while maintaining—and even improving—quality. By lowering barriers between development, testing, and operations, DevOps practices can add tremendous business value to software projects and systems. Bob Aiello explains how to prepare for and implement continuous delivery—in both agile and non-agile environments—employing industry standard processes and automated frameworks. Bob shares DevOps best practices starting with its role early in the application lifecycle through release and application maintenance. He introduces the emerging “Infrastructure as Code” concept that automates server and system provisioning within cloud computing environments. Learn ways to overcome technical, process, and cultural challenges with DevOps. Take back a set of practical and proven practices—for automated application build, automated packaging, and automated deployment—that will put your organization on the path to rapid and reliable releases.
This document discusses how Kanban and DevOps are related. It describes how Kanban practices like visualizing workflow, limiting work-in-progress, and creating feedback loops can help optimize flow and continuous improvement in DevOps. The document provides examples of applying Kanban techniques to problems in areas like flow, feedback, and risk management. It argues that Kanban is a natural fit for facilitating incremental changes in DevOps initiatives over time.
WTF: Where To Focus when you take over a Drupal projectSymetris
Jumping into pre-built Drupal projects sometimes requires a leap of faith as much for clients as for developers. The client is usually coming out of a bad previous business relationship and the code is not always structured according to your standards.
During this talk, Symetris will share its experience and provide tips on how to navigate these often uncharted waters. Our goal is to help you convert an uncertain client into a long term partner and have a checklist of what to look out for as developers.
Microservices - Scaling Development and ServicePaulo Gaspar
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.
Flight checks -QA for Releases that Prevent Disasters from Escaping into the ...Brie Hoblin
The document discusses flight checks and quality assurance for software releases to prevent disasters. It provides examples of past software disasters like the Mars Climate Orbiter that exploded due to using the wrong measurement units. The document defines a disaster as a bug that significantly harms a client or users. It discusses scenarios to determine if they constitute disasters and outlines factors to consider for deployment decisions, rollback vs hotfixing, and preventing disasters through quality assurance.
DOES15 - Randy Shoup - Ten (Hard-Won) Lessons of the DevOps TransitionGene Kim
Randy Shoup, Consulting CTO
DevOps is no longer just for Internet unicorns any more. Today many large enterprises are transitioning from the slow and siloed traditional IT approach to modern DevOps practices, and getting substantial improvements in agility, velocity, scalability, and efficiency. But this transition is not without its challenges and pitfalls, and those of us who have led this journey have the scar tissue to prove it.
A successful transition to DevOps practices ultimately involves changes to organization, to culture, and to architecture. Organizationally, we want to create multi-skilled teams with end-to-end ownership and shared on-call responsibilities. Culturally, we want to prioritize solving problems and improving the product over closing tickets. Architecturally, we want to move to an infrastructure with independently testable and deployable components.
The ten practical lessons outlined in this session synthesize the speaker’s experiences leading teams at eBay, Google, and KIXEYE, as well as from his current consulting practice.
Pat Hermens - From 100 to 1,000+ deployments a day - Codemotion Amsterdam 2019Codemotion
Coolblue is a proud Dutch company, with a large internal development department; one that truly takes CI/CD to heart. Empowerment through automation is at the heart of these development teams, and with more than 1000 deployments a day, we think it's working out quite well. In this session, Pat Hermens (a Development Managers) will step you through what enables us to move so quickly, which tools we use, and most importantly, the mindset that is required to enable development teams to deliver at such a rapid pace.
Using flow approaches to effectively manage agile testing at the enterprise l...Yuval Yeret
Slides from my upcoming LSSC11 talk:
More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm when talking about Big Batches, Wastes, ineffective handoffs and mountains of rework, as well as high transaction costs. I’ve recently been using Lean/Kanban flow based approaches to provide a way to evolve testing organizations to a more effective way of working, so that they can better support earlier feedback and higher flexibility. I will present this work as well as case studies from enterprise-level product development companies that are starting to use these approaches.
We will deal with the following challenges:
* Complex environments when it is not realistic to finish all required work within a sprint
* How to visualize and reduce testing batch sizes within sprints/releases using CFD
* How to deal with the testing bottleneck so common in product development organizations – practical suggestions and how to deal with the mindset issues
* How to run stabilization/hardening periods using Flow-based thinking
http://lssc11.crowdvine.com/talks/18074
Continuous Testing: Preparing for DevOpsSTePINForum
Digital transformation requires continuous testing to quickly adapt to changes and deliver value to customers. Traditional testing relies heavily on manual testing which is inefficient. Continuous testing uses test automation to test early and often through the development process. This shifts testing left and allows for more frequent testing of applications and APIs. Continuous testing leverages techniques like exploratory testing, test automation, and continuous integration to significantly increase testing efficiency and reduce risks. The goal is to close knowledge gaps through continuous and adaptive investigation.
01 why of dev ops - devopsguys - magentys - finalDevOpsGroup
This document discusses the reasons for adopting a DevOps approach and methodology. It outlines how business and technology environments have changed, putting pressure on development and operations teams. DevOps is presented as a way to help organizations react to these changes and deliver business value across the entire product lifecycle through practices like automation, collaboration, and continuous delivery. The document argues that DevOps can help organizations reduce costs and time-to-market while improving productivity.
The changing role of testing and test automation in the increasingly fast-paced world of continuous delivery and automated acceptance testing. Learn how, in a DevOps environment, testing activities start with requirements discovery and definition, playing a vital role in not only detecting defects, but preventing them, and ensuring not only that the features are built right, but the right features are built. And learn how test automation needs to happen during, not after, the sprint, and how you can achieve this.
Despite rumors to the contrary, the role of the tester is not diminished with the arrival of automated DevOps, with its ultra-rapid deployment cycles and its emphasis on automation. On the contrary, testers play a vital role in ensuring that the code that gets deployed ten times a day is worth deploying.
Continuous delivery a happier, safer alternative to release trainsThoughtworks
This document discusses principles and practices for continuous delivery including automating the build, deployment, testing and release process. It emphasizes reducing risk through techniques like feature toggles, blue-green deployments, canary releasing and implementing a production immune system. It also stresses the importance of collaboration between developers, testers and operations personnel.
The document discusses automating authorization and accreditation (A&A) processes through continuous compliance. It proposes treating compliance like test-driven development (TDD) and continuous delivery/DevOps by defining compliance requirements and controls using a common YAML schema. This would allow building automated pipelines to generate authorization artifacts like plans of action and milestones (POAMs) based on certification inputs and system details. The key is separating compliance components and logic from technical implementation details to enable unified code and compliance pipelines that can respond rapidly to security issues and deployment changes. OpenControl is presented as an open source project implementing this approach using common compliance standards, automation tools like Concourse, and a community for collaboration.
his talk will present the core concepts of Exponential Business Agility, or XBA. XBA is a set of patterns for organising value streams around self-organising, autonomous teams, and is part of the XSCALE approach to scaling agile. XBA combines the Spotify model with practice patterns drawn from the Iroquois Confederacy, the most successful and longest-lived holarchy in history.
Learn how Throughput Accounting optimises the contribution of each business function to top line throughput rather than blindly attempting to minimise operating expense.
And discover how Self-Propagating Transformation avoids pushing change into pre-existing teams, programs or silos, but generates agile capability by grafting the kernel of a new culture onto the trunk of the old.
Be a pod of dolphins, not a dancing elephant. Don’t try to scale agile. De-scale your organisation instead.
Moving to Continuous Delivery Without Breaking Your CodeXebiaLabs
This document summarizes Andrew Phillips' presentation on moving to continuous delivery without breaking code. The key points are:
1) Continuous delivery requires both fast execution of code deployments through automated pipelines as well as thorough testing and analysis to ensure high quality and avoid breaking code.
2) Testing practices need to change to keep up with continuous delivery by focusing on automation, functional coverage over technical coverage, and metrics on test quality.
3) A central hub is needed to aggregate testing data from across pipelines and tools to make informed "go/no-go" decisions on releases based on historical test results.
4) Intelligent test selection and optimization techniques can help further improve continuous delivery by running only the most
All Change how the economics of Cloud will make you think differently about JavaSteve Poole
This document discusses how the economics of cloud computing will change how Java applications are developed. Cloud providers charge for computing resources on an hourly basis (e.g. $ per GB per hour), which means applications need to use resources efficiently. Java applications generally use more memory and have longer startup times than other languages. To be cost effective in the cloud, Java applications will need to reduce their memory footprint, decrease startup times, and be designed to fail and recover gracefully. The rise of APIs and microservices also requires changes to make Java more modular and efficient in constrained environments.
Responsive, adaptive and responsible - keynote at NebraskaJSChristian Heilmann
This document discusses challenges facing web developers and proposes ways to address them in a responsible manner. It notes that web principles of maintainability, accessibility, and flexibility are often challenged by a focus on visuals over content and a belief that things should look the same everywhere. It argues that developers internalize these challenges too much by releasing things too quickly without proper crafting. The document calls on developers to be more responsible for their work by always questioning authority and avoiding blind faith in new technologies or browser innovations. It stresses the importance of focusing on users over other priorities and addressing issues through love rather than punishment.
The document outlines the agenda for Akamai's Customer Technology Day event, which includes presentations and discussions on topics like website performance, HTTP/2, cloud computing, APIs, and cybersecurity. Attendees can provide feedback, suggest future event ideas, and continue conversations online. A survey is also included to collect feedback on the Technology Day.
Capital One transitioned to DevOps by starting with a SWAT team that automated builds, deployments, and infrastructure for two applications. This improved speed and removed handoffs. Challenges included trying to automate everything at once and handoffs when automation was returned to application teams. Key lessons included focusing on automation and API's, reducing handoffs, avoiding silos, and delivering working solutions over perfection.
The document discusses concepts related to continuous delivery and deployment pipelines. It advocates building quality into software through automated testing and collaboration between developers, testers and operations teams. Continuous delivery aims to make software production-ready at any time by implementing configuration management, continuous integration, and automated testing in a deployment pipeline that provides feedback at every change. This reduces risk and enables frequent, reliable releases that are tied to business needs rather than operational constraints.
Cloud Academy Webinar: Recipe for DevOps Success: Capital One StyleMark Andersen
Capital One transitioned to a DevOps model to improve speed of delivery and reduce handoffs between teams. They started with a SWAT team that automated builds, deployments, and infrastructure for two applications. This proved successful and they expanded automation to more applications. Challenges included trying to automate everything at once and handoffs when automation was returned to application teams. Key lessons included focusing on automation, removing handoffs, training application teams on automation, and delivering working solutions incrementally rather than waiting for perfection.
DevOps requires agility. The document discusses how DevOps involves operations and development engineers working together throughout the entire service lifecycle. It provides the example of Etsy, which deployed code to production an average of 32-50 times per day. Continuous integration is presented as a way to integrate changes frequently in order to detect issues early. The key aspects of continuous integration discussed are having a CI server that rebuilds and runs tests on every commit, as well as activities like unit testing, code analysis, reporting and visualization.
The document discusses four key metrics - deployment frequency, lead time for changes, change fail rate, and time to restore services - that are useful for measuring DevOps success. It provides definitions for each metric and explains how to instrument systems to collect data on these metrics continuously in order to drive improvement. Implementing these metrics through a Four Keys infrastructure allows teams to track their performance over time, identify bottlenecks, and quantify the success of experiments.
This document discusses how to avoid killing a project through accumulating technical debt. It provides tips for project managers to identify, understand, and address technical debt issues. The document outlines 4 steps for project managers to address crappy code: 1) identify the problem, 2) identify the reason, 3) act to stop writing junk code, and 4) monitor code health going forward. It also lists signs that a project may be in trouble from too much technical debt and recommendations for what project managers can do to improve code quality and reduce debt.
SkillsMatter June 2018: Java in the 21st Century: Are You Thinking Far Enough...Steve Poole
The document appears to be a presentation discussing the future of Java and how it needs to adapt to changing computing landscapes like cloud, data analytics, and machine learning. It argues that Java must innovate faster through an open ecosystem to remain competitive. It provides examples of how Java is becoming more modular and getting faster release cycles to better support new workloads and business needs.
This document provides an overview of debugging distributed systems. It begins with definitions of distributed systems and why they are difficult to debug due to factors like concurrency, lack of a global clock, and independent failures. It then outlines a structured 8 step approach to debugging distributed systems: 1) observe and document issues, 2) create a minimal reproducer, 3) debug client side, 4) check DNS and routing, 5) check connections, 6) inspect traffic and messages, 7) debug server side, and 8) wrap up with a post mortem. The document concludes with examples of distributed systems war stories and questions.
The impact of innovation on travel and tourism industries (World Travel Marke...Brian Solis
From the impact of Pokemon Go on Silicon Valley to artificial intelligence, futurist Brian Solis talks to Mathew Parsons of World Travel Market about the future of travel, tourism and hospitality.
Reuters: Pictures of the Year 2016 (Part 2)maditabalnco
This document contains 20 photos from news events around the world between January and November 2016. The photos show international events like the US presidential election, the conflict in Ukraine, the migrant crisis in Europe, the Rio Olympics, and more. They also depict human interest stories and natural phenomena from various countries.
Using flow approaches to effectively manage agile testing at the enterprise l...Yuval Yeret
Slides from my upcoming LSSC11 talk:
More and more organizations want to become more agile these days. When the theory hits the shores of reality, few organizations can get to an idealistic agile feature team that does all testing within sprints, has no need for release-level processes, and where everything is fully automated continuous deployment style. Usually the testing organization is in the eye of the storm when talking about Big Batches, Wastes, ineffective handoffs and mountains of rework, as well as high transaction costs. I’ve recently been using Lean/Kanban flow based approaches to provide a way to evolve testing organizations to a more effective way of working, so that they can better support earlier feedback and higher flexibility. I will present this work as well as case studies from enterprise-level product development companies that are starting to use these approaches.
We will deal with the following challenges:
* Complex environments when it is not realistic to finish all required work within a sprint
* How to visualize and reduce testing batch sizes within sprints/releases using CFD
* How to deal with the testing bottleneck so common in product development organizations – practical suggestions and how to deal with the mindset issues
* How to run stabilization/hardening periods using Flow-based thinking
http://lssc11.crowdvine.com/talks/18074
Continuous Testing: Preparing for DevOpsSTePINForum
Digital transformation requires continuous testing to quickly adapt to changes and deliver value to customers. Traditional testing relies heavily on manual testing which is inefficient. Continuous testing uses test automation to test early and often through the development process. This shifts testing left and allows for more frequent testing of applications and APIs. Continuous testing leverages techniques like exploratory testing, test automation, and continuous integration to significantly increase testing efficiency and reduce risks. The goal is to close knowledge gaps through continuous and adaptive investigation.
01 why of dev ops - devopsguys - magentys - finalDevOpsGroup
This document discusses the reasons for adopting a DevOps approach and methodology. It outlines how business and technology environments have changed, putting pressure on development and operations teams. DevOps is presented as a way to help organizations react to these changes and deliver business value across the entire product lifecycle through practices like automation, collaboration, and continuous delivery. The document argues that DevOps can help organizations reduce costs and time-to-market while improving productivity.
The changing role of testing and test automation in the increasingly fast-paced world of continuous delivery and automated acceptance testing. Learn how, in a DevOps environment, testing activities start with requirements discovery and definition, playing a vital role in not only detecting defects, but preventing them, and ensuring not only that the features are built right, but the right features are built. And learn how test automation needs to happen during, not after, the sprint, and how you can achieve this.
Despite rumors to the contrary, the role of the tester is not diminished with the arrival of automated DevOps, with its ultra-rapid deployment cycles and its emphasis on automation. On the contrary, testers play a vital role in ensuring that the code that gets deployed ten times a day is worth deploying.
Continuous delivery a happier, safer alternative to release trainsThoughtworks
This document discusses principles and practices for continuous delivery including automating the build, deployment, testing and release process. It emphasizes reducing risk through techniques like feature toggles, blue-green deployments, canary releasing and implementing a production immune system. It also stresses the importance of collaboration between developers, testers and operations personnel.
The document discusses automating authorization and accreditation (A&A) processes through continuous compliance. It proposes treating compliance like test-driven development (TDD) and continuous delivery/DevOps by defining compliance requirements and controls using a common YAML schema. This would allow building automated pipelines to generate authorization artifacts like plans of action and milestones (POAMs) based on certification inputs and system details. The key is separating compliance components and logic from technical implementation details to enable unified code and compliance pipelines that can respond rapidly to security issues and deployment changes. OpenControl is presented as an open source project implementing this approach using common compliance standards, automation tools like Concourse, and a community for collaboration.
his talk will present the core concepts of Exponential Business Agility, or XBA. XBA is a set of patterns for organising value streams around self-organising, autonomous teams, and is part of the XSCALE approach to scaling agile. XBA combines the Spotify model with practice patterns drawn from the Iroquois Confederacy, the most successful and longest-lived holarchy in history.
Learn how Throughput Accounting optimises the contribution of each business function to top line throughput rather than blindly attempting to minimise operating expense.
And discover how Self-Propagating Transformation avoids pushing change into pre-existing teams, programs or silos, but generates agile capability by grafting the kernel of a new culture onto the trunk of the old.
Be a pod of dolphins, not a dancing elephant. Don’t try to scale agile. De-scale your organisation instead.
Moving to Continuous Delivery Without Breaking Your CodeXebiaLabs
This document summarizes Andrew Phillips' presentation on moving to continuous delivery without breaking code. The key points are:
1) Continuous delivery requires both fast execution of code deployments through automated pipelines as well as thorough testing and analysis to ensure high quality and avoid breaking code.
2) Testing practices need to change to keep up with continuous delivery by focusing on automation, functional coverage over technical coverage, and metrics on test quality.
3) A central hub is needed to aggregate testing data from across pipelines and tools to make informed "go/no-go" decisions on releases based on historical test results.
4) Intelligent test selection and optimization techniques can help further improve continuous delivery by running only the most
All Change how the economics of Cloud will make you think differently about JavaSteve Poole
This document discusses how the economics of cloud computing will change how Java applications are developed. Cloud providers charge for computing resources on an hourly basis (e.g. $ per GB per hour), which means applications need to use resources efficiently. Java applications generally use more memory and have longer startup times than other languages. To be cost effective in the cloud, Java applications will need to reduce their memory footprint, decrease startup times, and be designed to fail and recover gracefully. The rise of APIs and microservices also requires changes to make Java more modular and efficient in constrained environments.
Responsive, adaptive and responsible - keynote at NebraskaJSChristian Heilmann
This document discusses challenges facing web developers and proposes ways to address them in a responsible manner. It notes that web principles of maintainability, accessibility, and flexibility are often challenged by a focus on visuals over content and a belief that things should look the same everywhere. It argues that developers internalize these challenges too much by releasing things too quickly without proper crafting. The document calls on developers to be more responsible for their work by always questioning authority and avoiding blind faith in new technologies or browser innovations. It stresses the importance of focusing on users over other priorities and addressing issues through love rather than punishment.
The document outlines the agenda for Akamai's Customer Technology Day event, which includes presentations and discussions on topics like website performance, HTTP/2, cloud computing, APIs, and cybersecurity. Attendees can provide feedback, suggest future event ideas, and continue conversations online. A survey is also included to collect feedback on the Technology Day.
Capital One transitioned to DevOps by starting with a SWAT team that automated builds, deployments, and infrastructure for two applications. This improved speed and removed handoffs. Challenges included trying to automate everything at once and handoffs when automation was returned to application teams. Key lessons included focusing on automation and API's, reducing handoffs, avoiding silos, and delivering working solutions over perfection.
The document discusses concepts related to continuous delivery and deployment pipelines. It advocates building quality into software through automated testing and collaboration between developers, testers and operations teams. Continuous delivery aims to make software production-ready at any time by implementing configuration management, continuous integration, and automated testing in a deployment pipeline that provides feedback at every change. This reduces risk and enables frequent, reliable releases that are tied to business needs rather than operational constraints.
Cloud Academy Webinar: Recipe for DevOps Success: Capital One StyleMark Andersen
Capital One transitioned to a DevOps model to improve speed of delivery and reduce handoffs between teams. They started with a SWAT team that automated builds, deployments, and infrastructure for two applications. This proved successful and they expanded automation to more applications. Challenges included trying to automate everything at once and handoffs when automation was returned to application teams. Key lessons included focusing on automation, removing handoffs, training application teams on automation, and delivering working solutions incrementally rather than waiting for perfection.
DevOps requires agility. The document discusses how DevOps involves operations and development engineers working together throughout the entire service lifecycle. It provides the example of Etsy, which deployed code to production an average of 32-50 times per day. Continuous integration is presented as a way to integrate changes frequently in order to detect issues early. The key aspects of continuous integration discussed are having a CI server that rebuilds and runs tests on every commit, as well as activities like unit testing, code analysis, reporting and visualization.
The document discusses four key metrics - deployment frequency, lead time for changes, change fail rate, and time to restore services - that are useful for measuring DevOps success. It provides definitions for each metric and explains how to instrument systems to collect data on these metrics continuously in order to drive improvement. Implementing these metrics through a Four Keys infrastructure allows teams to track their performance over time, identify bottlenecks, and quantify the success of experiments.
This document discusses how to avoid killing a project through accumulating technical debt. It provides tips for project managers to identify, understand, and address technical debt issues. The document outlines 4 steps for project managers to address crappy code: 1) identify the problem, 2) identify the reason, 3) act to stop writing junk code, and 4) monitor code health going forward. It also lists signs that a project may be in trouble from too much technical debt and recommendations for what project managers can do to improve code quality and reduce debt.
SkillsMatter June 2018: Java in the 21st Century: Are You Thinking Far Enough...Steve Poole
The document appears to be a presentation discussing the future of Java and how it needs to adapt to changing computing landscapes like cloud, data analytics, and machine learning. It argues that Java must innovate faster through an open ecosystem to remain competitive. It provides examples of how Java is becoming more modular and getting faster release cycles to better support new workloads and business needs.
This document provides an overview of debugging distributed systems. It begins with definitions of distributed systems and why they are difficult to debug due to factors like concurrency, lack of a global clock, and independent failures. It then outlines a structured 8 step approach to debugging distributed systems: 1) observe and document issues, 2) create a minimal reproducer, 3) debug client side, 4) check DNS and routing, 5) check connections, 6) inspect traffic and messages, 7) debug server side, and 8) wrap up with a post mortem. The document concludes with examples of distributed systems war stories and questions.
The impact of innovation on travel and tourism industries (World Travel Marke...Brian Solis
From the impact of Pokemon Go on Silicon Valley to artificial intelligence, futurist Brian Solis talks to Mathew Parsons of World Travel Market about the future of travel, tourism and hospitality.
Reuters: Pictures of the Year 2016 (Part 2)maditabalnco
This document contains 20 photos from news events around the world between January and November 2016. The photos show international events like the US presidential election, the conflict in Ukraine, the migrant crisis in Europe, the Rio Olympics, and more. They also depict human interest stories and natural phenomena from various countries.
Lightning Talk #9: How UX and Data Storytelling Can Shape Policy by Mika Aldabaux singapore
How can we take UX and Data Storytelling out of the tech context and use them to change the way government behaves?
Showcasing the truth is the highest goal of data storytelling. Because the design of a chart can affect the interpretation of data in a major way, one must wield visual tools with care and deliberation. Using quantitative facts to evoke an emotional response is best achieved with the combination of UX and data storytelling.
The document discusses how personalization and dynamic content are becoming increasingly important on websites. It notes that 52% of marketers see content personalization as critical and 75% of consumers like it when brands personalize their content. However, personalization can create issues for search engine optimization as dynamic URLs and content are more difficult for search engines to index than static pages. The document provides tips for SEOs to help address these personalization and SEO challenges, such as using static URLs when possible and submitting accurate sitemaps.
This document summarizes a study of CEO succession events among the largest 100 U.S. corporations between 2005-2015. The study analyzed executives who were passed over for the CEO role ("succession losers") and their subsequent careers. It found that 74% of passed over executives left their companies, with 30% eventually becoming CEOs elsewhere. However, companies led by succession losers saw average stock price declines of 13% over 3 years, compared to gains for companies whose CEO selections remained unchanged. The findings suggest that boards generally identify the most qualified CEO candidates, though differences between internal and external hires complicate comparisons.
We’re all trying to find that idea or spark that will turn a good project into a great project. Creativity plays a huge role in the outcome of our work. Harnessing the power of collaboration and open source, we can make great strides towards excellence. Not just for designers, this talk can be applicable to many different roles – even development. In this talk, Seasoned Creative Director Sara Cannon is going to share some secrets about creative methodology, collaboration, and the strong role that open source can play in our work.
The Six Highest Performing B2B Blog Post FormatsBarry Feldman
If your B2B blogging goals include earning social media shares and backlinks to boost your search rankings, this infographic lists the size best approaches.
1) The document discusses the opportunity for technology to improve organizational efficiency and transition economies into a "smart and clean world."
2) It argues that aggregate efficiency has stalled at around 22% for 30 years due to limitations of the Second Industrial Revolution, but that digitizing transport, energy, and communication through technologies like blockchain can help manage resources and increase efficiency.
3) Technologies like precision agriculture, cloud computing, robotics, and autonomous vehicles may allow for "dematerialization" and do more with fewer physical resources through effects like reduced waste and need for transportation/logistics infrastructure.
Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling change, reporting the system’s configuration, and auditing—won’t do the trick anymore. Bob Aiello presents an in-depth tour of a more robust and powerful approach to CM consisting of six key functions: source code management, build engineering, environment management, change management and control, release management, and deployment. Bob describes current and emerging CM trends—support for agile development, cloud computing, and mobile apps development—and reviews the industry standards and frameworks essential in CM today. Take back an integrated approach to establish proper IT governance and compliance using the latest CM practices while offering development teams the most effective CM practices available today.
Robust configuration management (CM) practices are essential for creating continuous builds to support agile’s integration and testing demands, and for rapidly packaging, releasing, and deploying applications into production. Classic CM—identifying system components, controlling changes, reporting the system’s configuration, and auditing—won’t do the trick anymore. Bob Aiello presents an in-depth tour of a more robust and powerful approach to CM consisting of six key functions: source code management, build engineering, environment management, change management and control, release management, and deployment. Bob describes current and emerging CM trends—support for agile development, cloud computing, and mobile apps development—and reviews the industry standards and frameworks essential in CM today. Take back an integrated approach to establish proper IT governance and compliance using the latest CM practices while offering development teams the most effective CM practices available today.
Implementing DevOps AutomationBest Practices and Common MistakesDerek Ashmore
Derek C. Ashmore gave a presentation on implementing DevOps automation best practices and common mistakes. He discussed establishing DevOps discipline through practices like source code management, infrastructure as code testing, and feature branching. Ashmore also covered DevOps management approaches like automating approvals and guardrails instead of manual reviews. He warned against mistakes such as a lack of testing for common infrastructure code and creating an overly large blast radius for changes.
The document is a presentation by Mike Kavis on deriving value from enterprise DevOps. It discusses how DevOps aims to build better quality software faster and more reliably through collaboration between development and operations teams. It outlines some common misperceptions of DevOps and explains that the most fundamental goal is to remove waste from processes like redundant work and wait times. The presentation also examines what is driving DevOps from both a business perspective of faster deployments and fewer failures, and a technology perspective of new cloud-based architectures requiring more automation and collaboration across teams. It argues that DevOps needs a culture shift toward continuous improvement and removing waste from systems through automation.
Writing microservices in Java -- Chicago-2015-11-10Derek Ashmore
This document summarizes a presentation on writing microservices in Java. It discusses:
- What microservices are and common traits like single functional purpose and standard interfaces
- Reasons for using microservices like no lock-in, easier management, and higher throughput
- Design considerations like service boundaries, handling failures, data integrity, and performance
- Common patterns for designing microservices around failures, transactions, and performance
- Cross-cutting concerns like deployment, security, and contract testing
- When microservices are appropriate to use
The presentation provides examples and references additional resources on GitHub for sample code.
Don’t Go over the Waterfall: Keep Agile Testing AgileTechWell
All too often an agile iteration resembles a mini-waterfall cycle with developers coding for the duration of the iteration and then throwing code “over the wall” to the test team. This results in the all-too-familiar “test squeeze” with testers often testing code after the iteration has already finished. When testing occurs after an iteration’s end, the agile principle of potentially releasable is violated and negatively impacts the next iteration. To avoid these problems we must ensure that all testing is completed before the end of the iteration. But how can we achieve this? Aaron Barrett explains that the solution lies in the planning and processes that govern the agile team. Learn proven strategies that allow your test teams to move testing back inside the iteration and take back a plan to keep you from going over the waterfall.
Writing microservices in java java one-2015-10-28Derek Ashmore
Derek C. Ashmore gave a presentation on writing microservices in Java. He began by defining microservices as having a single functional purpose and being loosely coupled. He discussed design considerations like service boundaries, handling service failures, and performance. Common patterns for microservices like circuit breakers, caching, and messaging queues were also covered. Ashmore concluded with a discussion of cross-cutting concerns, common mistakes, and when microservices are appropriate to use.
Microservices for java architects coders-conf-2015-05-15Derek Ashmore
Derek C. Ashmore gave a presentation on microservices for Java architects. He began by introducing himself and his background. He then discussed what microservices are, how they differ from traditional monolithic architectures, and some of the benefits of refactoring into microservices. The remainder of the presentation covered design considerations and patterns for microservices, such as service boundaries, failure handling, performance, and data integrity. It also discussed packaging and deployment options like Spring Boot and Docker. Ashmore concluded by noting some limitations of microservices and providing further resources.
Cloud Migration for Financial Services - Toronto - October 2016Amazon Web Services
Presented by Cloud Technology Partners. Robert Christiansen presents us best practices for cloud adoption, taking us on the journey from a single application on the cloud, through hybrid cloud, culminating with a Cloud First Approach.
The document is a presentation about infrastructure automation for the cloud. It discusses how infrastructure is changing with the rise of cloud computing and how this necessitates new approaches like treating infrastructure as code. It advocates for techniques like configuration management, version controlling all components, building from source code, enabling one step deployments, continuous monitoring, and integrating development and operations teams through a DevOps culture and shared processes. The overall goal is to enable agile infrastructure that allows for business agility and a faster time to market.
Distributed/Dual-Shore Agile Software Development – Is It Effective?Synerzip
This webinar covers the best practices for making dual-shore Agile work effectively.
Topics that are covered -
Business case for Dual-Shore development
• Business case for Agile
• Can Dual-Shore and Agile be combined effectively?
• Challenges
• Best Practices
• Synerzip Introduction
Stay tuned for Synerzip's upcoming webinars that you may be interested in https://www.synerzip.com/webinars/
The Survey Says: Testers Spend Their Time Doing...TechWell
How can testers contribute more to the success of their project and their company? How can they focus on asking the right questions, improving test planning and design, and finding defects so the business releases a quality product―even though there’s always one more fire to extinguish or one more request to fulfill? There aren’t enough hours in the day to do it all. Join Al Wagner as he reveals recent survey results showing where testers actually spend their time and where testers think their time would be better spent. Compare your own experience with what 250 test professionals from around the world reported. You may be surprised how prevalent testing challenges really are. Learn what techniques and technologies are available to help today’s test professionals execute what they were actually hired to do—test software. Return to your organization with an increased understanding of how other testers are dealing with their testing bottlenecks and what activities your peers view as the best use of their valuable time.
This document appears to be a presentation on achieving ITSM success when implementing the BMC Remedy ITSM Suite. It includes an agenda, introductions of panel experts, an outline of key areas for success including financial planning, infrastructure, communication, and industry standards. The presentation provides guidance and best practices around each area to help attendees successfully implement or upgrade their ITSM environment for maximum success.
Geting cloud architecture right the first time linthicum interop fall 2013David Linthicum
The document discusses best practices for cloud architecture. It notes that many current cloud systems lack proper architecture and do not meet expectations due to issues like inefficient resource utilization, outages, lack of security and tenant management. Common mistakes made are not understanding how to scale architectures, deal with tenants, implement proper security, or use services correctly. The document provides guidance on developing a solid cloud architecture, including determining business needs, designing with services in mind, creating security and governance plans, and migrating only components that provide value to the cloud. It emphasizes focusing on core services like data, transactions and utilities, and building for tenants rather than individual users.
This document provides an overview of auditing and being audited. It discusses the different types of audits including internal, supplier, and third party audits. It describes the typical phases of an audit including planning, execution, reporting, and closeout. It provides definitions for key audit terms and outlines the objective of audits as collecting objective evidence to make an informed judgment. The document is intended to help readers understand auditing programs and techniques.
Microservices for architects los angeles-2016-07-16Derek Ashmore
Derek C. Ashmore gave a presentation on microservices where he discussed: the definition and benefits of microservices; design considerations like service boundaries, failure handling patterns, and addressing cross-cutting concerns; when microservices make sense to use; and common mistakes to avoid like inappropriate service boundaries. The presentation provided examples of code and further resources on microservices.
Microservices for Java Architects (Indianapolis, April 15, 2015)Derek Ashmore
Slide deck for presentation given to the Indianapolis Java Users Group on April 15, 2015.
For some reason, Slideshare doesn't like the hyper-links in the presentation. Here's a PDF version for which the hyper-links work: https://drive.google.com/file/d/0BywOAPVO4FvATEZ5V052a2lrZEk/view?usp=sharing
Due to its ease of use and distributed repository infrastructure, Git is quickly becoming the version control system of choice for many. Getting started takes only a few minutes, and available online tutorials explain Git basics and more advanced features including branching. As easy as Git is to implement, many developers find Git challenging to scale for large enterprises. Some go to Cloud-based Git service providers; others implement tools such as Stash and gitflow for effective branching patterns and variant management. Integrating Git with other tools including workflow automation, continuous integration, and continuous delivery all come with their own challenges. Bob Aiello “gits” you started with understanding how to implement and maintain a flexible and scalable Git infrastructure that can support your agile development efforts including continuous delivery and DevOps. Git is a great tool, and scaling Git for the enterprise is very doable—if you implement the right tools and processes.
The document discusses the transformation of a program to an agile methodology. It begins with an introduction to agile, discussing why it was adopted and how it differs from traditional software development lifecycles. It then outlines the initial problematic state of the program and how agile principles could help address issues like product quality, team dynamics, and outdated architecture. The document goes on to describe the agile journey, significant phases of progress, and how practices like frequent delivery, customer collaboration, and team empowerment were implemented. It contrasts agile and waterfall methodologies and principles.
Lifestyles of the rich and frameworklessEqual Experts
The document discusses frameworks versus building applications from scratch. It argues that frameworks are useful for speed of development, ease of hiring, and bootstrapping minimum viable products. However, building applications from scratch allows for specific needs, fine-grained control, and knowledge gaining. The rest of the document involves live coding demonstrations of routing, data binding, and templating without using frameworks to gain a better understanding of how they work under the hood.
Similar to Continuous Delivery: Rapid and Reliable Releases with DevOps Practices (20)
Isabel Evans stopped drawing and painting after being told she was not very good at it, which led to a loss of confidence in her creative and professional abilities. However, she realized that attempting creative activities is important for cognitive and emotional development, and that making mistakes and learning from failures allows for growth. By reengaging with failure through art and with support from others, Isabel was able to regain confidence in her abilities and reboot her career. The document discusses different perspectives on failure and the importance of learning from mistakes.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
This document summarizes a half-day tutorial on test design for fully automated build architectures presented by Melissa Benua of mParticle at STAREAST 2018. The tutorial covered guiding principles for test design including prioritizing important and reliable tests, structuring automated pipelines around components, packages, and releases, and monitoring test results through code coverage, flaky test handling, and logging versus counters. It also included exercises mapping test cases to functional boundaries and categories of tests to pipeline stages.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
The document summarizes a presentation about including databases in a continuous integration/delivery process. It discusses treating database code like application code by placing it under version control and integrating databases into the DevOps software development pipeline. This allows databases to be built, tested, and released like other software through continuous integration, delivery, and deployment.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfChart Kalyan
A Mix Chart displays historical data of numbers in a graphical or tabular form. The Kalyan Rajdhani Mix Chart specifically shows the results of a sequence of numbers over different periods.
[OReilly Superstream] Occupy the Space: A grassroots guide to engineering (an...Jason Yip
The typical problem in product engineering is not bad strategy, so much as “no strategy”. This leads to confusion, lack of motivation, and incoherent action. The next time you look for a strategy and find an empty space, instead of waiting for it to be filled, I will show you how to fill it in yourself. If you’re wrong, it forces a correction. If you’re right, it helps create focus. I’ll share how I’ve approached this in the past, both what works and lessons for what didn’t work so well.
"Frontline Battles with DDoS: Best practices and Lessons Learned", Igor IvaniukFwdays
At this talk we will discuss DDoS protection tools and best practices, discuss network architectures and what AWS has to offer. Also, we will look into one of the largest DDoS attacks on Ukrainian infrastructure that happened in February 2022. We'll see, what techniques helped to keep the web resources available for Ukrainians and how AWS improved DDoS protection for all customers based on Ukraine experience
"Choosing proper type of scaling", Olena SyrotaFwdays
Imagine an IoT processing system that is already quite mature and production-ready and for which client coverage is growing and scaling and performance aspects are life and death questions. The system has Redis, MongoDB, and stream processing based on ksqldb. In this talk, firstly, we will analyze scaling approaches and then select the proper ones for our system.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
Driving Business Innovation: Latest Generative AI Advancements & Success StorySafe Software
Are you ready to revolutionize how you handle data? Join us for a webinar where we’ll bring you up to speed with the latest advancements in Generative AI technology and discover how leveraging FME with tools from giants like Google Gemini, Amazon, and Microsoft OpenAI can supercharge your workflow efficiency.
During the hour, we’ll take you through:
Guest Speaker Segment with Hannah Barrington: Dive into the world of dynamic real estate marketing with Hannah, the Marketing Manager at Workspace Group. Hear firsthand how their team generates engaging descriptions for thousands of office units by integrating diverse data sources—from PDF floorplans to web pages—using FME transformers, like OpenAIVisionConnector and AnthropicVisionConnector. This use case will show you how GenAI can streamline content creation for marketing across the board.
Ollama Use Case: Learn how Scenario Specialist Dmitri Bagh has utilized Ollama within FME to input data, create custom models, and enhance security protocols. This segment will include demos to illustrate the full capabilities of FME in AI-driven processes.
Custom AI Models: Discover how to leverage FME to build personalized AI models using your data. Whether it’s populating a model with local data for added security or integrating public AI tools, find out how FME facilitates a versatile and secure approach to AI.
We’ll wrap up with a live Q&A session where you can engage with our experts on your specific use cases, and learn more about optimizing your data workflows with AI.
This webinar is ideal for professionals seeking to harness the power of AI within their data management systems while ensuring high levels of customization and security. Whether you're a novice or an expert, gain actionable insights and strategies to elevate your data processes. Join us to see how FME and AI can revolutionize how you work with data!
5th LF Energy Power Grid Model Meet-up SlidesDanBrown980551
5th Power Grid Model Meet-up
It is with great pleasure that we extend to you an invitation to the 5th Power Grid Model Meet-up, scheduled for 6th June 2024. This event will adopt a hybrid format, allowing participants to join us either through an online Mircosoft Teams session or in person at TU/e located at Den Dolech 2, Eindhoven, Netherlands. The meet-up will be hosted by Eindhoven University of Technology (TU/e), a research university specializing in engineering science & technology.
Power Grid Model
The global energy transition is placing new and unprecedented demands on Distribution System Operators (DSOs). Alongside upgrades to grid capacity, processes such as digitization, capacity optimization, and congestion management are becoming vital for delivering reliable services.
Power Grid Model is an open source project from Linux Foundation Energy and provides a calculation engine that is increasingly essential for DSOs. It offers a standards-based foundation enabling real-time power systems analysis, simulations of electrical power grids, and sophisticated what-if analysis. In addition, it enables in-depth studies and analysis of the electrical power grid’s behavior and performance. This comprehensive model incorporates essential factors such as power generation capacity, electrical losses, voltage levels, power flows, and system stability.
Power Grid Model is currently being applied in a wide variety of use cases, including grid planning, expansion, reliability, and congestion studies. It can also help in analyzing the impact of renewable energy integration, assessing the effects of disturbances or faults, and developing strategies for grid control and optimization.
What to expect
For the upcoming meetup we are organizing, we have an exciting lineup of activities planned:
-Insightful presentations covering two practical applications of the Power Grid Model.
-An update on the latest advancements in Power Grid -Model technology during the first and second quarters of 2024.
-An interactive brainstorming session to discuss and propose new feature requests.
-An opportunity to connect with fellow Power Grid Model enthusiasts and users.
What is an RPA CoE? Session 1 – CoE VisionDianaGray10
In the first session, we will review the organization's vision and how this has an impact on the COE Structure.
Topics covered:
• The role of a steering committee
• How do the organization’s priorities determine CoE Structure?
Speaker:
Chris Bolin, Senior Intelligent Automation Architect Anika Systems
Northern Engraving | Nameplate Manufacturing Process - 2024Northern Engraving
Manufacturing custom quality metal nameplates and badges involves several standard operations. Processes include sheet prep, lithography, screening, coating, punch press and inspection. All decoration is completed in the flat sheet with adhesive and tooling operations following. The possibilities for creating unique durable nameplates are endless. How will you create your brand identity? We can help!
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.