The document discusses agile development workflows represented by cards on a wall. It describes common workflow stages like analysis, design, code, test, and deploy. In agile, the workflow is sequential but development is concurrent with small tasks. Tasks are represented on cards that move through different stages as work is completed, including "to do", "in progress", and "done". Parameters like throughput, latency and queue limits are used to manage workflow.
Scrum with Kanban; small adjustments, big improvementsPaulo Caroli
Scrum with Kanban; small adjustments, big improvements.
Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.
O XP não é contra Design com Paulo Caroli, Café Ágil em RecifePaulo Caroli
Nesta palestra Paulo Caroli, Agilista e protagonista da ThoughtWorks Brasil, vai falar sobre XP (eXtreme Programming) e o desentendimento de que XP não promove design.
Esta palestra vai explorar design em XP, comparando com design em processos de software mais tradicionais. Você entenderá como XP promove aperfeiçoamento contínuo de design através das práticas de Design Simples, Integração Contínua, Desenvolvimento Baseado em Testes e Refactoring.
Direto ao ponto; criando produtos de forma enxutaPaulo Caroli
“Construir, Medir, Aprender”, como diz Steve Blank, é muito mais elaborado do que colocar software em produção para ver se funciona. O Lean Startup é interessante, mas para desenvolvedores de software acaba se traduzindo em uma importante pergunta: “Tá, mas o que construir?”.
Não é fácil lidar com essa disparidade entre o significado de Produto Mínimo Viável para o negócio e a iniciação de projetos de software que tentam criar produtos de forma enxuta. Depois de experimentar muitos estilos de iniciação do projeto de software, documentamos uma receita que vem sendo aplicada no cotidiano e funcionando muito bem. A esse conjunto de práticas e técnicas demos o nome de Direto ao Ponto.
Venha assistir nesta palestra uma conversa sobre MVP e um resumo da receita efetiva para iniciação do projetos de software que vai entregar o produto de forma enxuta.
Measuring lead time is important and is a key performance indicator (KPI) that every Agile team should track. Poor lead time causes bottlenecks in the team production flow, inefficiencies, delay costs, not to mention unhappy customers. Come to this session to discuss with others how to track and monitor improvement on lead time.
Retrospectivas Divertidas: atividades e idéias para fazer retrospectivas ágei...Paulo Caroli
A habilidade de aprender e responder rapidamente é uma das características de uma equipe de desenvolvimento bem sucedida. Como transformar um grupo de pessoas em uma equipe, que aprende com seus erros e compartilha seus sucessos?
Retrospectivas ajudam a melhorar a comunicação, produtividade e qualidade no dia a dia, porém reunir um grupo de pessoas para falar sobre problemas e discutir melhorias não é tarefa fácil.
Esta palestra falará sobre como criar um ambiente seguro, em que as pessoas se sintam confortáveis para compartilhar suas reais opiniões. Apresentaremos técnicas e atividades que podem ser utilizadas em diferentes contextos, de forma que toda a equipe seja ouvida e que suas discussões se transformem em ações de melhoria.
O XP não é contra Design com Paulo Caroli, Café Ágil em Recife Paulo Caroli
Nesta palestra Paulo Caroli, Agilista e protagonista da ThoughtWorks Brasil, vai falar sobre XP (eXtreme Programming) e o desentendimento de que XP não promove design.
Esta palestra vai explorar design em XP, comparando com design em processos de software mais tradicionais. Você entenderá como XP promove aperfeiçoamento contínuo de design através das práticas de Design Simples, Integração Contínua, Desenvolvimento Baseado em Testes e Refactoring.
Scrum with Kanban; small adjustments, big improvementsPaulo Caroli
Scrum with Kanban; small adjustments, big improvements.
Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.
O XP não é contra Design com Paulo Caroli, Café Ágil em RecifePaulo Caroli
Nesta palestra Paulo Caroli, Agilista e protagonista da ThoughtWorks Brasil, vai falar sobre XP (eXtreme Programming) e o desentendimento de que XP não promove design.
Esta palestra vai explorar design em XP, comparando com design em processos de software mais tradicionais. Você entenderá como XP promove aperfeiçoamento contínuo de design através das práticas de Design Simples, Integração Contínua, Desenvolvimento Baseado em Testes e Refactoring.
Direto ao ponto; criando produtos de forma enxutaPaulo Caroli
“Construir, Medir, Aprender”, como diz Steve Blank, é muito mais elaborado do que colocar software em produção para ver se funciona. O Lean Startup é interessante, mas para desenvolvedores de software acaba se traduzindo em uma importante pergunta: “Tá, mas o que construir?”.
Não é fácil lidar com essa disparidade entre o significado de Produto Mínimo Viável para o negócio e a iniciação de projetos de software que tentam criar produtos de forma enxuta. Depois de experimentar muitos estilos de iniciação do projeto de software, documentamos uma receita que vem sendo aplicada no cotidiano e funcionando muito bem. A esse conjunto de práticas e técnicas demos o nome de Direto ao Ponto.
Venha assistir nesta palestra uma conversa sobre MVP e um resumo da receita efetiva para iniciação do projetos de software que vai entregar o produto de forma enxuta.
Measuring lead time is important and is a key performance indicator (KPI) that every Agile team should track. Poor lead time causes bottlenecks in the team production flow, inefficiencies, delay costs, not to mention unhappy customers. Come to this session to discuss with others how to track and monitor improvement on lead time.
Retrospectivas Divertidas: atividades e idéias para fazer retrospectivas ágei...Paulo Caroli
A habilidade de aprender e responder rapidamente é uma das características de uma equipe de desenvolvimento bem sucedida. Como transformar um grupo de pessoas em uma equipe, que aprende com seus erros e compartilha seus sucessos?
Retrospectivas ajudam a melhorar a comunicação, produtividade e qualidade no dia a dia, porém reunir um grupo de pessoas para falar sobre problemas e discutir melhorias não é tarefa fácil.
Esta palestra falará sobre como criar um ambiente seguro, em que as pessoas se sintam confortáveis para compartilhar suas reais opiniões. Apresentaremos técnicas e atividades que podem ser utilizadas em diferentes contextos, de forma que toda a equipe seja ouvida e que suas discussões se transformem em ações de melhoria.
O XP não é contra Design com Paulo Caroli, Café Ágil em Recife Paulo Caroli
Nesta palestra Paulo Caroli, Agilista e protagonista da ThoughtWorks Brasil, vai falar sobre XP (eXtreme Programming) e o desentendimento de que XP não promove design.
Esta palestra vai explorar design em XP, comparando com design em processos de software mais tradicionais. Você entenderá como XP promove aperfeiçoamento contínuo de design através das práticas de Design Simples, Integração Contínua, Desenvolvimento Baseado em Testes e Refactoring.
Scrum with Kanban. Small adjustments, big improvements.Johann Arispe
Scrum with Kanban; small adjustments, big improvements (Paulo Caroli and Johann Arispe)
Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.
A linha de montagem de SW -n paulo caroli - QconSP 2010Paulo Caroli
Esta palestra sobre “Agile Card Wall” explica esta abordagem única para a gestão e acompanhamento do desenvolvimento de software. Você vai aprender técnicas valiosas que podem ser aplicadas a qualquer empresa e equipe que procura melhorar a sua implementação Agil. Você vai descobrir como uma simples ferramenta que complementa as práticas, princípios e valores de Agile pode transformar sua organização.
Nesta palestra voce vai entender como cartões na parede tornam conceitos básicos de Scrum, Lean e XP visíveis a todo time.
Understand why we keep missing deadlines; what is the element that keeps making us give incorrect dates and how we can estimate better with mathematical basis!
Fast and accurate metrics. Is it actually possible?Bogdan Storozhuk
This talk is a story about complete redesign of one data structure from Dropwizard Metrics library to achieve some way of measuring histogram without outliers, approximations and with acceptable performance. We will talk about hard and controversial decisions programmer should make to design fast, concise but in the same time very simple data structures. You will learn about: memory consumption optimizations, minimizing allocations, decreasing GC pressure, achieving thread safety.
Lean Kanban India 2017 | Damn… we missed the date again! | Sudipta LahiriLeanKanbanIndia
Session Title : Damn… we missed the date again!
Session Overview:We have experienced the embarrassment of missing our planned dates. Ironically, this cycle doesn’t end with one instance. We re-commit to another date and miss than again! We are all experienced people, we have been in this business for a long time. Why then do we keep missing our dates again and again?
Scrum makes a sincere attempt in changing this pattern. By making the team estimate how much it can deliver within a Sprint and by mandating that the team should be not be disturbed with changing scope within a Sprint, it attempts to increase the probability of hitting the dates. Yet, it isn’t uncommon for teams to be burnt out by the time the Sprint ends OR for unfinished scope spilling over to the next Sprint.
Clearly, something is wrong at the core. Why is this so difficult? Is it reasonable to keep blaming the team or the people managing the project? This experience isn’t the exception! It is the norm in most teams.
In this session, we discuss what is wrong at the core. What are we missing in our planning? If this does not work, what will? Does Kanban have a solution for this?
At the end of this session, you should be able to learn how not to fall into this trap again!
There is much hype about Kanban since it was used by supermarkets and then perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach.
As project managers and software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar.
In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will dive into concepts such as limiting work in progress, Minimum Viable Product and Minimum Marketable Feature and see how these concepts can make our lives easier.
During this session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do.
How we improved i os delivery speed from qa side by Kateryna SprynsianBadoo
Quality Assurance often has two sides. On the one hand, team leads always encourage us to be faster than the speed of light when we talk about feature delivery. On the other hand, QA's dream of spending less time on regressions and more time doing automation, non-functional testing, etc. Come along to learn the success story of how we gained time for interesting tasks by moving to flows with little or no manual QA, but still managed to save our jobs.
Are we there yet?
Opening keynote, London Lean Kanban Day #llkd15
What is Kanban, where does it take us, and how will we know we’ve arrived?
Updated July 2015 for
Live Agile Workshop & Forum Group, Singapore
BCS Nottingham & Derby
Agile Metrics : Velocity is NOT the Goal - NDC Oslo 2014Doc Norton
Velocity is one of the most common metrics used-and one of the most commonly misused-on agile projects. Velocity is simply a measurement of speed in a given direction-the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team?
Michael “Doc" Norton walks us through the Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks. Leave with a toolkit of additional metrics that, coupled with velocity, give a better view of the project's overall health.
Slides to my Discovering Scrum Workshop in cooperation with RUMOS in Lisbon. Exercises include "Remember Heavan" (what was your best project?), Why waterfall and software development don't mix, How Scrum is different, and gathering requirements from stakeholders.
Kanban for Software Development and Kaizen CultureAcquate
Talk #1 - Kanban for Developers
There is much hype about Kanban since it was perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach.
As software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar.
In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will also compare manufacturing practices with software development techniques and see how we can benefit from their experiences. During the session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do.
Talk #2 - Kaizen: Continuous Process Improvement
Enterprises can utilize Process Improvement to improve their workflow, allowing them to be more efficient, eliminate bottlenecks and problem areas, and as a result, achieve reduced costs, on-time delivery and increased profits. Currently, enterprises are facing stiffer competition to win customer acceptance through quality, and the need to develop more customer-oriented products and services faster than ever before.
Einstein said "We can't solve problems by using the same kind of thinking we used when we created them.", and that is what lies at the heart of Kaizen. Improvement comes with a different look at the problems and doing this continuously every day and everywhere. It is more of a company culture than a project.
But where do we start improving? British comic writer Douglas Adams said "See first, think later, then test. But always see first. Otherwise you will only see what you were expecting.". And that is exactly where we start. By looking deep into our workflow and process.
In this session, we will look at Kaizen philosophy, why change is important and very hard to do. we'll also analyze waste and why it is bad for our business and see how quality-first approach makes us better at what we do. I will also provide some test cases and finish off by looking into implementing a Kaizen culture at the office by involving everybody.
This is the video of me giving this presentation: https://youtu.be/fxorF66SDmo
What does a lead developer do, and how do they function on a software development team? This videos takes you through an average lead developer's calendar and their daily interactions, in order to gain a better insight into their function and methodologies.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
Scrum with Kanban. Small adjustments, big improvements.Johann Arispe
Scrum with Kanban; small adjustments, big improvements (Paulo Caroli and Johann Arispe)
Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.
A linha de montagem de SW -n paulo caroli - QconSP 2010Paulo Caroli
Esta palestra sobre “Agile Card Wall” explica esta abordagem única para a gestão e acompanhamento do desenvolvimento de software. Você vai aprender técnicas valiosas que podem ser aplicadas a qualquer empresa e equipe que procura melhorar a sua implementação Agil. Você vai descobrir como uma simples ferramenta que complementa as práticas, princípios e valores de Agile pode transformar sua organização.
Nesta palestra voce vai entender como cartões na parede tornam conceitos básicos de Scrum, Lean e XP visíveis a todo time.
Understand why we keep missing deadlines; what is the element that keeps making us give incorrect dates and how we can estimate better with mathematical basis!
Fast and accurate metrics. Is it actually possible?Bogdan Storozhuk
This talk is a story about complete redesign of one data structure from Dropwizard Metrics library to achieve some way of measuring histogram without outliers, approximations and with acceptable performance. We will talk about hard and controversial decisions programmer should make to design fast, concise but in the same time very simple data structures. You will learn about: memory consumption optimizations, minimizing allocations, decreasing GC pressure, achieving thread safety.
Lean Kanban India 2017 | Damn… we missed the date again! | Sudipta LahiriLeanKanbanIndia
Session Title : Damn… we missed the date again!
Session Overview:We have experienced the embarrassment of missing our planned dates. Ironically, this cycle doesn’t end with one instance. We re-commit to another date and miss than again! We are all experienced people, we have been in this business for a long time. Why then do we keep missing our dates again and again?
Scrum makes a sincere attempt in changing this pattern. By making the team estimate how much it can deliver within a Sprint and by mandating that the team should be not be disturbed with changing scope within a Sprint, it attempts to increase the probability of hitting the dates. Yet, it isn’t uncommon for teams to be burnt out by the time the Sprint ends OR for unfinished scope spilling over to the next Sprint.
Clearly, something is wrong at the core. Why is this so difficult? Is it reasonable to keep blaming the team or the people managing the project? This experience isn’t the exception! It is the norm in most teams.
In this session, we discuss what is wrong at the core. What are we missing in our planning? If this does not work, what will? Does Kanban have a solution for this?
At the end of this session, you should be able to learn how not to fall into this trap again!
There is much hype about Kanban since it was used by supermarkets and then perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach.
As project managers and software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar.
In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will dive into concepts such as limiting work in progress, Minimum Viable Product and Minimum Marketable Feature and see how these concepts can make our lives easier.
During this session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do.
How we improved i os delivery speed from qa side by Kateryna SprynsianBadoo
Quality Assurance often has two sides. On the one hand, team leads always encourage us to be faster than the speed of light when we talk about feature delivery. On the other hand, QA's dream of spending less time on regressions and more time doing automation, non-functional testing, etc. Come along to learn the success story of how we gained time for interesting tasks by moving to flows with little or no manual QA, but still managed to save our jobs.
Are we there yet?
Opening keynote, London Lean Kanban Day #llkd15
What is Kanban, where does it take us, and how will we know we’ve arrived?
Updated July 2015 for
Live Agile Workshop & Forum Group, Singapore
BCS Nottingham & Derby
Agile Metrics : Velocity is NOT the Goal - NDC Oslo 2014Doc Norton
Velocity is one of the most common metrics used-and one of the most commonly misused-on agile projects. Velocity is simply a measurement of speed in a given direction-the rate at which a team is delivering toward a product release. As with a vehicle en route to a particular destination, increasing the speed may appear to ensure a timely arrival. However, that assumption is dangerous because it ignores the risks with higher speeds. And while it’s easy to increase a vehicle’s speed, where exactly is the accelerator on a software team?
Michael “Doc" Norton walks us through the Hawthorne Effect and Goodhart’s Law to explain why setting goals for velocity can actually hurt a project's chances. Take a look at what can negatively impact velocity, ways to stabilize fluctuating velocity, and methods to improve velocity without the risks. Leave with a toolkit of additional metrics that, coupled with velocity, give a better view of the project's overall health.
Slides to my Discovering Scrum Workshop in cooperation with RUMOS in Lisbon. Exercises include "Remember Heavan" (what was your best project?), Why waterfall and software development don't mix, How Scrum is different, and gathering requirements from stakeholders.
Kanban for Software Development and Kaizen CultureAcquate
Talk #1 - Kanban for Developers
There is much hype about Kanban since it was perfected and introduced to the world by Toyota. Since then, not only manufacturers but all businesses looked into this simple but extremely powerful approach.
As software developers are yearning for better project management and visibility on all aspects of their work, Kanban naturally blipped on their radar.
In this session, we will look at the origins of Kanban, how it applies to software development along with misunderstandings and myths. We will also compare manufacturing practices with software development techniques and see how we can benefit from their experiences. During the session we will have some interactive exercises to help us better understand Kanban and becoming more efficient and productive by limiting the amount of work we do.
Talk #2 - Kaizen: Continuous Process Improvement
Enterprises can utilize Process Improvement to improve their workflow, allowing them to be more efficient, eliminate bottlenecks and problem areas, and as a result, achieve reduced costs, on-time delivery and increased profits. Currently, enterprises are facing stiffer competition to win customer acceptance through quality, and the need to develop more customer-oriented products and services faster than ever before.
Einstein said "We can't solve problems by using the same kind of thinking we used when we created them.", and that is what lies at the heart of Kaizen. Improvement comes with a different look at the problems and doing this continuously every day and everywhere. It is more of a company culture than a project.
But where do we start improving? British comic writer Douglas Adams said "See first, think later, then test. But always see first. Otherwise you will only see what you were expecting.". And that is exactly where we start. By looking deep into our workflow and process.
In this session, we will look at Kaizen philosophy, why change is important and very hard to do. we'll also analyze waste and why it is bad for our business and see how quality-first approach makes us better at what we do. I will also provide some test cases and finish off by looking into implementing a Kaizen culture at the office by involving everybody.
This is the video of me giving this presentation: https://youtu.be/fxorF66SDmo
What does a lead developer do, and how do they function on a software development team? This videos takes you through an average lead developer's calendar and their daily interactions, in order to gain a better insight into their function and methodologies.
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
6. Um fluxo de trabalho (workflow)
é uma sequência de etapas e
atividades de trabalho realizado
por uma pessoa ou uma equipe,
para alcançar um objetivo
específico.
235. Obrigado!
Perguntas?
A linha de montagem de SW
representada como cartões na parede
Paulo Caroli Agile Coach
pcaroli@thoughtworks.com
Twitter: @paulocaroli