Creating a Better Testing Future: The World Is Changing and We Must Change With It
•
1 like•435 views
The IEEE 829 Test Documentation standard is thirty years old this year. Boris Beizer’s first book on software testing also turned thirty. Testing Computer Software, the best selling book on software testing, is twenty-five. During the last three decades, hardware platforms have evolved from mainframes to minis to desktops to laptops to tablets to smartphones. Development paradigms have shifted from waterfall to agile. Consumers expect more functionality, demand higher quality, and are less loyal to brands. The world has changed dramatically and testing must change to match it. Testing processes that helped us succeed in the past may prevent our success in the future. Lee Copeland shares his insights into the future of testing, sharing his Do’s and Don’ts in the areas of technology, organization, test processes, test plans, and automation. Join Lee for a thought provoking look at creating a better testing future.
Report
Share
Report
Share
Download to read offline
Recommended
What I learned from 5 years of sciencing the crap out of DevOps
For years we laboured under the misapprehension that going faster meant breaking things. After several years of science-ing, Jez and Dr Nicole Forsgren have identified the key elements that enable not just higher throughput but also higher stability, availability and quality, lower cost, and happier teams. Discover how continuous delivery, cloud infrastructure, and effective management and leadership practices produce higher software delivery performance (and indeed what we might mean by performance), along with how to measure culture and its impact on IT and organizational culture. Find out how we actually ensure our results are reliable and meaningful. Learn the patterns and practices used by high performing organizations to outcompete their peers.
The Changing Role of Release Engineering in a DevOps World
There is no denying that DevOps has shaken up the world of developing and deploying software. With all the buzz around new techniques and technologies, it's easy to get lost in the “We deploy hundreds of times a day!” cacophony and all the new tools. The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
Tools Won't Fix Your Broken DevOps
This document appears to be a slide presentation on DevOps practices and culture. Some key points discussed include:
- High-performing IT organizations are twice as likely to exceed goals in areas like profitability and customer satisfaction.
- DevOps focuses on continuous delivery, quality, lean processes, effective collaboration, and a culture of learning from failures.
- Culture can be measured and influenced by providing employees the tools and training to do their jobs successfully.
- Adopting DevOps practices may lead to improved lead times, release frequency, change fail rates, and service restoration times.
The Data Behind DevOps: What Does it Take to be a High Performer? Jenkins Wor...
How do you become a high performing technology organization? Over the past five years, the State of DevOps Report has shown how the highest-performing technology teams decisively outperform their lower-performing peers. The report has also investigated the effects of burnout, culture and employee engagement on organizational performance. Nicole Forsgren shares insights into the key leadership, technical, architectural, and product capabilities that drive these outcomes, including new findings from cloud, outsourcing, and open source. She offers highlights and surprises uncovered over the last five years from over 30,000 responses.
Vmware2021 why even devop nicolefv
So often, we talk about doing the DevOps for money, fame, and high performance. But DevOps was the original hipster of changing the way we work to take care of ourselves and each other. In this talk, Nicole Forsgren will discuss how these technology transformations can not only help us ship software with speed and stability, they can reduce burnout, improve our culture, and communicate better. She will also share the latest research from her team about productivity, and what this means for the future of work -- spoiler alert: productivity is personal. As we shift back into work patterns that look like normal (whatever normal is), we can reimagine cultures and technologies that shift to support us and our teams -- just like DevOps did in its beginning.
How is testing different in a DevOps agile team. A perspective from the team.
In this webinar some of the test team at NewVoiceMedia will discuss how testing has changed for them and why working in an agile team is positive for a tester
Find out more - http://testhuddle.com/resource/testing-in-devops/
Soaring in the Clouds - Don't be dragged down by ITIL bloat!
Cloud computing is here and being used by organizations to allow them to be more fleet footed in time to market, and nimble in aligning to changing business needs when it comes to delivering the services to the business and its customers. From a service management perspective it makes no difference wether the service is delivered from the "Cloud", an in house hosted infrastructure or a combination of both. You still need a framework for managing service delivery and ensuring services.
Presentation by Brian Lenner, Principal Consultant at Navvia.
Visit http://navvia.com to know more.
Software as Craft
This document summarizes the key findings from the 2018 State of DevOps report. Some of the main points include:
- Elite performing teams are still able to optimize for throughput, stability and availability.
- Adopting essential cloud characteristics and using cloud resources effectively is correlated with high performance.
- Architecture and how teams are structured matters more than the specific technology stack.
- Open source software usage and avoiding outsourcing are correlated with better performance.
- Continuous testing, monitoring, security and including the database in DevOps practices are emerging technical best practices.
- Culture and ensuring autonomy for teams also contributes significantly to performance.
Recommended
What I learned from 5 years of sciencing the crap out of DevOps
For years we laboured under the misapprehension that going faster meant breaking things. After several years of science-ing, Jez and Dr Nicole Forsgren have identified the key elements that enable not just higher throughput but also higher stability, availability and quality, lower cost, and happier teams. Discover how continuous delivery, cloud infrastructure, and effective management and leadership practices produce higher software delivery performance (and indeed what we might mean by performance), along with how to measure culture and its impact on IT and organizational culture. Find out how we actually ensure our results are reliable and meaningful. Learn the patterns and practices used by high performing organizations to outcompete their peers.
The Changing Role of Release Engineering in a DevOps World
There is no denying that DevOps has shaken up the world of developing and deploying software. With all the buzz around new techniques and technologies, it's easy to get lost in the “We deploy hundreds of times a day!” cacophony and all the new tools. The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
Tools Won't Fix Your Broken DevOps
This document appears to be a slide presentation on DevOps practices and culture. Some key points discussed include:
- High-performing IT organizations are twice as likely to exceed goals in areas like profitability and customer satisfaction.
- DevOps focuses on continuous delivery, quality, lean processes, effective collaboration, and a culture of learning from failures.
- Culture can be measured and influenced by providing employees the tools and training to do their jobs successfully.
- Adopting DevOps practices may lead to improved lead times, release frequency, change fail rates, and service restoration times.
The Data Behind DevOps: What Does it Take to be a High Performer? Jenkins Wor...
How do you become a high performing technology organization? Over the past five years, the State of DevOps Report has shown how the highest-performing technology teams decisively outperform their lower-performing peers. The report has also investigated the effects of burnout, culture and employee engagement on organizational performance. Nicole Forsgren shares insights into the key leadership, technical, architectural, and product capabilities that drive these outcomes, including new findings from cloud, outsourcing, and open source. She offers highlights and surprises uncovered over the last five years from over 30,000 responses.
Vmware2021 why even devop nicolefv
So often, we talk about doing the DevOps for money, fame, and high performance. But DevOps was the original hipster of changing the way we work to take care of ourselves and each other. In this talk, Nicole Forsgren will discuss how these technology transformations can not only help us ship software with speed and stability, they can reduce burnout, improve our culture, and communicate better. She will also share the latest research from her team about productivity, and what this means for the future of work -- spoiler alert: productivity is personal. As we shift back into work patterns that look like normal (whatever normal is), we can reimagine cultures and technologies that shift to support us and our teams -- just like DevOps did in its beginning.
How is testing different in a DevOps agile team. A perspective from the team.
In this webinar some of the test team at NewVoiceMedia will discuss how testing has changed for them and why working in an agile team is positive for a tester
Find out more - http://testhuddle.com/resource/testing-in-devops/
Soaring in the Clouds - Don't be dragged down by ITIL bloat!
Cloud computing is here and being used by organizations to allow them to be more fleet footed in time to market, and nimble in aligning to changing business needs when it comes to delivering the services to the business and its customers. From a service management perspective it makes no difference wether the service is delivered from the "Cloud", an in house hosted infrastructure or a combination of both. You still need a framework for managing service delivery and ensuring services.
Presentation by Brian Lenner, Principal Consultant at Navvia.
Visit http://navvia.com to know more.
Software as Craft
This document summarizes the key findings from the 2018 State of DevOps report. Some of the main points include:
- Elite performing teams are still able to optimize for throughput, stability and availability.
- Adopting essential cloud characteristics and using cloud resources effectively is correlated with high performance.
- Architecture and how teams are structured matters more than the specific technology stack.
- Open source software usage and avoiding outsourcing are correlated with better performance.
- Continuous testing, monitoring, security and including the database in DevOps practices are emerging technical best practices.
- Culture and ensuring autonomy for teams also contributes significantly to performance.
Successful writing at work copyright 2017 cengage learn
This document is the table of contents for a book about successful writing at work. It outlines the contents of the book, which covers topics such as identifying audiences, establishing purpose, adapting style and tone for different audiences, characteristics of job-related writing, writing ethically, the writing process of researching, planning, drafting, revising and editing, collaborative writing, and conducting effective meetings. The table of contents provides an overview of what is covered in each chapter to help readers understand what content is included in the book.
Lean Product Management User-Centered App Design
The document discusses lean product management and user-centered app design. It covers topics like doing just enough to provide early value to users, eliminating waste, engaging workforces with few meetings and continuous delivery, and learning just enough, designing just enough, and delivering just enough. The secrets to being a modern software organization are said to be speed to market, customer focus, and engaged workforce. Critical components of a successful product are described as being desirable, viable, and feasible.
The Key to High Performance - What the Data Says
Over the past five years, the State of DevOps Report has shown that high-performing IT teams decisively outperform their peers: they deploy 200x more frequently, with 2,555 faster lead times and 1/3 change fail rate. This year, we investigate architecture, experimentation in work, other business outcomes (e.g., for gov't). Come see the latest in what it takes to make software amazing.
Unbloat your SDLC
There are no two SDLC processes that are the same. Every company/project has their own specific SDLC process, however the only thing that most have in common is their bloat. The bloat is most evident in the time-to-market aspect of the project. Other evidence of this bloat is slow QA cycles, implementation of design changes are slow, and deployment of the product is slow also.
If you don't know where you're going it doesn't matter how fast you get there
The best-performing organizations have the highest quality, throughput, and reliability while also delivering value. They are able to achieve this by focusing on a few key measurement principles, which Nicole and Jez will outline in this talk. These include knowing your outcome measuring it, capturing metrics in tension, and collecting complementary measures… along with a few others. Nicole and Jez explain the importance of knowing how (and what) to measure—ensuring you catch successes and failures when they first show up, not just when they’re epic, so you can course correct rapidly. Measuring progress lets you focus on what’s important and helps you communicate this progress to peers, leaders, and stakeholders, and arms you for important conversations around targets such as SLOs. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to be great SREs and move performance in the right direction.
Continuous Testing: Preparing for DevOps
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.
Secrets and surprises of high performance: What the data says
This document summarizes the key findings from a presentation on high performing DevOps teams. It discusses that while technology itself may not matter, factors like frequent deployment, cooperation between dev and ops, culture and processes are important. Data shows high performing teams deploy code 46x more frequently and have much faster lead times. These teams also have much higher reliability and lower failure rates. Adopting DevOps practices correlates with better meeting organizational goals, higher customer satisfaction, and improved employee satisfaction. The document cautions against relying on maturity models and argues that architecture is more important than the specific technology stack. It advocates for using data and science to continuously improve practices to better the work experience.
How Do We Better Sell DevOps? - PuppetConf 2013
"How Do We Better Sell DevOps?" by Gene Kim, Author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win", IT Revolution Press.
Presentation Overview: In this talk, Gene shares his top lessons learned over my years studying high performing IT organizations on how to sell the value of DevOps, and help other stakeholders and executives have their own a-ha moments. He talks about specific stories about the circumstances that led to these a-ha moments, how they created DevOps champions in surprising places (e.g., Development, CTOs, Product Management, UX, Infosec) in organizations you'll recognize, and how they enabled implementing DevOps patterns that had awesome results.
Speaker Bio: Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Visible Ops Handbook” and “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win." Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list.
[Webinar] The Changing Role of Release Engineering in a DevOps World with J. ...
The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
Tools, Culture, and Aesthetics: The Art of DevOps
My DevOps Days Tel Aviv keynote: In this talk, we will examine why these now school-aged ideals remain so difficult to implement, explore why DevOps is often described as "the movement that refuses to identify itself," and what your team can do to confront the dichotomies they are likely to face as they transform how they, their colleagues, and their company go about their daily work.
Soft Skills You Need Are Not Always Taught in Class
For years in the software industry, the focus of discussion, programs, and expense has been on career skill development to enhance team performance. To support skill development, a variety of certifications and training opportunities have been created to increase technical knowledge acquisition. Gaining technical knowledge is important, but this knowledge is often secondary to having other skills that are of more value to the organization. Jon Hagar explores these so-called “soft” skills—analysis, rational thought, communication, mentoring, technical debt management, reframing problems, modeling, time management, and social aptitude—and discusses the differences between knowledge from study and practiced skills. Delegates are asked to consider the value and to discuss how to develop and improve such skills. Finally, through an entertaining analogy Jon highlights the differences between skill and knowledge.
Keeping The Auditor Away: DevOps Audit Compliance Case Studies
GenOrganizations and development teams are moving beyond waterfall models to those embracing a continuous delivery/DevOps-style set of processes. The deployment of doing tens, hundreds, or even thousands of deploys per day as 'normal' does not align to the SDLC, separation of duties, and common controls expected by auditors.
In this presentation, we will describe what auditors look for in a compliance audit, how to develop alternate control procedures that fulfill those reporting requirements, how to avoid “red flags” that indicate inadequate controls, and real world case studies and reporting artifacts.
Gene Kim has been studying high performing IT organizations since 1999 and helped develop the SOX scoping guidelines with the Institute of Internal Auditors in 2005. James DeLuccia IV is the leader for the Ernst & Young Americas Certification Services, James oversees all of the audits against common industry standards, and champions several global program implementation roll-outs. Developing and 'translating' the control environment behaviors of clients, such as Google, Amazon, Workday, and others is difficult. This discussion will bridge the needs of auditors with the community of developers by sharing examples, discussing the assurance expectations, and how to communicate to pass an audit.
DOES 2016 Sciencing the Crap Out of DevOps
Four years and over 20,000 respondents later, and we have learned a lot about what makes IT and organizational performance awesome. This year we include insights into security, containers, trunk-based development, and lean product management. Tune in for practical take-aways to make your teams' technology transformations even better.
The Data Behind DevOps: Becoming a High Performer
This document discusses high performance in technology organizations and the DevOps movement. It finds that technology organizations that are high performers are twice as likely to achieve goals like productivity and profitability. High performers have code deployments 46 times more frequent and lead time from commit to deploy is 440 times faster. They also recover from downtime 96 times faster. Achieving high performance requires a focus on technology, processes, and organizational culture together. Leadership is also important but not sufficient on its own. The document provides recommendations for accelerating improvement, including starting with architecture and approval processes.
Tool Tracking Solutions
The document discusses the importance of effective tool tracking solutions for bringing tooling projects in on time. It emphasizes that tracking documents should be self-explanatory, visually display key information without needing to search, and make it easy to determine project status and identify any delays. The document also stresses that the right people should be assigned to projects with the proper qualifications and experience to walk the process through predefined phases. Regular review meetings are recommended to ask questions, track open issues, and ensure projects progress as scheduled. Visual tracking solutions that clearly show project timelines and status are presented as an effective way to communicate progress.
Why Is Managing Software So Hard?
This presentation explores the reasons why software projects are significantly more difficult to manage than other types of projects. Software-specific issues related to scope, resources, and time are explored, as well as how software projects differ from other projects in the physical world. An argument for why software constitutes a “Wicked Problem” is expanded, and numerous software development myths are attacked with real-world anecdotes and solutions.
Agile bodensee - Agile Testing: Bug prevention vs. bug detection
The document discusses agile testing and bug prevention. It advocates for embedding testers within development teams to focus on prevention rather than detection of bugs. The ideal approach involves continuous testing parallel to development with the entire team involved in testing.
How Metrics Make Your DevOps Awesome
We all know the CAMS model of DevOps: Culture, Automation, Measurement, and Sharing… what if Measurement is the secret ingredient to awesome DevOps?
The most innovative organizations use metrics to measure the right things so they can make their DevOps awesome. You want to measure the right things, too - but where should you start? You need to know what you want to measure, what not to measure, and what to watch out for. Because the secret is that metrics shape your culture - and Nicole will show you how.
DevOps State of the Union 2015
Ernest Mueller, Karthik Gaekwad, and James Wickett, the Agile Admins (http://theagileadmin.com) delivered this presentation on what's hot in DevOps in 2015 for the BrightTALK Summit. The video is online at https://www.brighttalk.com/webcast/5742/154715
2019 Top Lessons Learned Since the Phoenix Project Was Released
This document summarizes key lessons from a presentation by Gene Kim on building a world-class engineering culture. Some of the main surprises discussed include: (1) the business value of DevOps is even higher than previously thought, (2) DevOps benefits operations and security as much as development, (3) measuring code deployment lead time is more important than deployments per day, and (4) Conway's Law has implications for organizational structure and architecture. The presentation also discusses how DevOps enables organizations to become dynamic learning organizations.
Test Estimation in Practice
Anyone who has ever attempted to estimate software testing effort realizes just how difficult the task can be. The number of factors that can affect the estimate is virtually unlimited. The key to good estimates is to understand the primary variables, compare them to known standards, and normalize the estimates based on their differences. This is easy to say but difficult to accomplish because estimates are frequently required even when very little is known about the project and what is known is constantly changing. Throw in a healthy dose of politics and a bit of wishful thinking and estimation can become a nightmare. Rob Sabourin provides a foundation for anyone who must estimate software testing work effort. Learn about the test team’s and tester’s roles in estimation and measurement, and how to estimate in the face of uncertainty. Analysts, developers, leads, test managers, testers, and QA personnel can all benefit from this tutorial.
Test Automation for Mobile Applications: A Practical Guide
The world of information technology is undergoing revolutionary changes. Advancements in mobile computing, fueled by mobile applications, are playing an important role in driving these changes. While developers build their technical skills to accommodate these evolving trends, it is equally important for testers to understand what it takes to test mobile applications. Testers must understand the scope of mobile device applications testing, whether automation is feasible, and what challenges will face the test team. Kunal Chauhan presents an optimized approach to testing smart devices, specifically focusing on mobile applications test automation, the various forms of applications (web, native, hybrid), and the tools available to assist in the automation process. Kunal demonstrates an automation framework using open source tools, providing a practical implementable solution to add to your mobile test automation toolkit.
More Related Content
What's hot
Successful writing at work copyright 2017 cengage learn
This document is the table of contents for a book about successful writing at work. It outlines the contents of the book, which covers topics such as identifying audiences, establishing purpose, adapting style and tone for different audiences, characteristics of job-related writing, writing ethically, the writing process of researching, planning, drafting, revising and editing, collaborative writing, and conducting effective meetings. The table of contents provides an overview of what is covered in each chapter to help readers understand what content is included in the book.
Lean Product Management User-Centered App Design
The document discusses lean product management and user-centered app design. It covers topics like doing just enough to provide early value to users, eliminating waste, engaging workforces with few meetings and continuous delivery, and learning just enough, designing just enough, and delivering just enough. The secrets to being a modern software organization are said to be speed to market, customer focus, and engaged workforce. Critical components of a successful product are described as being desirable, viable, and feasible.
The Key to High Performance - What the Data Says
Over the past five years, the State of DevOps Report has shown that high-performing IT teams decisively outperform their peers: they deploy 200x more frequently, with 2,555 faster lead times and 1/3 change fail rate. This year, we investigate architecture, experimentation in work, other business outcomes (e.g., for gov't). Come see the latest in what it takes to make software amazing.
Unbloat your SDLC
There are no two SDLC processes that are the same. Every company/project has their own specific SDLC process, however the only thing that most have in common is their bloat. The bloat is most evident in the time-to-market aspect of the project. Other evidence of this bloat is slow QA cycles, implementation of design changes are slow, and deployment of the product is slow also.
If you don't know where you're going it doesn't matter how fast you get there
The best-performing organizations have the highest quality, throughput, and reliability while also delivering value. They are able to achieve this by focusing on a few key measurement principles, which Nicole and Jez will outline in this talk. These include knowing your outcome measuring it, capturing metrics in tension, and collecting complementary measures… along with a few others. Nicole and Jez explain the importance of knowing how (and what) to measure—ensuring you catch successes and failures when they first show up, not just when they’re epic, so you can course correct rapidly. Measuring progress lets you focus on what’s important and helps you communicate this progress to peers, leaders, and stakeholders, and arms you for important conversations around targets such as SLOs. Great outcomes don’t realize themselves, after all, and having the right metrics gives us the data we need to be great SREs and move performance in the right direction.
Continuous Testing: Preparing for DevOps
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.
Secrets and surprises of high performance: What the data says
This document summarizes the key findings from a presentation on high performing DevOps teams. It discusses that while technology itself may not matter, factors like frequent deployment, cooperation between dev and ops, culture and processes are important. Data shows high performing teams deploy code 46x more frequently and have much faster lead times. These teams also have much higher reliability and lower failure rates. Adopting DevOps practices correlates with better meeting organizational goals, higher customer satisfaction, and improved employee satisfaction. The document cautions against relying on maturity models and argues that architecture is more important than the specific technology stack. It advocates for using data and science to continuously improve practices to better the work experience.
How Do We Better Sell DevOps? - PuppetConf 2013
"How Do We Better Sell DevOps?" by Gene Kim, Author of "The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win", IT Revolution Press.
Presentation Overview: In this talk, Gene shares his top lessons learned over my years studying high performing IT organizations on how to sell the value of DevOps, and help other stakeholders and executives have their own a-ha moments. He talks about specific stories about the circumstances that led to these a-ha moments, how they created DevOps champions in surprising places (e.g., Development, CTOs, Product Management, UX, Infosec) in organizations you'll recognize, and how they enabled implementing DevOps patterns that had awesome results.
Speaker Bio: Gene is a multiple award winning CTO, researcher and author. He was founder and CTO of Tripwire for 13 years. He has written three books, including “The Visible Ops Handbook” and “The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win." Gene is a huge fan of IT operations, and how it can enable developers to maximize throughput of features from “code complete” to “in production,” without causing chaos and disruption to the IT environment. He has worked with some of the top Internet companies on improving deployment flow and increasing the rigor around IT operational processes. In 2007, ComputerWorld added Gene to the “40 Innovative IT People Under The Age Of 40” list.
[Webinar] The Changing Role of Release Engineering in a DevOps World with J. ...
The rise of DevOps is revitalizing age-old topics in release engineering and application lifecycle management, and aspects of software delivery that DevOps doesn’t magically solve. If you're responsible for the release engineering function in your organization, see what the new world looks like and which aspects of the industry it’s leaving behind.
Tools, Culture, and Aesthetics: The Art of DevOps
My DevOps Days Tel Aviv keynote: In this talk, we will examine why these now school-aged ideals remain so difficult to implement, explore why DevOps is often described as "the movement that refuses to identify itself," and what your team can do to confront the dichotomies they are likely to face as they transform how they, their colleagues, and their company go about their daily work.
Soft Skills You Need Are Not Always Taught in Class
For years in the software industry, the focus of discussion, programs, and expense has been on career skill development to enhance team performance. To support skill development, a variety of certifications and training opportunities have been created to increase technical knowledge acquisition. Gaining technical knowledge is important, but this knowledge is often secondary to having other skills that are of more value to the organization. Jon Hagar explores these so-called “soft” skills—analysis, rational thought, communication, mentoring, technical debt management, reframing problems, modeling, time management, and social aptitude—and discusses the differences between knowledge from study and practiced skills. Delegates are asked to consider the value and to discuss how to develop and improve such skills. Finally, through an entertaining analogy Jon highlights the differences between skill and knowledge.
Keeping The Auditor Away: DevOps Audit Compliance Case Studies
GenOrganizations and development teams are moving beyond waterfall models to those embracing a continuous delivery/DevOps-style set of processes. The deployment of doing tens, hundreds, or even thousands of deploys per day as 'normal' does not align to the SDLC, separation of duties, and common controls expected by auditors.
In this presentation, we will describe what auditors look for in a compliance audit, how to develop alternate control procedures that fulfill those reporting requirements, how to avoid “red flags” that indicate inadequate controls, and real world case studies and reporting artifacts.
Gene Kim has been studying high performing IT organizations since 1999 and helped develop the SOX scoping guidelines with the Institute of Internal Auditors in 2005. James DeLuccia IV is the leader for the Ernst & Young Americas Certification Services, James oversees all of the audits against common industry standards, and champions several global program implementation roll-outs. Developing and 'translating' the control environment behaviors of clients, such as Google, Amazon, Workday, and others is difficult. This discussion will bridge the needs of auditors with the community of developers by sharing examples, discussing the assurance expectations, and how to communicate to pass an audit.
DOES 2016 Sciencing the Crap Out of DevOps
Four years and over 20,000 respondents later, and we have learned a lot about what makes IT and organizational performance awesome. This year we include insights into security, containers, trunk-based development, and lean product management. Tune in for practical take-aways to make your teams' technology transformations even better.
The Data Behind DevOps: Becoming a High Performer
This document discusses high performance in technology organizations and the DevOps movement. It finds that technology organizations that are high performers are twice as likely to achieve goals like productivity and profitability. High performers have code deployments 46 times more frequent and lead time from commit to deploy is 440 times faster. They also recover from downtime 96 times faster. Achieving high performance requires a focus on technology, processes, and organizational culture together. Leadership is also important but not sufficient on its own. The document provides recommendations for accelerating improvement, including starting with architecture and approval processes.
Tool Tracking Solutions
The document discusses the importance of effective tool tracking solutions for bringing tooling projects in on time. It emphasizes that tracking documents should be self-explanatory, visually display key information without needing to search, and make it easy to determine project status and identify any delays. The document also stresses that the right people should be assigned to projects with the proper qualifications and experience to walk the process through predefined phases. Regular review meetings are recommended to ask questions, track open issues, and ensure projects progress as scheduled. Visual tracking solutions that clearly show project timelines and status are presented as an effective way to communicate progress.
Why Is Managing Software So Hard?
This presentation explores the reasons why software projects are significantly more difficult to manage than other types of projects. Software-specific issues related to scope, resources, and time are explored, as well as how software projects differ from other projects in the physical world. An argument for why software constitutes a “Wicked Problem” is expanded, and numerous software development myths are attacked with real-world anecdotes and solutions.
Agile bodensee - Agile Testing: Bug prevention vs. bug detection
The document discusses agile testing and bug prevention. It advocates for embedding testers within development teams to focus on prevention rather than detection of bugs. The ideal approach involves continuous testing parallel to development with the entire team involved in testing.
How Metrics Make Your DevOps Awesome
We all know the CAMS model of DevOps: Culture, Automation, Measurement, and Sharing… what if Measurement is the secret ingredient to awesome DevOps?
The most innovative organizations use metrics to measure the right things so they can make their DevOps awesome. You want to measure the right things, too - but where should you start? You need to know what you want to measure, what not to measure, and what to watch out for. Because the secret is that metrics shape your culture - and Nicole will show you how.
DevOps State of the Union 2015
Ernest Mueller, Karthik Gaekwad, and James Wickett, the Agile Admins (http://theagileadmin.com) delivered this presentation on what's hot in DevOps in 2015 for the BrightTALK Summit. The video is online at https://www.brighttalk.com/webcast/5742/154715
2019 Top Lessons Learned Since the Phoenix Project Was Released
This document summarizes key lessons from a presentation by Gene Kim on building a world-class engineering culture. Some of the main surprises discussed include: (1) the business value of DevOps is even higher than previously thought, (2) DevOps benefits operations and security as much as development, (3) measuring code deployment lead time is more important than deployments per day, and (4) Conway's Law has implications for organizational structure and architecture. The presentation also discusses how DevOps enables organizations to become dynamic learning organizations.
What's hot (20)
Successful writing at work copyright 2017 cengage learn
Successful writing at work copyright 2017 cengage learn
If you don't know where you're going it doesn't matter how fast you get there
If you don't know where you're going it doesn't matter how fast you get there
Secrets and surprises of high performance: What the data says
Secrets and surprises of high performance: What the data says
[Webinar] The Changing Role of Release Engineering in a DevOps World with J. ...
[Webinar] The Changing Role of Release Engineering in a DevOps World with J. ...
Soft Skills You Need Are Not Always Taught in Class
Soft Skills You Need Are Not Always Taught in Class
Keeping The Auditor Away: DevOps Audit Compliance Case Studies
Keeping The Auditor Away: DevOps Audit Compliance Case Studies
Agile bodensee - Agile Testing: Bug prevention vs. bug detection
Agile bodensee - Agile Testing: Bug prevention vs. bug detection
2019 Top Lessons Learned Since the Phoenix Project Was Released
2019 Top Lessons Learned Since the Phoenix Project Was Released
Viewers also liked
Test Estimation in Practice
Anyone who has ever attempted to estimate software testing effort realizes just how difficult the task can be. The number of factors that can affect the estimate is virtually unlimited. The key to good estimates is to understand the primary variables, compare them to known standards, and normalize the estimates based on their differences. This is easy to say but difficult to accomplish because estimates are frequently required even when very little is known about the project and what is known is constantly changing. Throw in a healthy dose of politics and a bit of wishful thinking and estimation can become a nightmare. Rob Sabourin provides a foundation for anyone who must estimate software testing work effort. Learn about the test team’s and tester’s roles in estimation and measurement, and how to estimate in the face of uncertainty. Analysts, developers, leads, test managers, testers, and QA personnel can all benefit from this tutorial.
Test Automation for Mobile Applications: A Practical Guide
The world of information technology is undergoing revolutionary changes. Advancements in mobile computing, fueled by mobile applications, are playing an important role in driving these changes. While developers build their technical skills to accommodate these evolving trends, it is equally important for testers to understand what it takes to test mobile applications. Testers must understand the scope of mobile device applications testing, whether automation is feasible, and what challenges will face the test team. Kunal Chauhan presents an optimized approach to testing smart devices, specifically focusing on mobile applications test automation, the various forms of applications (web, native, hybrid), and the tools available to assist in the automation process. Kunal demonstrates an automation framework using open source tools, providing a practical implementable solution to add to your mobile test automation toolkit.
A Funny Thing Happened on the Way to User Acceptance Testing
Randy Rice presented on lessons learned from user acceptance testing (UAT) on four different projects. The first project involved a new laboratory testing system that had severe performance issues and required three redeployments. The second project with the same company was more successful due to improved testing practices. The third project involved designing many tests based on business scenarios before knowing the user interface. The last project involved a complex legal system where system testing found most defects and UAT was limited due to user capabilities. Key lessons included not relying solely on UAT, having contingency plans, and flexibility in testing plans.
Application Performance Testing: A Simplified Universal Approach
Scott Barber presented on approaches for performance testing throughout the software development lifecycle. He advocated for taking a preventative approach through continuous collaboration between developers and testers from the start of a project. This includes activities like code profiling, load testing components, and establishing performance goals at each stage with a focus on catching issues early.
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and More
Large-scale and complex testing projects can stress the testing and automation practices we have learned through the years, resulting in less than optimal outcomes. However, a number of innovative ideas and concepts are emerging to better support industrial-strength testing for big projects. Hans Buwalda shares his experiences and strategies he's developed for organizing and managing testing on large projects. Learn how to design tests specifically for automation, including how to incorporate keyword testing and other techniques. Learn what roles virtualization and the cloud can play, and the potential pitfalls of such options. Take away tips and tricks to make automation more stable, and to deal with the numerous versions and configurations common in large projects. Hans also describes the main challenges with global teams including time zones and cultural differences, and offers seven common problem "patterns," and what you can do to address them.
Getting Started with Risk-based Testing
Whether you are new to testing or looking for a better way to organize your test practices and processes, the Systematic Test and Evaluation Process (STEP™) offers a flexible approach to help you and your team succeed. Dale Perry describes this risk-based framework—applicable to any development lifecycle model—to help you make critical testing decisions earlier and with more confidence. The STEP™ approach helps you decide how to focus your testing effort, what elements and areas to test, and how to organize test designs and documentation. Learn the fundamentals of test analysis and how to develop an inventory of test objectives to help prioritize your testing efforts. Discover how to translate these objectives into a concrete strategy for designing and developing tests. With a prioritized inventory and focused test architecture, you will be able to create test cases, execute the resulting tests, and accurately report on the quality of your application and the effectiveness of your testing. Take back a proven approach to organize your testing efforts and new ways to add more value to your project and organization.
Testing with Limited, Vague, and Missing Requirements
Requirements are essential for the success of projects―or are they? As testers, we often demand concrete requirements, specified and documented in minute detail. However, does the business really know what they want early in the project? Can they actually produce such a document? Is it acceptable to test with limited or vague requirements? Lloyd Roden challenges your most basic beliefs, explaining how detailed requirements can damage and hinder the progress of testing. Lloyd provides example applications that have no requirements, vague requirements, evolving requirements, complex requirements, and detailed requirements. You will assess and test each of these examples in turn and will establish what is the best approach in these situations and for what reasons. Learn how to question applications and provide feedback on their quality using your experience and appropriate techniques regardless of the level of detail provided in the requirements.
Test Process Improvement in Agile
Jeroen Mengerink presented on test process improvement in Agile environments. He discussed how current TPI models focus on testing and structure but may not apply well to Agile. He proposed maturity levels for Agile testing - forming, norming, and performing. The presentation provided an assessment model to evaluate key areas like teamwork, test management, and regression testing. It offered examples and recommendations for improving processes in an Agile way, focusing on people, the development process, and testing flexibly.
Leveraging Open Source Automation: A Selenium WebDriver Example
The document summarizes a case study of a company that leveraged the open source Selenium WebDriver framework for test automation. It describes the company's needs, decision to use Selenium over a commercial tool, planning and design of the Selenium framework, implementation details, outcomes of increased test coverage and reduced execution time, and conclusions about using Selenium with proper planning.
Test Automation Patterns
When implementing test automation, many people encounter problems: where to start with automation, high maintenance costs for the automated tests, or unrealistic management expectations. The good news is that solutions to these problems exist and have been effectively used by many. A “pattern” is a general reusable solution to a commonly occurring problem. Patterns have been popular in software development for many years, but they are not commonly recognized in system-level test automation. Dorothy Graham shares a collection of common problems (issues) and their solutions (patterns) which she and others are now developing as a wiki. To help resolve typical issues, Dot gives you a brief guided tour of some patterns—from Maintainable Testware and Domain-Driven Testing to Fail Gracefully and Kill the Zombies. Dot helps you recognize test automation issues and shows you how to identify appropriate patterns to help solve them.
Security Testing for Testing Professionals
Today’s software applications are often security critical, making security testing an essential part of a software quality program. Unfortunately, most testers have not been taught how to effectively test the security of the software applications they validate. Join Jeff Payne as he shares what you need to know to integrate effective security testing into your everyday software testing activities. Learn how software vulnerabilities are introduced into code and exploited by hackers. Discover how to define and validate security requirements. Explore effective test techniques for assuring that common security features are tested. Learn about the most common security vulnerabilities and how to identify key security risks within applications, and use testing to mitigate them. Understand how to security test applications—both web- and GUI-based—during the software development process. Review examples of how common security testing tools work and assist the security testing process. Take home valuable tools and techniques for effectively testing the security of your applications going forward.
Principles Before Practices: Transform Your Testing by Understanding Key Conc...
It’s one thing to be exposed to new techniques from conferences and training courses, but it’s quite another thing to apply them in real life. A major reason is that people tend to focus on learning the technique without first grasping the underlying principles. Basic testing principles, such as the pesticide paradox of software defects and defect clustering, have been known for many years. Other principles, such as “Test automation is not automatic” and “Not every software failure is a defect,” are learned by experience. Once you grasp the principle, particular techniques become more applicable and extensible. However, principles take time to learn and much practice to apply well. Randy Rice explains why true learning and application are not instant and what it takes to really absorb what we learn. Randy shows how two specific techniques—pairwise testing and risk-based testing—can be misapplied unless the key concepts are first understood. Leave knowing how to build your own set of software testing principles that can be applied in many contexts
Techniques for Agile Performance Testing
The performance of your application affects your business more than you might think. Top engineering organizations think of performance as not just a nice-to-have feature but as a crucial feature of their product. Those organizations understand that performance has a direct impact on user experience and, ultimately, their bottom line. Unfortunately, most engineering teams do not regularly test the performance and scalability of their infrastructure. Jim Hirschauer shares the latest performance testing tools and insights into why your team should add performance testing to an agile development process. Learn how to evaluate performance and scalability with MultiMechanize, Bees with Machine Guns, and Google PageSpeed. Take back an understanding of how to automate performance testing and evaluate the impact it has on performance and on your business.
A Rapid Introduction to Rapid Software Testing
You're under tight time pressure and have barely enough information to proceed with testing. How do you test quickly and inexpensively, yet still produce informative, credible, and accountable results? Rapid Software Testing, adopted by context-driven testers worldwide, offers a field-proven answer to this all-too-common dilemma. In this one-day sampler of the approach, Michael Bolton introduces you to the skills and practice of Rapid Software Testing through stories, discussions, and "minds-on" exercises that simulate important aspects of real testing problems. The rapid approach isn't just testing with speed or a sense of urgency; it's mission-focused testing that eliminates unnecessary work, assures that the most important things get done, and constantly asks how testers can help speed up the successful completion of the project. Join Michael to learn how Rapid Testing focuses on both the mind set and skill set of the individual tester, using tight loops of exploration and critical thinking skills to help continuously re-optimize testing to match clients' needs and expectations.
Introducing Keyword-driven Test Automation
In both agile and traditional projects, keyword-driven testing—when done correctly—has proven to be a powerful way to attain a high level of automation. Many testing organizations use keyword-driven testing but aren't realizing the full benefits of scalability and maintainability that are essential to keep up with the demands of testing today's software. Hans Buwalda describes the keyword approach, and how you use it to can meet the very aggressive goal that he calls the "5 percent challenge"―automate 95 percent of your tests with no more than 5 percent of your total testing effort. Hans also discusses how the keyword approach relates to other automation techniques like scripting and data-driven testing, and in what way keywords can be used for specific situations like graphics, multimedia, and mobile. Use the information and the real-world examples that Hans presents to attain a very high level of maintainable automation with the lowest possible effort.
Testing Cloud Services: SaaS, PaaS, and IaaS
Cloud computing has changed the environment of testing. Its use is increasing for hosting business applications (SaaS) and testing (TaaS). Martin Pol and Jeroen Mengerink focus on SaaS, describing the relevant infrastructure and platform services (IaaS and PaaS). How do we test performance of the cloud itself? How do we make sure that the continuity of services is guaranteed? How do we cope with elasticity and the philosophy of bring-your-own-device (BYOD)? Martin and Jeroen discuss the risks that arise when implementing cloud computing―some traditional, but others completely new. Learn how to mitigate these risks with current, modified, and new test techniques. As testers, we must be involved earlier in the cloud selection process. Testers should help to create and evaluate selection criteria to minimize risk. In addition, testers should be involved in the project longer as testing in production is needed to determine if the Service Level Agreements are being met.
Viewers also liked (16)
Test Automation for Mobile Applications: A Practical Guide
Test Automation for Mobile Applications: A Practical Guide
A Funny Thing Happened on the Way to User Acceptance Testing
A Funny Thing Happened on the Way to User Acceptance Testing
Application Performance Testing: A Simplified Universal Approach
Application Performance Testing: A Simplified Universal Approach
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and More
The Challenges of BIG Testing: Automation, Virtualization, Outsourcing, and More
Testing with Limited, Vague, and Missing Requirements
Testing with Limited, Vague, and Missing Requirements
Leveraging Open Source Automation: A Selenium WebDriver Example
Leveraging Open Source Automation: A Selenium WebDriver Example
Principles Before Practices: Transform Your Testing by Understanding Key Conc...
Principles Before Practices: Transform Your Testing by Understanding Key Conc...
Similar to Creating a Better Testing Future: The World Is Changing and We Must Change With It
Creating a Better Testing Future: The World Is Changing and We Must Change Wi...
The IEEE 829 Test Documentation standard is thirty years old this year. Boris Beizer’s first book on software testing also turned thirty. Testing Computer Software, the best selling book on software testing, is twenty-five. During the last three decades, hardware platforms have evolved from mainframes to minis to desktops to laptops to tablets to smartphones. Development paradigms have shifted from waterfall to agile. Consumers expect more functionality, demand higher quality, and are less loyal to brands. The world has changed dramatically and testing must change to match it. Testing processes that helped us succeed in the past may prevent our success in the future. Lee Copeland shares his insights into the future of testing, sharing his Do’s and Don’ts in the areas of technology, organization, test processes, test plans, and automation. Join Lee for a thought provoking look at creating a better testing future.
Data-Driven Software Testing: The New, Lean Approach to Quality
The Internet of Things and always connected devices are generating exabytes of user data and device telemetry. Organizations worldwide are leveraging this data for new products and new business insights, but this data is also fundamentally changing how organizations drive, assess, and improve product quality. Testers have traditionally relied on test results, but, with additional data sources now available to testers, the testers’ ability to process these is expanding like never before. Data-driven quality (DDQ) strategies such as Testing in Production (TiP) are essential tools for most testers. But the questions are: How do you implement these strategies to benefit your specific product? How do you convert testers into data scientists? How do A/B testing, continuous delivery, and creating products from service components drive us to a leaner and better approach to quality? Ken Johnston answers these questions and more in this insightful session.
141015 Discovering Scrum at Scrum Roma
A workshop on discovering what makes for great project, how scrum enables great projects, and a look at what will change when you do scrum
They Said, We Said: Bridge the Communication Gap with Behavior-Driven Develop...
The document describes a presentation by Sheetal Patel of The Vanguard Group on using Behavior-Driven Development (BDD) to improve communication between business and development teams. BDD uses examples in plain language to formalize requirements and validate software behavior. The Vanguard used BDD and Cucumber to engage business, development, and testing in collaborative sessions to define stories and test scenarios upfront. This helped address miscommunications over software features and reduced unused features from 64% to a lower percentage.
AgileMidwest2018-Erickson-PowerOfRetrospective
This document provides examples of retrospective techniques that can be used to keep team retrospectives fresh and relevant. It discusses how retrospectives are important for the inspect and adapt process in Agile but that teams say "I hate retrospectives" when the format does not vary. It then provides descriptions and instructions for several retrospective techniques including The White Elephant, Seven Questions, Two Truths and a Lie, Clear the Air, and Recognizing Group Knowledge. The document emphasizes choosing retrospective techniques appropriate for the team and situation and respecting the team's time.
ATC2013-Thiru and Abhishek-How to prevent Agile from becoming Fragile?
ATC2013-Thiru and Abhishek-How to prevent Agile from becoming Fragile?India Scrum Enthusiasts Community
The document discusses how to prevent agile from becoming fragile. It identifies some common reasons why agile can become fragile such as lack of effective risk management and not extending agile practices to testing and deployment phases. It recommends using risk burn down charts throughout the project lifecycle, adopting automation best practices during testing and deployment, and maintaining interrupts in a separate "ops backlog" to prevent agile from becoming fragile.How to Pitch a Software Development Initiative and Ignite Culture Change
You’ve got a great idea for transforming software development or IT processes in your organization, but you’re not sure how to get buy-in from key stakeholders, or how to change your company culture.
In this session, Microsoft MVP Ike Ellis will draw on his experience as a consultant and leader in software development to give you real-world tips to define, shape, and share your pitch successfully. Whether you are launching a revolutionary new initiative or expanding an existing effort to improve your software development, Ike’s tips will help you create a plan to effect change in your teams.
What is Continuous Delivery really?
Slides from the first Austin Continuous Delivery meetup: http://www.meetup.com/Austin-Continuous-Delivery-Meetup/events/218743628/
Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...
This document discusses agile software development and is presented by Eric Wu, co-founder of Bracket Labs. It outlines some of the key problems with traditional waterfall software development processes, such as unpredictable requirements and costs. It then introduces agile development principles from the Agile Manifesto, including an emphasis on working software, customer collaboration, and responding to change. Finally, it provides an example of an agile process incorporating sprints, demonstrations, retrospectives and stand-up meetings, and notes how agile practices have evolved and expanded beyond just software development over the past 10 years.
Brownfields agile draft v11
The document discusses software development from a systems perspective using the Cynefin framework. It describes different types of software development including greenfield development for new capabilities, and brownfield development which involves ongoing maintenance and enhancements to existing systems. The complexity of software development increases from simple to complicated to complex to chaotic domains. Different practices are needed depending on the domain, and success in one domain does not guarantee success in another. Requirements also increase in complexity from linear structures in complicated domains to fractal structures in chaotic domains.
Tom Gilb - Power to the Programmers @ I T.A.K.E. Unconference 2014, Bucharest
Tom Gilb, an independent teacher, consultant and writer.
He was a keynote speaker at I T.A.K.E. Unconference 2014 (http://2014.itakeunconf.com/)
He talked about:
- architecture than can be made better by developers
- how one can get quality by designing it in, not by debugging it
- that engineering is defined by multidimensional problem solving.
www.mozaicworks.com
How do we fix testing
Perhaps in no other professional field is the dichotomy between theory and practice more starkly different than in the realm of software testing. Researchers and thought leaders claim that testing requires a high level of cognitive and interpersonal skills, in order to make judgments about the ability of software to fulfill its operational goals. In their minds, testing is about assessing and communicating the risks involved in deploying software in a specific state.
However, in many organizations, testing remains a necessary evil, and a cost to drive down as much as possible. Testing is merely a measure of conformance to requirements, without regard to the quality of requirements or how conformance is measured. This is certainly an important measure, but tells an incomplete story about the value of software in support of our business goals.
We as testers often help to perpetuate the status quo. Although in many cases we realize we can add far more value than we do, we continue to perform testing in a manner that reduces our value in the software development process.
This presentation looks at the state of the art as well of the state of common practice, and attempts to provide a rationale and roadmap whereby the practice of testing can be made more exciting and stimulating to the testing professional, as well as more valuable to the product and the organization.
[HCMC STC Jan 2015] Creating a Better Testing Future
Ho Chi Minh City Software Testing Conference January 2015
Software Testing in the Agile World
Website: www.hcmc-stc.org
Author: Lee Copeland
The IEEE 829 Test Documentation standard is thirty years old this year. Boris Beizer’s first book on software testing also turned thirty. Testing Computer Software, the best selling book on software testing, is twenty-five. During the last three decades, hardware platforms have evolved from mainframes to minis to desktops to laptops to tablets to smartphones. Development paradigms have shifted from waterfall to agile. Consumers expect more functionality, demand higher quality, and are less loyal to brands. The world has changed dramatically and testing must change to match it. Testing processes that helped us succeed in the past may prevent our success in the future. Lee Copeland shares his insights into the future of testing, sharing his Do’s and Don’ts in the areas of technology, organization, test processes, test plans, and automation. Join Lee for a thought provoking look at creating a better testing future.
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...
This document provides an overview of applying agile project management practices to hardware and systems development. It begins with biographies of the authors and case studies where agile methods improved software development. It then discusses challenges applying agile to hardware with long lead times. Key practices discussed include using short intervals with feedback, translating user stories and burn-downs to hardware, and managing projects with boundary conditions and out of bounds processes. The document provides examples and outlines adapting scrum practices like sprints, planning and retrospectives for hardware development.
A Brave New World of Delivering IT
Slides from the presentation "A Brave New World of Delivering IT – what Devops and Continuous Delivery really means to the business" by Andrew Phillips at the Unicom DevOps Summit: DevOps for Business Value.
See http://www.devopssummit.com/london-june-2015/
Software Testing’s Future—According to Lee Copeland
The original IEEE 829 Test Documentation standard is thirty years old this year. Boris Beizer’s first book on software testing, Software Testing Techniques, also passed thirty. Testing Computer Software, the best-selling book on software testing, is more than twenty five. During the past three decades, hardware platforms have evolved from mainframes to minis to desktops to laptops to smartphones to tablets. Development paradigms have shifted from waterfall to agile. Consumers expect more functionality, demand higher quality, and are less loyal to brands. The world has changed dramatically—and testing must change to match it. Testing processes that helped us succeed in the past may prevent our success in the future. Lee Copeland shares his insights into the future of testing, including his views in the areas of technology, organization, test processes, test plans, and automation. Join Lee for a thought-provoking look at creating a better testing future.
Culture, Processes and Tools of Continuous Delivery
Slides from the presentation "Three Pillars of Continuous Delivery: Culture, Processes and Tools" at the CD Summits London and Paris 2014. http://www.cloudbees.com/cdsummit/london
Moving to Continuous Delivery without breaking everything
This document discusses the need for continuous delivery and integration of testing into software development pipelines. It notes that while pipelines focus on speed of delivery, testing is needed to ensure quality and avoid breaking changes. A central hub is needed to provide a single view of all test results from different sources to help determine if a release is ready. Intelligent test selection and optimization could help run relevant test subsets to improve feedback speed while maintaining coverage. An integrated test analysis tool can help address these challenges of continuous delivery.
Chicago CD Summit: 3 Pillars of Continuous Delivery
The document discusses the three pillars of continuous delivery culture, processes, and tools. It argues that culture is best bootstrapped by starting with tooling and processes to achieve quick wins, rather than trying to change culture directly. This helps build momentum for continuous delivery efforts. The presentation provides examples of tools and processes for continuous delivery and emphasizes the importance of communication to fully embed these changes into an organization's culture over time.
SFBA Splunk Usergroup meeting March 13, 2024
SFBA Splunk Usergroup meeting March 13, 2024: Two talks: Speed Scale and Simplicity; Splunk Admin Lessons Learned
Similar to Creating a Better Testing Future: The World Is Changing and We Must Change With It (20)
Creating a Better Testing Future: The World Is Changing and We Must Change Wi...
Creating a Better Testing Future: The World Is Changing and We Must Change Wi...
Data-Driven Software Testing: The New, Lean Approach to Quality
Data-Driven Software Testing: The New, Lean Approach to Quality
They Said, We Said: Bridge the Communication Gap with Behavior-Driven Develop...
They Said, We Said: Bridge the Communication Gap with Behavior-Driven Develop...
ATC2013-Thiru and Abhishek-How to prevent Agile from becoming Fragile?
ATC2013-Thiru and Abhishek-How to prevent Agile from becoming Fragile?
How to Pitch a Software Development Initiative and Ignite Culture Change
How to Pitch a Software Development Initiative and Ignite Culture Change
Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...
Introduction to Agile Software Development - Eric Wu - MBAX6360 New Product D...
Tom Gilb - Power to the Programmers @ I T.A.K.E. Unconference 2014, Bucharest
Tom Gilb - Power to the Programmers @ I T.A.K.E. Unconference 2014, Bucharest
[HCMC STC Jan 2015] Creating a Better Testing Future
[HCMC STC Jan 2015] Creating a Better Testing Future
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...
Agile Project Management in a Waterfall World: Managing Sprints with Predicti...
Software Testing’s Future—According to Lee Copeland
Software Testing’s Future—According to Lee Copeland
Culture, Processes and Tools of Continuous Delivery
Culture, Processes and Tools of Continuous Delivery
Moving to Continuous Delivery without breaking everything
Moving to Continuous Delivery without breaking everything
Chicago CD Summit: 3 Pillars of Continuous Delivery
Chicago CD Summit: 3 Pillars of Continuous Delivery
More from TechWell
Failing and Recovering
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
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 Architecture
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 Start
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 Strategy
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 Success
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.
Implement BDD with Cucumber and SpecFlow
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 Sanity
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.
Ma 15
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 Strategy
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 DevOps
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—Leadership
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 Teams
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 Game
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 Teams
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 Implementation
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 Process
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 Automate
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 Success
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 Transformation
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.
More from TechWell (20)
Instill a DevOps Testing Culture in Your Team and Organization
Instill a DevOps Testing Culture in Your Team and Organization
Test Design for Fully Automated Build Architecture
Test Design for Fully Automated Build Architecture
System-Level Test Automation: Ensuring a Good Start
System-Level Test Automation: Ensuring a Good Start
Testing Transformation: The Art and Science for Success
Testing Transformation: The Art and Science for Success
Develop WebDriver Automated Tests—and Keep Your Sanity
Develop WebDriver Automated Tests—and Keep Your Sanity
Eliminate Cloud Waste with a Holistic DevOps Strategy
Eliminate Cloud Waste with a Holistic DevOps Strategy
Transform Test Organizations for the New World of DevOps
Transform Test Organizations for the New World of DevOps
The Fourth Constraint in Project Delivery—Leadership
The Fourth Constraint in Project Delivery—Leadership
Resolve the Contradiction of Specialists within Agile Teams
Resolve the Contradiction of Specialists within Agile Teams
Pin the Tail on the Metric: A Field-Tested Agile Game
Pin the Tail on the Metric: A Field-Tested Agile Game
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
Agile Performance Holarchy (APH)—A Model for Scaling Agile Teams
A Business-First Approach to DevOps Implementation
A Business-First Approach to DevOps Implementation
Databases in a Continuous Integration/Delivery Process
Databases in a Continuous Integration/Delivery Process
Turn the Lights On: A Power Utility Company's Agile Transformation
Turn the Lights On: A Power Utility Company's Agile Transformation
Recently uploaded
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Dmitrii Kamaev, PhD
Senior Product Owner - QIAGEN
Principle of conventional tomography-Bibash Shahi ppt..pptx
before the computed tomography, it had been widely used.
GNSS spoofing via SDR (Criptored Talks 2024)
In the realm of cybersecurity, offensive security practices act as a critical shield. By simulating real-world attacks in a controlled environment, these techniques expose vulnerabilities before malicious actors can exploit them. This proactive approach allows manufacturers to identify and fix weaknesses, significantly enhancing system security.
This presentation delves into the development of a system designed to mimic Galileo's Open Service signal using software-defined radio (SDR) technology. We'll begin with a foundational overview of both Global Navigation Satellite Systems (GNSS) and the intricacies of digital signal processing.
The presentation culminates in a live demonstration. We'll showcase the manipulation of Galileo's Open Service pilot signal, simulating an attack on various software and hardware systems. This practical demonstration serves to highlight the potential consequences of unaddressed vulnerabilities, emphasizing the importance of offensive security practices in safeguarding critical infrastructure.
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Inconsistent user experience and siloed data, high costs, and changing customer expectations – Citizens Bank was experiencing these challenges while it was attempting to deliver a superior digital banking experience for its clients. Its core banking applications run on the mainframe and Citizens was using legacy utilities to get the critical mainframe data to feed customer-facing channels, like call centers, web, and mobile. Ultimately, this led to higher operating costs (MIPS), delayed response times, and longer time to market.
Ever-changing customer expectations demand more modern digital experiences, and the bank needed to find a solution that could provide real-time data to its customer channels with low latency and operating costs. Join this session to learn how Citizens is leveraging Precisely to replicate mainframe data to its customer channels and deliver on their “modern digital bank” experiences.
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays, June 2024 with Maria Copot 20
HCL Notes and Domino License Cost Reduction in the World of DLAU
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-and-domino-license-cost-reduction-in-the-world-of-dlau/
The introduction of DLAU and the CCB & CCX licensing model caused quite a stir in the HCL community. As a Notes and Domino customer, you may have faced challenges with unexpected user counts and license costs. You probably have questions on how this new licensing approach works and how to benefit from it. Most importantly, you likely have budget constraints and want to save money where possible. Don’t worry, we can help with all of this!
We’ll show you how to fix common misconfigurations that cause higher-than-expected user counts, and how to identify accounts which you can deactivate to save money. There are also frequent patterns that can cause unnecessary cost, like using a person document instead of a mail-in for shared mailboxes. We’ll provide examples and solutions for those as well. And naturally we’ll explain the new licensing model.
Join HCL Ambassador Marc Thomas in this webinar with a special guest appearance from Franz Walder. It will give you the tools and know-how to stay on top of what is going on with Domino licensing. You will be able lower your cost through an optimized configuration and keep it low going forward.
These topics will be covered
- Reducing license cost by finding and fixing misconfigurations and superfluous accounts
- How do CCB and CCX licenses really work?
- Understanding the DLAU tool and how to best utilize it
- Tips for common problem areas, like team mailboxes, functional/test users, etc
- Practical examples and best practices to implement right away
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/temporal-event-neural-networks-a-more-efficient-alternative-to-the-transformer-a-presentation-from-brainchip/
Chris Jones, Director of Product Management at BrainChip , presents the “Temporal Event Neural Networks: A More Efficient Alternative to the Transformer” tutorial at the May 2024 Embedded Vision Summit.
The expansion of AI services necessitates enhanced computational capabilities on edge devices. Temporal Event Neural Networks (TENNs), developed by BrainChip, represent a novel and highly efficient state-space network. TENNs demonstrate exceptional proficiency in handling multi-dimensional streaming data, facilitating advancements in object detection, action recognition, speech enhancement and language model/sequence generation. Through the utilization of polynomial-based continuous convolutions, TENNs streamline models, expedite training processes and significantly diminish memory requirements, achieving notable reductions of up to 50x in parameters and 5,000x in energy consumption compared to prevailing methodologies like transformers.
Integration with BrainChip’s Akida neuromorphic hardware IP further enhances TENNs’ capabilities, enabling the realization of highly capable, portable and passively cooled edge devices. This presentation delves into the technical innovations underlying TENNs, presents real-world benchmarks, and elucidates how this cutting-edge approach is positioned to revolutionize edge AI across diverse applications.Mutation Testing for Task-Oriented Chatbots
Conversational agents, or chatbots, are increasingly used to access all sorts of services using natural language. While open-domain chatbots - like ChatGPT - can converse on any topic, task-oriented chatbots - the focus of this paper - are designed for specific tasks, like booking a flight, obtaining customer support, or setting an appointment. Like any other software, task-oriented chatbots need to be properly tested, usually by defining and executing test scenarios (i.e., sequences of user-chatbot interactions). However, there is currently a lack of methods to quantify the completeness and strength of such test scenarios, which can lead to low-quality tests, and hence to buggy chatbots.
To fill this gap, we propose adapting mutation testing (MuT) for task-oriented chatbots. To this end, we introduce a set of mutation operators that emulate faults in chatbot designs, an architecture that enables MuT on chatbots built using heterogeneous technologies, and a practical realisation as an Eclipse plugin. Moreover, we evaluate the applicability, effectiveness and efficiency of our approach on open-source chatbots, with promising results.
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...Edge AI and Vision Alliance
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/how-axelera-ai-uses-digital-compute-in-memory-to-deliver-fast-and-energy-efficient-computer-vision-a-presentation-from-axelera-ai/
Bram Verhoef, Head of Machine Learning at Axelera AI, presents the “How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-efficient Computer Vision” tutorial at the May 2024 Embedded Vision Summit.
As artificial intelligence inference transitions from cloud environments to edge locations, computer vision applications achieve heightened responsiveness, reliability and privacy. This migration, however, introduces the challenge of operating within the stringent confines of resource constraints typical at the edge, including small form factors, low energy budgets and diminished memory and computational capacities. Axelera AI addresses these challenges through an innovative approach of performing digital computations within memory itself. This technique facilitates the realization of high-performance, energy-efficient and cost-effective computer vision capabilities at the thin and thick edge, extending the frontier of what is achievable with current technologies.
In this presentation, Verhoef unveils his company’s pioneering chip technology and demonstrates its capacity to deliver exceptional frames-per-second performance across a range of standard computer vision networks typical of applications in security, surveillance and the industrial sector. This shows that advanced computer vision can be accessible and efficient, even at the very edge of our technological ecosystem.Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...Pitangent Analytics & Technology Solutions Pvt. Ltd
Discover top-tier mobile app development services, offering innovative solutions for iOS and Android. Enhance your business with custom, user-friendly mobile applications.Apps Break Data
How information systems are built or acquired puts information, which is what they should be about, in a secondary place. Our language adapted accordingly, and we no longer talk about information systems but applications. Applications evolved in a way to break data into diverse fragments, tightly coupled with applications and expensive to integrate. The result is technical debt, which is re-paid by taking even bigger "loans", resulting in an ever-increasing technical debt. Software engineering and procurement practices work in sync with market forces to maintain this trend. This talk demonstrates how natural this situation is. The question is: can something be done to reverse the trend?
June Patch Tuesday
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.
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Folding is a recent technique for building efficient recursive SNARKs. Several elegant folding protocols have been proposed, such as Nova, Supernova, Hypernova, Protostar, and others. However, all of them rely on an additively homomorphic commitment scheme based on discrete log, and are therefore not post-quantum secure. In this work we present LatticeFold, the first lattice-based folding protocol based on the Module SIS problem. This folding protocol naturally leads to an efficient recursive lattice-based SNARK and an efficient PCD scheme. LatticeFold supports folding low-degree relations, such as R1CS, as well as high-degree relations, such as CCS. The key challenge is to construct a secure folding protocol that works with the Ajtai commitment scheme. The difficulty, is ensuring that extracted witnesses are low norm through many rounds of folding. We present a novel technique using the sumcheck protocol to ensure that extracted witnesses are always low norm no matter how many rounds of folding are used. Our evaluation of the final proof system suggests that it is as performant as Hypernova, while providing post-quantum security.
Paper Link: https://eprint.iacr.org/2024/257
Monitoring and Managing Anomaly Detection on OpenShift.pdf
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.
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Join us to learn how UiPath Apps can directly and easily interact with prebuilt connectors via Integration Service--including Salesforce, ServiceNow, Open GenAI, and more.
The best part is you can achieve this without building a custom workflow! Say goodbye to the hassle of using separate automations to call APIs. By seamlessly integrating within App Studio, you can now easily streamline your workflow, while gaining direct access to our Connector Catalog of popular applications.
We’ll discuss and demo the benefits of UiPath Apps and connectors including:
Creating a compelling user experience for any software, without the limitations of APIs.
Accelerating the app creation process, saving time and effort
Enjoying high-performance CRUD (create, read, update, delete) operations, for
seamless data management.
Speakers:
Russell Alfeche, Technology Leader, RPA at qBotic and UiPath MVP
Charlie Greenberg, host
Leveraging the Graph for Clinical Trials and Standards
Katja Glaß
OpenStudyBuilder Community Manager - Katja Glaß Consulting
Marius Conjeaud
Principal Consultant - Neo4j
JavaLand 2024: Application Development Green Masterplan
My presentation slides I used at JavaLand 2024
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
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
Recently uploaded (20)
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Biomedical Knowledge Graphs for Data Scientists and Bioinformaticians
Principle of conventional tomography-Bibash Shahi ppt..pptx
Principle of conventional tomography-Bibash Shahi ppt..pptx
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
HCL Notes and Domino License Cost Reduction in the World of DLAU
HCL Notes and Domino License Cost Reduction in the World of DLAU
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
“Temporal Event Neural Networks: A More Efficient Alternative to the Transfor...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
9 CEO's who hit $100m ARR Share Their Top Growth Tactics Nathan Latka, Founde...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
“How Axelera AI Uses Digital Compute-in-memory to Deliver Fast and Energy-eff...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
Crafting Excellence: A Comprehensive Guide to iOS Mobile App Development Serv...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
zkStudyClub - LatticeFold: A Lattice-based Folding Scheme and its Application...
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Connector Corner: Seamlessly power UiPath Apps, GenAI with prebuilt connectors
Leveraging the Graph for Clinical Trials and Standards
Leveraging the Graph for Clinical Trials and Standards
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAU
Creating a Better Testing Future: The World Is Changing and We Must Change With It
- 2. Lee Copeland SQE With more than thirty years of experience as an information systems professional at commercial and nonprofit organizations, Lee Copeland has held technical and managerial positions in applications development, software testing, and software process improvement. Lee has developed and taught numerous training courses on software development and testing issues, and is a well-known speaker with Software Quality Engineering. Lee presents at software conferences in the United States and abroad. He is the author of the popular reference book, A Practitioner’s Guide to Software Test Design.
- 3. 2/11/2014 1 Creating a Better Testing Future Lee Copeland Testing Future The World Is Changing and Testing Must Change With It 1 Lee Copeland Software Quality Engineering lee@sqe.com Topics • Our World is Changingg g • The Curse of Past Successes • Lee’s Don’ts and Do’s for Future Success 2 2
- 4. 2/11/2014 2 Technology Is Changing Then Now 33 Now Customers Are Changing Expect more capability Less tolerant of low quality 44 Less loyal to brands
- 5. 2/11/2014 3 Business Is Changing 55 • In the past, organizations controlled external Communication is Changing p , g communication, both content and channels • Today, with the rise of Social Media … 66
- 6. 2/11/2014 4 Communication is Changing • Organizational structure controlled testerg communication, both content and channels • Today social media can connect testers world 77 • Today, social media can connect testers world- wide Development Process Is Changing hThen Now 88 Now
- 7. 2/11/2014 5 Development Process Is Changing • COBOL • CICS • VSAM • C++ • Java • HTML 4/5 Then 99 HTML 4/5 • JavaScript • XML • SQL • noSQL Now Testing Must Match Today’s Technology IEEE 829 Testing Standard 1983 1983 1987 1010
- 8. 2/11/2014 6 Testing Must Match Development 1111 Topics • Our World is Changingg g • The Curse of Past Successes • Lee’s Don’ts and Do’s for Future Success 1212
- 9. 2/11/2014 7 The Curse of Past Successes 1313 The Curse of Past Successes • Processes that made us successful in the past may prevent us from being successful in the future 1414
- 10. 2/11/2014 8 The Curse of Past Successes 1515 Camera Film The Curse of Past Successes 1616 Video Rental Stores
- 11. 2/11/2014 9 The Curse of Past Successes 1717 Newspapers The Curse of Past Successes 1818 Brick and Mortar Stores
- 12. 2/11/2014 10 The Curse of Past Successes 1919 Getting Bills in the Mail Topics • Our World is Changingg g • The Curse of Past Successes • Lee’s Don’ts and Do’s for Future Success 2020
- 13. 2/11/2014 11 The Don’ts and Do’s Focus Organization TestProcessAutomation 2121 TechnologyPlanning The Don’ts and Do’s Organization 2222
- 14. 2/11/2014 12 Organization • DON’T – Maintain teams of “developers” and “testers”, throwing products over the wall 2323 – This was supposed to foster “independence.” Instead, it created “us vs. them” and “huh?” Development Test Organization • DON’T – Establish Testing Centers of Excellence 2424 – “It’s where the disengaged gather to not produce” – David Hussman
- 15. 2/11/2014 13 Organization • DO – Integrate developers and testers together on the same team 2525 The Don’ts and Do’s Test Process 2626
- 16. 2/11/2014 14 Test Process • DON’T – Cling to a Waterfall style when your organization is moving toward Agile 2727 Test Process • DON’T – Try to test EVERYTHING 2828
- 17. 2/11/2014 15 Test Process • DON’T – Confuse Checking with Testing 2929 Michael Bolton Test Process • When we already believe something to be true,y g , we verify our belief by checking. Checking is a process of confirmation, verification, and validation • Checking is a highly automatable process 3030
- 18. 2/11/2014 16 Test Process • Testing is something that we do with theg g motivation of finding new information • It is a process of exploration, discovery, investigation, and learning • Testing is not automatable. It’s using our brain in real time, and it’s really fun 3131 Test Process • DO – Adopt a Customer-focused approach to testing 3232
- 19. 2/11/2014 17 Test Process • DO – Focus on “What Value Does Testing Add?” 3333 rather than “What Processes Does Testing Execute?” The Don’ts and Do’s Technology 3434
- 20. 2/11/2014 18 Technology • DON’T – Use Stone Age techniques, tools, and technologies 3535 Technology • DO – Embrace new technologies 3636
- 21. 2/11/2014 19 Technology • DO – Consider open source test tools 3737 The Don’ts and Do’s Planning 3838
- 22. 2/11/2014 20 Planning • DON’T – Adopt rigid, overly detailed plans – Restrict testing to explicit requirements 3939 – Remember: “No battle plan survives contact with the enemy” – Helmuth von Moltke Planning • DO – Create plans that Tell a story Present essential data Inspire and communicate 4040 Describe a reasoned plan of action
- 23. 2/11/2014 21 The Don’ts and Do’s Automation 4141 Automation • DON’T – Rely on Capture/Replay 4242
- 24. 2/11/2014 22 Automation • DON’T – Try to automate every test 4343 Automation • DON’T – Try to replace humans in testing 4444
- 25. 2/11/2014 23 Automation • DO – Use Test-driven Development 4545 Automation • DO – Use Acceptance Test-driven Development 4646
- 26. 2/11/2014 24 Automation • DO – Use Exploratory Testing “Simultaneous learning, test design, and test execution.” 4747 – James Bach Automation • DO – and Session-based Exploratory Test Management Perform Exploratory Testing in Sessions: Charter 4848 Timebox Reviewable result Debriefing Jon Bach
- 27. 2/11/2014 25 The Don’ts and Do’s Focus 4949 Focus on Prevention Over Finding • DO – Remember, while finding defects is important – We should be focused on defect prevention activities 5050
- 28. 2/11/2014 26 The Don’ts and Do’s Focus Organization TestProcessAutomation 5151 TechnologyPlanning Thanks for Attending Shameless commercial message lee@sqe.com 5252
- 29. 2/11/2014 27 My Thanks To • Dorothy Graham • David Hussman • Jonathan Kohl • Alon Linetzki • Dan North • Martin Pol For their ideas, review, and comments 5353 • Rob Sabourin • Alan Shalloway • Adrian Zwingli