DevOps aims to break down silos between development and operations teams through culture, automation, measurement and sharing. It promotes a self-service approach where developers have autonomy over the infrastructure needed to develop, test and deploy applications. This allows for faster delivery of features and fixes through practices like infrastructure as code and continuous integration and deployment. Some benefits include improved repeatability, automation, scalability and agility.
The document describes WiredReach's process for implementing continuous deployment. It discusses how they moved from bi-weekly release cycles with large releases to releasing multiple times per day with releases containing under 25 lines of code. This was done by setting up automated testing and deployment pipelines. It also touches on some of the challenges they faced in taking this approach and strategies for incrementally building systems to support continuous deployment like adding production monitoring and building a "cluster immune system".
Jesse Robbins gave a presentation on DevOps culture at CloudExpoEurope. He discussed how successful tech companies like Google, Amazon, and Microsoft built their own automation and deployment tools to support DevOps practices internally before these became common. Robbins outlined three fundamental attributes of successful DevOps cultures: 1) treating infrastructure as code, 2) designing applications as services, and 3) integrating development, operations, and other teams. He also provided examples of how to start changing culture in large organizations by starting small, creating champions, using metrics, celebrating successes, and taking advantage of compelling events.
The document discusses best practices for continuous integration, continuous delivery, and automation in software development. It recommends automating the entire development cycle from build to test to deployment. Changes should be deployed frequently, such as multiple times a day, to catch errors early. All code, configurations, and dependencies should be stored in version control. A deployment pipeline approach is advocated with separate stages for testing, verification, and release to different environments. Rollback and recovery should be planned and tested.
This document discusses the Maven project development tool. It introduces Maven's core concepts including the project object model (POM) which defines project metadata, the build lifecycle of phases and goals, plugins for custom tasks, and dependency management. The document explains how Maven aims to standardize project structure and make builds easy to understand and reproduce.
MeasureWorks - Velocity Conference Europe 2012 - a Web Performance dashboard ...MeasureWorks
For the Velocity Conference Europe 2012 workshop day this presentation is about the essentials for creation and building a Web Performance dashboard. This with ultimate goal of providing the audience a framework for designing and building a web performance dashboard. The session will cover the following 3 items:
Design guidelines: What defines a web performance dashboard? How to make sure it’s actionable and for people to actually use it on day to day basis?
Data collection: Why performance data? The various ways there are to collect data (e.g. synthetic versus RUM data, Webpagetest, Mobile) and how to correlate the different types of data and tools
Building the dashboard: How to build the actual dashboard, providing an overview of the tools/techniques used
At the end of the workshop you will be able to design and build your own dashboard based on the framework provided, or to optimize the current dashboards within your organization.
DevOps aims to break down silos between development and operations teams through culture, automation, measurement and sharing. It promotes a self-service approach where developers have autonomy over the infrastructure needed to develop, test and deploy applications. This allows for faster delivery of features and fixes through practices like infrastructure as code and continuous integration and deployment. Some benefits include improved repeatability, automation, scalability and agility.
The document describes WiredReach's process for implementing continuous deployment. It discusses how they moved from bi-weekly release cycles with large releases to releasing multiple times per day with releases containing under 25 lines of code. This was done by setting up automated testing and deployment pipelines. It also touches on some of the challenges they faced in taking this approach and strategies for incrementally building systems to support continuous deployment like adding production monitoring and building a "cluster immune system".
Jesse Robbins gave a presentation on DevOps culture at CloudExpoEurope. He discussed how successful tech companies like Google, Amazon, and Microsoft built their own automation and deployment tools to support DevOps practices internally before these became common. Robbins outlined three fundamental attributes of successful DevOps cultures: 1) treating infrastructure as code, 2) designing applications as services, and 3) integrating development, operations, and other teams. He also provided examples of how to start changing culture in large organizations by starting small, creating champions, using metrics, celebrating successes, and taking advantage of compelling events.
The document discusses best practices for continuous integration, continuous delivery, and automation in software development. It recommends automating the entire development cycle from build to test to deployment. Changes should be deployed frequently, such as multiple times a day, to catch errors early. All code, configurations, and dependencies should be stored in version control. A deployment pipeline approach is advocated with separate stages for testing, verification, and release to different environments. Rollback and recovery should be planned and tested.
This document discusses the Maven project development tool. It introduces Maven's core concepts including the project object model (POM) which defines project metadata, the build lifecycle of phases and goals, plugins for custom tasks, and dependency management. The document explains how Maven aims to standardize project structure and make builds easy to understand and reproduce.
MeasureWorks - Velocity Conference Europe 2012 - a Web Performance dashboard ...MeasureWorks
For the Velocity Conference Europe 2012 workshop day this presentation is about the essentials for creation and building a Web Performance dashboard. This with ultimate goal of providing the audience a framework for designing and building a web performance dashboard. The session will cover the following 3 items:
Design guidelines: What defines a web performance dashboard? How to make sure it’s actionable and for people to actually use it on day to day basis?
Data collection: Why performance data? The various ways there are to collect data (e.g. synthetic versus RUM data, Webpagetest, Mobile) and how to correlate the different types of data and tools
Building the dashboard: How to build the actual dashboard, providing an overview of the tools/techniques used
At the end of the workshop you will be able to design and build your own dashboard based on the framework provided, or to optimize the current dashboards within your organization.
Dev ops tutorial for beginners what is devops & devops toolsJanBask Training
DevOps Tools Are Used To Offer Improved Performance. You can explore more about above-listed DevOps tools (Puppet, Chef, Sensu, Nagios, Bamboo, Eclipse, Git, Saltstack, Jenkins ) that are used to provide improved performance by DevOps team. DevOps tools are used to improve the developer's efficiency.
Short Introduction of software engineering for bioinformatics 丈 宮本
This document provides an overview of different software engineering approaches for bioinformatics projects, including Waterfall, Agile, DevOps, eXtreme Programming, and tools like Git, GitHub, Jenkins, Docker, and Fabric. Waterfall is not well-suited for bioinformatics due to lack of flexibility, while Agile and DevOps methodologies allow for iterative development and integration of code changes. eXtreme Programming focuses on code maintainability through practices like test-driven development and continuous integration. Version control with Git/GitHub and configuration tools like Docker and Fabric can help manage reproducibility and infrastructure as code.
Take advantage of new trends in agile: Iterationless Kanban and Continuous De...Atlassian
The document discusses how Dachis Group has successfully integrated Lean Startup and Lean Development methodologies. There were three key areas of focus: building the product backlog by modeling features, epics, and stories in JIRA; structuring the Kanban flow using tools like GreenHopper and custom plugins; and implementing continuous deployment using tools like Chef, Jenkins, and custom code for automated deployments. The presentation provides examples of how Dachis Group implemented these practices for their large-scale, globally distributed teams. It recommends background reading on Lean Startup, Customer Development, Kanban, and Continuous Delivery and offers contact details for further discussion.
Yahoo adopted Scrum in 2004 with one experimental team and gradually expanded to over 200 Scrum teams by 2008 with over 1500 employees. Key results included an average team velocity increase of 35% per year, development cost reductions of over $1 million per year, and a 100% return on investment in trainings in the first year. While 15-20% of employees did not like Scrum initially, Yahoo saw faster time to market, higher quality, and satisfied customers compared to waterfall.
This presentation provides a clear path for your agile project by using a handful of simple steps. Don’t expect an ambiguous restatement of the Agile Manifesto. You will learn specific steps that will challenge your team and delight your customers.
This document summarizes and compares several popular DevOps tools used for tasks like version control, configuration management, continuous integration/delivery, monitoring, and testing. Key tools mentioned include Git, GitHub, Ansible, Jenkins, Chef, Puppet, Statuspage, ServiceNow, Docker, Kubernetes, Prometheus, Splunk, Datadog, Selenium, and JFrog Artifactory. Each tool is briefly described in terms of its main functionality and role in a DevOps workflow.
1) DevOps aims to automate and integrate processes between software development and IT teams to increase efficiency. It emphasizes cross-team communication and technology automation.
2) When adopting Salesforce DevOps, organizations face challenges around lack of best practices, admin-friendliness of tools, complexity of Salesforce environments, and finding expertise.
3) There are two main approaches to Salesforce DevOps - building out a solution using Salesforce tools like DX and scripting, or buying an ISV solution. Building provides more flexibility while buying provides pre-built features and support.
Storage, network and computational resources are becoming API driven. Configuration management tools provide another level of automation and semantics to the systems. As these tools evolve the exercise of building systems looks more and more like software development. Further, when developing web applications, the application is the infrastructure. If the servers are down, there is no application. The value of the application is tied to the systems. Treating the systems and application holistically, encouraging communication and collaboration between dev and ops is the path to true artisanal retro-futurism ⊗ team-scale anarcho-syndicalism.
This document discusses best practices for PHP application delivery and outlines challenges such as missed release dates due to lack of coordination between dev and ops teams. It presents Zend Server as a solution to improve collaboration through automated deployments and visibility. Zend Server helps meet performance expectations through application monitoring and infrastructure scaling. It also helps maintain quality with shorter cycles through code reuse, tools and training. Zend Server ensures app SLAs are met by managing changes across servers as one and proactively identifying performance issues.
Systems Management Forum 2013 (http://ac.nikkeibp.co.jp/nc/smf2013s/) の基調講演資料です。楽天では2012年4月から社内でPaaSを展開しており、その基盤の上でさまざまなサービスが開発、運用されています。講演では、楽天PaaSでのDevOpsの実践方法について具体的に紹介しました。
Google在2013開始導入Gradle工具作為新的Android build system,Gradle的使用正是實踐DevOps的良好利器,除了方便進行automated building外, Gradle更幫助我們消弭不同開發環境/工具間的差異問題,如同infarsture as code之於web application/service的重要性,build script as code就是幫助Android App快速發佈版本並維持品質穩定的關鍵最後一哩路。
此次主題將探討如何利用gradle進行精實良好的系統開發配置管理,建立一條下達開發者本地端上通產品發佈系統的透明化產品開發流水線。你是否常常一個App剛發佈不久,下一個idea已經生成,舊程式需要繼續維護同時又要添加新功能,你的開發方法是否能讓多方產品流水線順暢運行而且並行不悖?妥善利用Gradle並深入理解Build by convention的內涵是最好的選擇。
Unleashing the Power of Automated Refactoring with JDTNaresh Jain
Refactoring is a series of small steps, each of which changes the program’s internal structure without changing its external behaviour. Refactoring, as a tool, to automate behaviour-preserving transformations to source code are not only very popular in agile development environments, but have been widely established as a cornerstone of the daily software development process, regardless of the methodology being used. Most major development environments such as Eclipse offer a set of powerful refactoring to substantially increase development productivity.
In this live demo, I’ll show
* the real value of refactoring,
* how we practice it safely,
* when and why we refactor,
* the power of refactoring tools and
* when we avoid refactoring.
I’ll be using two real-world examples of refactoring and sharing what I’ve learned about this important practice of the last 15 years.
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014Jwooldridge
Thanks to Liam and the crew from Magentys for arranging a fantastic evening of presentations on all things DevOps.
Attached is my presentation from the event on Enterprise Devops.
For those of you who missed it:
“Join the crowd of 100 industry leaders across the Retail, Finance and Digital sectors for an exciting evening of talks in London’s Tech City on DevOps. Enjoy networking with a chilled beer alongside the experts who are making DevOps work and those who want to make it work.
Whether you’re a corporate or start-up, DevOps should be a hot topic so listen to how the experts are achieving great things, hear their views on the trends and discuss the future of DevOps.”
Jonny
enterprisedevops.com
Litmus is a tool for chaos engineering on Kubernetes. Version 2.0 introduces new features like multi-cloud control planes, team management, workflows to sequence experiments, probes to define application steady states, support for SLOs and GitOps, and improved observability and API support. The roadmap for 2021 includes strengthening control and execution, adding more experiments and probes, and integrating with more CNCF projects.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
The document discusses building a DevOps culture. It promotes having one team with one goal, pairing developers and operations staff, and sharing on-call responsibilities. It also recommends operations teams adopt agile practices like Kanban, daily standups, and retrospectives to become more aligned with development teams. The goal is to break down silos and have both teams work together seamlessly to deliver results faster.
This document summarizes scenes from implementing Scrum at a broadcasting company with offices in Berlin and Brasov. It discusses cultural differences between the German and Romanian teams that created challenges. It also outlines the company's products, organizational structure before and after adopting Scrum, and lessons learned around scaling Scrum, removing impediments, training, and allowing teams autonomy.
A very big thank you to Michael Palotas from Grid Fusion & eBay International for taking the time and effort to travel across the globe to present at the Australian Test Managers Forum 2014. If you would like any information on TMF please email tmf@kjross.com.au
Karthik Gaekwad is a member of the cloud team at National Instruments who owns the Canopy user management and licensing platform. He discusses National Instrument's approach to cloud development which includes short monthly iterations to incrementally develop and deploy new features. Key aspects of their approach include modeling the end-to-end system, designing features to be reusable across platforms, extensive testing and monitoring, and getting early user feedback through demos.
Quick Reference Poster based on the DevOps @ Microsoft transformation story (https://aka.ms/devops), focused on the five habits: Customer Focus, Production First Mindset, Team Autonomy + Enterprise Alignment, Shift Left Quality, and Infrastructure as a Flexible Resource.
We recommend you use the following to print the poster:
- Paper: (1) Satin 160 gsm (Standard) (White) - All Pages
- Page Size: Custom (16.5417 x23.3889)
- Final Size: Print on 16.54 x 23.39
Dev ops tutorial for beginners what is devops & devops toolsJanBask Training
DevOps Tools Are Used To Offer Improved Performance. You can explore more about above-listed DevOps tools (Puppet, Chef, Sensu, Nagios, Bamboo, Eclipse, Git, Saltstack, Jenkins ) that are used to provide improved performance by DevOps team. DevOps tools are used to improve the developer's efficiency.
Short Introduction of software engineering for bioinformatics 丈 宮本
This document provides an overview of different software engineering approaches for bioinformatics projects, including Waterfall, Agile, DevOps, eXtreme Programming, and tools like Git, GitHub, Jenkins, Docker, and Fabric. Waterfall is not well-suited for bioinformatics due to lack of flexibility, while Agile and DevOps methodologies allow for iterative development and integration of code changes. eXtreme Programming focuses on code maintainability through practices like test-driven development and continuous integration. Version control with Git/GitHub and configuration tools like Docker and Fabric can help manage reproducibility and infrastructure as code.
Take advantage of new trends in agile: Iterationless Kanban and Continuous De...Atlassian
The document discusses how Dachis Group has successfully integrated Lean Startup and Lean Development methodologies. There were three key areas of focus: building the product backlog by modeling features, epics, and stories in JIRA; structuring the Kanban flow using tools like GreenHopper and custom plugins; and implementing continuous deployment using tools like Chef, Jenkins, and custom code for automated deployments. The presentation provides examples of how Dachis Group implemented these practices for their large-scale, globally distributed teams. It recommends background reading on Lean Startup, Customer Development, Kanban, and Continuous Delivery and offers contact details for further discussion.
Yahoo adopted Scrum in 2004 with one experimental team and gradually expanded to over 200 Scrum teams by 2008 with over 1500 employees. Key results included an average team velocity increase of 35% per year, development cost reductions of over $1 million per year, and a 100% return on investment in trainings in the first year. While 15-20% of employees did not like Scrum initially, Yahoo saw faster time to market, higher quality, and satisfied customers compared to waterfall.
This presentation provides a clear path for your agile project by using a handful of simple steps. Don’t expect an ambiguous restatement of the Agile Manifesto. You will learn specific steps that will challenge your team and delight your customers.
This document summarizes and compares several popular DevOps tools used for tasks like version control, configuration management, continuous integration/delivery, monitoring, and testing. Key tools mentioned include Git, GitHub, Ansible, Jenkins, Chef, Puppet, Statuspage, ServiceNow, Docker, Kubernetes, Prometheus, Splunk, Datadog, Selenium, and JFrog Artifactory. Each tool is briefly described in terms of its main functionality and role in a DevOps workflow.
1) DevOps aims to automate and integrate processes between software development and IT teams to increase efficiency. It emphasizes cross-team communication and technology automation.
2) When adopting Salesforce DevOps, organizations face challenges around lack of best practices, admin-friendliness of tools, complexity of Salesforce environments, and finding expertise.
3) There are two main approaches to Salesforce DevOps - building out a solution using Salesforce tools like DX and scripting, or buying an ISV solution. Building provides more flexibility while buying provides pre-built features and support.
Storage, network and computational resources are becoming API driven. Configuration management tools provide another level of automation and semantics to the systems. As these tools evolve the exercise of building systems looks more and more like software development. Further, when developing web applications, the application is the infrastructure. If the servers are down, there is no application. The value of the application is tied to the systems. Treating the systems and application holistically, encouraging communication and collaboration between dev and ops is the path to true artisanal retro-futurism ⊗ team-scale anarcho-syndicalism.
This document discusses best practices for PHP application delivery and outlines challenges such as missed release dates due to lack of coordination between dev and ops teams. It presents Zend Server as a solution to improve collaboration through automated deployments and visibility. Zend Server helps meet performance expectations through application monitoring and infrastructure scaling. It also helps maintain quality with shorter cycles through code reuse, tools and training. Zend Server ensures app SLAs are met by managing changes across servers as one and proactively identifying performance issues.
Systems Management Forum 2013 (http://ac.nikkeibp.co.jp/nc/smf2013s/) の基調講演資料です。楽天では2012年4月から社内でPaaSを展開しており、その基盤の上でさまざまなサービスが開発、運用されています。講演では、楽天PaaSでのDevOpsの実践方法について具体的に紹介しました。
Google在2013開始導入Gradle工具作為新的Android build system,Gradle的使用正是實踐DevOps的良好利器,除了方便進行automated building外, Gradle更幫助我們消弭不同開發環境/工具間的差異問題,如同infarsture as code之於web application/service的重要性,build script as code就是幫助Android App快速發佈版本並維持品質穩定的關鍵最後一哩路。
此次主題將探討如何利用gradle進行精實良好的系統開發配置管理,建立一條下達開發者本地端上通產品發佈系統的透明化產品開發流水線。你是否常常一個App剛發佈不久,下一個idea已經生成,舊程式需要繼續維護同時又要添加新功能,你的開發方法是否能讓多方產品流水線順暢運行而且並行不悖?妥善利用Gradle並深入理解Build by convention的內涵是最好的選擇。
Unleashing the Power of Automated Refactoring with JDTNaresh Jain
Refactoring is a series of small steps, each of which changes the program’s internal structure without changing its external behaviour. Refactoring, as a tool, to automate behaviour-preserving transformations to source code are not only very popular in agile development environments, but have been widely established as a cornerstone of the daily software development process, regardless of the methodology being used. Most major development environments such as Eclipse offer a set of powerful refactoring to substantially increase development productivity.
In this live demo, I’ll show
* the real value of refactoring,
* how we practice it safely,
* when and why we refactor,
* the power of refactoring tools and
* when we avoid refactoring.
I’ll be using two real-world examples of refactoring and sharing what I’ve learned about this important practice of the last 15 years.
Enterprise Devops Presentation @ Magentys Seminar London May 15 2014Jwooldridge
Thanks to Liam and the crew from Magentys for arranging a fantastic evening of presentations on all things DevOps.
Attached is my presentation from the event on Enterprise Devops.
For those of you who missed it:
“Join the crowd of 100 industry leaders across the Retail, Finance and Digital sectors for an exciting evening of talks in London’s Tech City on DevOps. Enjoy networking with a chilled beer alongside the experts who are making DevOps work and those who want to make it work.
Whether you’re a corporate or start-up, DevOps should be a hot topic so listen to how the experts are achieving great things, hear their views on the trends and discuss the future of DevOps.”
Jonny
enterprisedevops.com
Litmus is a tool for chaos engineering on Kubernetes. Version 2.0 introduces new features like multi-cloud control planes, team management, workflows to sequence experiments, probes to define application steady states, support for SLOs and GitOps, and improved observability and API support. The roadmap for 2021 includes strengthening control and execution, adding more experiments and probes, and integrating with more CNCF projects.
How to go beyond traditional Scrum principles and scale to globally distributed teams with Continuous Delivery and Subversion. Presented by Andy Singleton of Assembla and Scott Rudenstein of WANdisco. Presented Nov. 15, 2012. 30 minutes.
The document discusses building a DevOps culture. It promotes having one team with one goal, pairing developers and operations staff, and sharing on-call responsibilities. It also recommends operations teams adopt agile practices like Kanban, daily standups, and retrospectives to become more aligned with development teams. The goal is to break down silos and have both teams work together seamlessly to deliver results faster.
This document summarizes scenes from implementing Scrum at a broadcasting company with offices in Berlin and Brasov. It discusses cultural differences between the German and Romanian teams that created challenges. It also outlines the company's products, organizational structure before and after adopting Scrum, and lessons learned around scaling Scrum, removing impediments, training, and allowing teams autonomy.
A very big thank you to Michael Palotas from Grid Fusion & eBay International for taking the time and effort to travel across the globe to present at the Australian Test Managers Forum 2014. If you would like any information on TMF please email tmf@kjross.com.au
Karthik Gaekwad is a member of the cloud team at National Instruments who owns the Canopy user management and licensing platform. He discusses National Instrument's approach to cloud development which includes short monthly iterations to incrementally develop and deploy new features. Key aspects of their approach include modeling the end-to-end system, designing features to be reusable across platforms, extensive testing and monitoring, and getting early user feedback through demos.
Quick Reference Poster based on the DevOps @ Microsoft transformation story (https://aka.ms/devops), focused on the five habits: Customer Focus, Production First Mindset, Team Autonomy + Enterprise Alignment, Shift Left Quality, and Infrastructure as a Flexible Resource.
We recommend you use the following to print the poster:
- Paper: (1) Satin 160 gsm (Standard) (White) - All Pages
- Page Size: Custom (16.5417 x23.3889)
- Final Size: Print on 16.54 x 23.39
MeetingPoint 2015 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver discusses how educational publisher Malmberg transitioned to continuous delivery practices using open source tools and cloud services. Key points include establishing a dedicated team to build out new infrastructure as code principles like keeping the master branch releasable at all times and treating infrastructure like code. Challenges in the transition included cultural resistance and ensuring security, while benefits were improved availability, agility, and cost reductions through higher automation. Future areas of focus include better monitoring, continuous performance and resilience testing, and security.
NextBuild 2015 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver presented on Malmberg's journey to continuous delivery using open source tools and cloud services. Malmberg is an educational publisher that builds e-learning applications using Java, Vert.x, AngularJS and MongoDB on Amazon cloud services. They faced issues with slow development and operations communication and difficult production problem analysis using a traditional model. To address this, Malmberg established an expert DevOps team, defined key principles like keeping the master branch releasable at all times and managing all automation through Jenkins, and overcame challenges like gaining developer skills and hitting AWS limits to achieve benefits like increased agility, availability and cost reductions.
Software Development 2020 - Swimming upstream in the container revolutionBert Jan Schrijver
Bert Jan Schrijver presented on Malmberg's journey to continuous delivery using open source tools and cloud services. Malmberg is an educational publisher that builds e-learning applications using Java, Vert.x, AngularJS and MongoDB on Amazon cloud services. They faced issues with slow development and operations communication and difficult production problem analysis using a traditional model. To address this, Malmberg established an expert DevOps team, defined key principles like keeping the master branch releasable at all times and managing all processes through Jenkins, and overcame challenges like gaining developer skills and infrastructure limits in transitioning to a self-service continuous delivery model. This approach improved agility, availability, cost reduction and problem resolution for Mal
Swimming upstream in the container revolutionnextbuild
Bert Jan Schrijver presented on Malmberg's journey to continuous delivery using open source tools and cloud services. Malmberg is an educational publisher that builds e-learning applications using Java, Vert.x, AngularJS and MongoDB on Amazon cloud services. They faced issues with slow development and operations communication and difficult production problem analysis using a traditional model. To address this, Malmberg established an expert DevOps team, defined key principles like keeping the master branch releasable at all times and managing all automation through Jenkins, and overcame challenges like gaining developer skills and hitting AWS limits to achieve benefits like increased agility, availability and cost reductions.
The document discusses leveraging DevOps practices to improve mainframe application delivery. It describes how traditional mainframe development and testing causes delays due to shared, restricted resources and inefficient processes. The solution presented uses DevOps tools and practices like continuous integration/delivery, dependency virtualization, and automated quality testing to enable more efficient mainframe application development and testing. This allows development and operations teams to work in parallel, validate code quality earlier, and deploy applications more frequently.
The development of a product from the point of view of a technician, starting from the concept, passing to the minimum viable till a management of a fully operational and deployed app.
Continuous Delivery the French Way – Dimitri Baeli Agile Tour Beirut
Return of experience of the CTO of lefuret.com, the leading French insurance aggregator teams on how they move from 2 weeks iteration to continuous delivery
What you will learn:
Overview of the Scrum cycle, and How they overcome the challenge of continuous integration, tips & tricks.
Continuous Delivery Agile Tour Beirut 2015Dimitri Baeli
Presentation done at Agile Tour Beirut 2015 about the way LesFurets.com learnt and applies the Continous Delivery principles.
* Books and principles
* Main activities
Rakuten Technology Conference 2011.
By David Ramos and Ilya Solovyev(LinkShare Corporation)
In today's high tech world, the complexity of projects continues to increase rapidly. Many technical organizations continuously ask themselves – what can we do to ensure the highest level of quality within a time-boxed project? When a project faces unforeseen challenges, there's an increased need for creative solutions and a higher level of teamwork. This presentation explores the coexistence of the agile and waterfall methodologies. This may be taboo in the traditional project management organization, however we have proven that it works.
The document discusses estimation in agile projects, noting that agile methods use iterative development with frequent delivery of working software to allow for emergence of requirements and capabilities. Agile estimation is done at both the iteration and release level, with developers re-estimating effort for upcoming iterations based on experience from previous iterations. Daily stand-up meetings, iteration planning meetings, and retrospectives help facilitate collaboration, adaptation, and continuous improvement in agile projects.
PuppetConf 2016: Continuous Delivery and DevOps with Jenkins and Puppet Enter...Puppet
This document discusses continuous delivery and DevOps practices using Jenkins and Puppet. It defines DevOps as addressing security at every stage and having high-performing teams that spend less time fixing issues. It also discusses the DevOps trinity of people, processes, and tools. Jenkins Pipelines and infrastructure as code with Puppet are presented as key practices for continuous delivery. The integration of Jenkins and Puppet Enterprise is demonstrated for automating application deployments.
SOASTA Webinar: Process Compression For Mobile App Dev 120612SOASTA
The webinar discusses continuous integration and automation for mobile development and testing. It presents tools from Atlassian, Zephyr, and SOASTA that can help automate the mobile development and testing process. Continuous integration with Bamboo can help developers integrate code changes more frequently and fail builds faster to catch bugs earlier. Zephyr provides test management to centralize test assets and provide visibility. SOASTA offers tools for test automation, real user monitoring, and performance/load testing to help achieve test completion with quality. Together these tools can help speed up the mobile development process through continuous integration, test automation, and visibility into the testing process.
This slide deck Introduces Chef and its role in DevOps. The agenda of the deck is as follows:
- A Review of DevOps
- BMs Continuous Delivery solution
- Introduction to Chef
- Chef and Continuous Delivery
Read more on DevOps: http://sdarchitect.wordpress.com/understanding-devops/
If you like the ideas raised in this presentation, don't forget to check out my latest book, Directing the Agile Organisation (http://theagiledirector.com/book).
This document proposes adopting an iterative development methodology that borrows from agile techniques like Scrum and XP. It suggests dividing projects into shorter 30-day iterations, with features estimated and designed at the start of each iteration. At the end of an iteration, working code would be completed along with automated testing. This approach aims to provide more accurate estimates, earlier feedback, better designed features, and more predictable development cycles compared to the current waterfall model. Key aspects to retain include code reviews, continuous integration, testing, and transparency of work.
Agile and DevOps are two software development industry heroes who have altered the way software applications are released. Explore its history, how they are related, and its distinguishing features.
Chef vs Puppet vs Ansible vs SaltStack | Configuration Management Tools Compa...Edureka!
This DevOps Tutorial takes you through what is Configuration Management all about and basic concepts of Infrastructure as code. It also compares the four most widely used Configuration Management tools i.e. Chef, Puppet, Ansible and SaltStack.
Check our complete DevOps YouTube playlist here: http://goo.gl/O2vo13
DevOps Tutorial Blog Series here: https://goo.gl/P0zAfF
Este documento presenta los principios de una organización ágil. Describe las características típicas de una organización ágil, incluyendo entregar cosas más rápido, no cumplir estimaciones y no alcanzar objetivos. Luego explica los ingredientes clave de una organización ágil, como cultura, gerentes, objetivos, procesos y organización. Finalmente, resume cómo estos ingredientes, cuando se alinean correctamente con autonomía, visión, aspiraciones guiadas por datos y equipos autónomos, pueden conducir a una organización orient
Este documento presenta una introducción a Agile y Scrum. Explica los principios fundamentales de Agile como la colaboración con el cliente, la respuesta al cambio y los individuos e interacciones. También describe los roles, reuniones y artefactos clave de Scrum como el Product Owner, el Equipo de Desarrollo y las reuniones diarias. Finalmente, analiza por qué a menudo falla la adopción de Agile debido a la resistencia al cambio y la falta de apoyo de la dirección y la cultura de la organización.
Introduction to the Agile methods used at InfoJobs. Description of the Agile manifesto and principles. Overview of Scrum, kanban and scrumban as used at InfoJobs.
Introduction of Cybersecurity with OSS at Code Europe 2024Hiroshi SHIBATA
I develop the Ruby programming language, RubyGems, and Bundler, which are package managers for Ruby. Today, I will introduce how to enhance the security of your application using open-source software (OSS) examples from Ruby and RubyGems.
The first topic is CVE (Common Vulnerabilities and Exposures). I have published CVEs many times. But what exactly is a CVE? I'll provide a basic understanding of CVEs and explain how to detect and handle vulnerabilities in OSS.
Next, let's discuss package managers. Package managers play a critical role in the OSS ecosystem. I'll explain how to manage library dependencies in your application.
I'll share insights into how the Ruby and RubyGems core team works to keep our ecosystem safe. By the end of this talk, you'll have a better understanding of how to safeguard your code.
Nunit vs XUnit vs MSTest Differences Between These Unit Testing Frameworks.pdfflufftailshop
When it comes to unit testing in the .NET ecosystem, developers have a wide range of options available. Among the most popular choices are NUnit, XUnit, and MSTest. These unit testing frameworks provide essential tools and features to help ensure the quality and reliability of code. However, understanding the differences between these frameworks is crucial for selecting the most suitable one for your projects.
Skybuffer SAM4U tool for SAP license adoptionTatiana Kojar
Manage and optimize your license adoption and consumption with SAM4U, an SAP free customer software asset management tool.
SAM4U, an SAP complimentary software asset management tool for customers, delivers a detailed and well-structured overview of license inventory and usage with a user-friendly interface. We offer a hosted, cost-effective, and performance-optimized SAM4U setup in the Skybuffer Cloud environment. You retain ownership of the system and data, while we manage the ABAP 7.58 infrastructure, ensuring fixed Total Cost of Ownership (TCO) and exceptional services through the SAP Fiori interface.
A Comprehensive Guide to DeFi Development Services in 2024Intelisync
DeFi represents a paradigm shift in the financial industry. Instead of relying on traditional, centralized institutions like banks, DeFi leverages blockchain technology to create a decentralized network of financial services. This means that financial transactions can occur directly between parties, without intermediaries, using smart contracts on platforms like Ethereum.
In 2024, we are witnessing an explosion of new DeFi projects and protocols, each pushing the boundaries of what’s possible in finance.
In summary, DeFi in 2024 is not just a trend; it’s a revolution that democratizes finance, enhances security and transparency, and fosters continuous innovation. As we proceed through this presentation, we'll explore the various components and services of DeFi in detail, shedding light on how they are transforming the financial landscape.
At Intelisync, we specialize in providing comprehensive DeFi development services tailored to meet the unique needs of our clients. From smart contract development to dApp creation and security audits, we ensure that your DeFi project is built with innovation, security, and scalability in mind. Trust Intelisync to guide you through the intricate landscape of decentralized finance and unlock the full potential of blockchain technology.
Ready to take your DeFi project to the next level? Partner with Intelisync for expert DeFi development services today!
Unlock the Future of Search with MongoDB Atlas_ Vector Search Unleashed.pdfMalak Abu Hammad
Discover how MongoDB Atlas and vector search technology can revolutionize your application's search capabilities. This comprehensive presentation covers:
* What is Vector Search?
* Importance and benefits of vector search
* Practical use cases across various industries
* Step-by-step implementation guide
* Live demos with code snippets
* Enhancing LLM capabilities with vector search
* Best practices and optimization strategies
Perfect for developers, AI enthusiasts, and tech leaders. Learn how to leverage MongoDB Atlas to deliver highly relevant, context-aware search results, transforming your data retrieval process. Stay ahead in tech innovation and maximize the potential of your applications.
#MongoDB #VectorSearch #AI #SemanticSearch #TechInnovation #DataScience #LLM #MachineLearning #SearchTechnology
Letter and Document Automation for Bonterra Impact Management (fka Social Sol...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on automated letter generation for Bonterra Impact Management using Google Workspace or Microsoft 365.
Interested in deploying letter generation automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Digital Marketing Trends in 2024 | Guide for Staying AheadWask
https://www.wask.co/ebooks/digital-marketing-trends-in-2024
Feeling lost in the digital marketing whirlwind of 2024? Technology is changing, consumer habits are evolving, and staying ahead of the curve feels like a never-ending pursuit. This e-book is your compass. Dive into actionable insights to handle the complexities of modern marketing. From hyper-personalization to the power of user-generated content, learn how to build long-term relationships with your audience and unlock the secrets to success in the ever-shifting digital landscape.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
GraphRAG for Life Science to increase LLM accuracyTomaz Bratanic
GraphRAG for life science domain, where you retriever information from biomedical knowledge graphs using LLMs to increase the accuracy and performance of generated answers
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
Main news related to the CCS TSI 2023 (2023/1695)Jakub Marek
An English 🇬🇧 translation of a presentation to the speech I gave about the main changes brought by CCS TSI 2023 at the biggest Czech conference on Communications and signalling systems on Railways, which was held in Clarion Hotel Olomouc from 7th to 9th November 2023 (konferenceszt.cz). Attended by around 500 participants and 200 on-line followers.
The original Czech 🇨🇿 version of the presentation can be found here: https://www.slideshare.net/slideshow/hlavni-novinky-souvisejici-s-ccs-tsi-2023-2023-1695/269688092 .
The videorecording (in Czech) from the presentation is available here: https://youtu.be/WzjJWm4IyPk?si=SImb06tuXGb30BEH .
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Tatiana Kojar
Skybuffer AI, built on the robust SAP Business Technology Platform (SAP BTP), is the latest and most advanced version of our AI development, reaffirming our commitment to delivering top-tier AI solutions. Skybuffer AI harnesses all the innovative capabilities of the SAP BTP in the AI domain, from Conversational AI to cutting-edge Generative AI and Retrieval-Augmented Generation (RAG). It also helps SAP customers safeguard their investments into SAP Conversational AI and ensure a seamless, one-click transition to SAP Business AI.
With Skybuffer AI, various AI models can be integrated into a single communication channel such as Microsoft Teams. This integration empowers business users with insights drawn from SAP backend systems, enterprise documents, and the expansive knowledge of Generative AI. And the best part of it is that it is all managed through our intuitive no-code Action Server interface, requiring no extensive coding knowledge and making the advanced AI accessible to more users.
10. CUSTOMER
1 COLLABORATION
over contract negotiation
MANIFESTO
AGILE
INDIVIDUALS and
2 INTERACTIONS
over processes and tools
RESPONDING to
3 CHANGE
over following a plan
WORKING
4 SOFTWARE
over full documentation
11. 1 DELIVER SOFTWARE
2 EMBRACE CHANGE
SHOW OFTEN
AGILE 3
PRINCIPLES 4 WORK TOGETHER
5 PROVIDE ENVIRONMENT
6 CHAT FACE-to-FACE
7 MINIMIZE WASTE
8 MAINTAIN PACE
9 SEEK TECH EXCELLENCE
10 LOVE SIMPLICITY
11 SELF-ORGANIZE TEAMS
12 IMPROVE CONTINUOUSLY
12. TIME BOXED
PLANNING
Fixed
Scope Time Cost
Agile!
Traditional
Estimated
Cost Time Scope
From a plan driven approach to a value driven one.
13. SCRUM
DEFINITION
iterative, incremental methodology for
project management often seen in agile
software development.
14. SCRUM
ROLES
PRODUCT OWNER
1
the voice of the customer
TEAM MEMBER
2
deliver the product
SCRUM MASTER
3
facilitator, mentor, coach
EXTERNAL EXPERTS
4
consultants, assessors, auditors
15. SCRUM
TEAMS
Team
Prod. Owner
?" ?"
Tech Lead Test engineers Int. designer
Visual Interface
Scrum Master designer
#" #" #" <>#
Developers Front-end dev.
?*#
QA Lead
16. In this beginning stage the
MYSCRUM?
At this point the student Now the student isn't
student follows the begins to branch out. With learning from other
teachings of one master the basic practices people, but from his own
precisely. He concentrates working he now starts to practice. He creates his
on how to do the learn the underlying own approaches and
task, without worrying too principles and theory adapts what he's learned
much about the underlying behind the technique. He to his own particular
theory. If there are multiple also starts learning from circumstances.
variations on how to do other masters and
the task, he concentrates integrates that learning
on just the one way his into his practice.
master teaches him.
shu ha ri
20. RELEASE
FREQUENTLY
Number of days with
releases
1 release 3,5 releases
every 2 every week!
weeks
IJ 2010 IJ 2012
21. CONTINUOUS
DELIVERY
Constant flow of new features into production
22. CONTINUOUS
DELIVERY
Flickr deploy ten times each
day...
Why don’t you?
http://code.flickr.com/
IJ 2010 IJ 2012 Flickr
23. PRODUCTION-READY
SOFTWARE
Fast, automated feedback on the
production readyness of your
application every time there is a
change – to code, infrastructure, or
configuration
http://channel9.msdn.com/Events/ALM-Summit/2011/Continuous-
Delivery
24. PRINCIPLES
create a repeatable, build quality in
reliable process for
releasing software done means released
automate almost everybody is
everything responsible for delivery
keep everything in continuous
version control improvement (kaizen)
http://gotocon.com/dl/jaoo-aarhus-2010/slides/JezHumble_ContinuousDelivery.pdf
25. Source control Perforce
CI server Jenkins
One-step build Ant Maven
Continuous delivery pillars
Automated testing JUnit QTP
27. ZERO* DOWNTIME
RELEASE UPDATES
To upgrade from 1.1 to 2.0
Release 1.1 Release 1.2 Release 1.3 Release 2.0 Release 2.1
Initial Make 1.1 Migrate db Clean 1.1
app to 2.0 compat DB
compatible
with 2.0 DB
DB Changes Release updated! DB Changes