In many cases, we choose solutions to problems without sufficient analysis of the underlying causes. This results in implementing a cover-up of the symptoms rather than a solution to the real underlying problem. When we do this, the problem is likely to resurface in one disguise or another, and we may mishandle it again—just as we did initially. Getting to the root of the problem is the better way to solve the current problem, and save time and money in the future. Alon Linetzki identifies and explains a number of root cause analysis techniques widely used in the industry, gives examples of how to apply them in software testing, demonstrates how to implement them, and discusses how to connect them to our day-to-day testing context. Alon shares how root cause analysis can be an effective tool in defect prevention.
How to Make Test Automation for Cloud-based SystemNick Babich
Automated Testing Best Practices and Tips. QA Automation and Test automation process flow. Continuous Delivery, Continuous integration and Test-driven development in cloud-based system. Automatic Deployment and Post-deployment verification. Agile development and quality assurance. Cloud-based telephony service.
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
How to Make Test Automation for Cloud-based SystemNick Babich
Automated Testing Best Practices and Tips. QA Automation and Test automation process flow. Continuous Delivery, Continuous integration and Test-driven development in cloud-based system. Automatic Deployment and Post-deployment verification. Agile development and quality assurance. Cloud-based telephony service.
In this session, we would discuss what "Agile Testing" is, what are the well known methods and models of Agile Testing and what to expect on the future of Agile Testing.
What are the Key drivers for automation? What are the Challenges in Agile automation and How to deal with them? How to automate? Who will automate? Which tool to select? Commercial or open source? What to automate? Which features? Here is what our experience says
This is chapter 1 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
QA Should be led from top down and implemented from bottom up. A presentation by Moti Demri, QA consultant and manager, experienced in building QA teams from the ground up, establishing market level standards (ISO 9000, CMMI) , processes, and testing methodologies for both manual and automated testing. Presented November 2013 to the JAX Chamber IT Council.
Software Process Models, The Linear Sequential Model, The Prototyping Model, The RAD Model, Evolutionary Process Models, Agile Process Model, Component-Based Development, Process, Product and Process.
Root Cause Analysis - Tools, Tips and Tricks to Get to the Bottom of Root CauseCraig Thornton
This webinar discusses and investigates how to conduct root cause analysis. Root cause analysis is something that companies really struggle with. There will be plenty of practical advice in the webinar to help with you understand the concepts and the tools.
If you would like to watch the recording of this webinar then copy and paste the below link into your web browser:
http://www.mangolive.com/blog-mango/root-cause-analysis-tools-webinar
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
With growing demands of customers, IT organizations need to structure their software testing processes and improve their general testing practices. Under the current dynamic conditions, testing activities are inevitably becoming more complex and compelling.
Ultimately, organizations are focusing on improving their technical abilities and infrastructure to stay competitive within their landscapes. They are seeking effective and powerful solutions to increase their operational efficiency, to reduce their testing costs, to minimize their delivery risks and to fulfill the high quality expectations.
Keytorc Testing Center of Excellence (K-TCoE) solution can be the most convenient and adaptive choice for boosting the product quality and enabling the testing services and capabilities of any IT organization. K-TCoE offers distinguished methods and streams for realizing cost savings, test process standardization, efficient resource usage and effective test governance. The solution will be addressing further numerous benefits and leverages on;
- Use of recent testing technology and tools,
- Balancing individual responsibilities and load,
- Process standardization and continuous improvement,
- High skilled test consultants and specialists,
- Business/Domain knowhow,
- Rotation Flexibility and faster ramp-up/ramp-down cycles,
- Client satisfaction with Service Level Agreement (SLA) based deliveries,
Müşterilerin artan talepleri, BT organizasyonlarının yazılım test süreçlerinin yapılandırılmasını ve sürekli iyileştirilmesini zorunlu kılmaktadır. Günümüz dinamik koşullarında yazılım test aktiviteleri, ileri seviyede karmaşık ve zorlayıcıdır.
Kurumlar alanlarında rekabetten uzak kalmamak adına, teknik yeterliliklerini ve altyapılarını geliştirmeye odaklanmaktadırlar. Etkin ve kalıcı çözümlere odaklanarak, operasyonel verimliliklerini arttırmaya, test maliyetlerini düşürmeye, risklerini azaltmaya ve müşterilerinin yüksek kalite beklentilerini karşılamaya çalışmaktadırlar.
Keytorc Testing Center of Excellence (K-TCoE), herhangi bir BT organizasyonu için, ürün kalitesini arttıran, yazılım test maliyetlerini düşüren, dışkaynak test hizmeti alımına olanak tanıyan en erişebilir ve uygulanabilir çözümdür. K-TCoE yaklaşımı ile standart test süreçleri, verimli kaynak kullanımı ve etkin test yönetimi mümkün olmaktadır.
K-TCoE çözümünün dayandığı temel unsurlar;
- Güncel test teknolojilerinin ve araçlarının kullanımı
- Bireysel sorumluluk ve yük dengelemesi
- Standartlaştırılmış test süreçleri ve sürekli gelişim
- Yüksek yetkinlikte test danışman ve uzmanları
- İş alanı bilgisi
- Rotasyon esnekliği
- Müşteri Memnuniyeti ve SLA odaklı teslimat
olarak sıralanabilir.
Let's explore what is agile testing, how agile testing is different than traditional testing. What practices team has to adopt to have parallel testing and how to create your own test automation framework. Test automation frameworks using cucumber, selenium, junit, nunit, rspec, coded UI etc.
What are the Key drivers for automation? What are the Challenges in Agile automation and How to deal with them? How to automate? Who will automate? Which tool to select? Commercial or open source? What to automate? Which features? Here is what our experience says
This is chapter 1 of ISTQB Advance Test Manager certification. This presentation helps aspirants understand and prepare the content of the certification.
Agile Testing: The Role Of The Agile TesterDeclan Whelan
This presentation provides an overview of the role of testers on agile teams.
In essence, the differences between testers and developers should blur so that focus is the whole team completing stories and delivering value.
Testers can add more value on agile teams by contributing earlier and moving from defect detection to defect prevention.
QA Should be led from top down and implemented from bottom up. A presentation by Moti Demri, QA consultant and manager, experienced in building QA teams from the ground up, establishing market level standards (ISO 9000, CMMI) , processes, and testing methodologies for both manual and automated testing. Presented November 2013 to the JAX Chamber IT Council.
Software Process Models, The Linear Sequential Model, The Prototyping Model, The RAD Model, Evolutionary Process Models, Agile Process Model, Component-Based Development, Process, Product and Process.
Root Cause Analysis - Tools, Tips and Tricks to Get to the Bottom of Root CauseCraig Thornton
This webinar discusses and investigates how to conduct root cause analysis. Root cause analysis is something that companies really struggle with. There will be plenty of practical advice in the webinar to help with you understand the concepts and the tools.
If you would like to watch the recording of this webinar then copy and paste the below link into your web browser:
http://www.mangolive.com/blog-mango/root-cause-analysis-tools-webinar
Agile Test Management Using Jira and ZephyrXBOSoft
Do you have traceability where you can efficiently determine the cause of defects if there was an unclear requirement? Are you sure your test cases cover your requirements? Can you easily execute targeted regression when you’ve updated your software’s functionality? Now with software development teams mostly working from home or in dispersed geographies, supporting effective collaboration between remote workers is critical. In this XBOSoft quarterly webinar, our CEO, Philip Lew, teams up with BDQ’s CEO Chris Bland, to discuss the problems with working remotely, integrating the phases of testing in development in an Agile, and how this can be done using Zephyr, one of the predominant plugins in the Atlassian marketplace for test management. In this webinar, you will learn how to:
--Link tests with user stories and group tests within test cycles.
--Tie your results (defects) all the way back to user stories for effective defect root cause analysis.
--Classify defects to analyze and prioritize your test efforts.
--Use the traceability matrix with Zephr for deep visibility into your Agile process.
With growing demands of customers, IT organizations need to structure their software testing processes and improve their general testing practices. Under the current dynamic conditions, testing activities are inevitably becoming more complex and compelling.
Ultimately, organizations are focusing on improving their technical abilities and infrastructure to stay competitive within their landscapes. They are seeking effective and powerful solutions to increase their operational efficiency, to reduce their testing costs, to minimize their delivery risks and to fulfill the high quality expectations.
Keytorc Testing Center of Excellence (K-TCoE) solution can be the most convenient and adaptive choice for boosting the product quality and enabling the testing services and capabilities of any IT organization. K-TCoE offers distinguished methods and streams for realizing cost savings, test process standardization, efficient resource usage and effective test governance. The solution will be addressing further numerous benefits and leverages on;
- Use of recent testing technology and tools,
- Balancing individual responsibilities and load,
- Process standardization and continuous improvement,
- High skilled test consultants and specialists,
- Business/Domain knowhow,
- Rotation Flexibility and faster ramp-up/ramp-down cycles,
- Client satisfaction with Service Level Agreement (SLA) based deliveries,
Müşterilerin artan talepleri, BT organizasyonlarının yazılım test süreçlerinin yapılandırılmasını ve sürekli iyileştirilmesini zorunlu kılmaktadır. Günümüz dinamik koşullarında yazılım test aktiviteleri, ileri seviyede karmaşık ve zorlayıcıdır.
Kurumlar alanlarında rekabetten uzak kalmamak adına, teknik yeterliliklerini ve altyapılarını geliştirmeye odaklanmaktadırlar. Etkin ve kalıcı çözümlere odaklanarak, operasyonel verimliliklerini arttırmaya, test maliyetlerini düşürmeye, risklerini azaltmaya ve müşterilerinin yüksek kalite beklentilerini karşılamaya çalışmaktadırlar.
Keytorc Testing Center of Excellence (K-TCoE), herhangi bir BT organizasyonu için, ürün kalitesini arttıran, yazılım test maliyetlerini düşüren, dışkaynak test hizmeti alımına olanak tanıyan en erişebilir ve uygulanabilir çözümdür. K-TCoE yaklaşımı ile standart test süreçleri, verimli kaynak kullanımı ve etkin test yönetimi mümkün olmaktadır.
K-TCoE çözümünün dayandığı temel unsurlar;
- Güncel test teknolojilerinin ve araçlarının kullanımı
- Bireysel sorumluluk ve yük dengelemesi
- Standartlaştırılmış test süreçleri ve sürekli gelişim
- Yüksek yetkinlikte test danışman ve uzmanları
- İş alanı bilgisi
- Rotasyon esnekliği
- Müşteri Memnuniyeti ve SLA odaklı teslimat
olarak sıralanabilir.
Let's explore what is agile testing, how agile testing is different than traditional testing. What practices team has to adopt to have parallel testing and how to create your own test automation framework. Test automation frameworks using cucumber, selenium, junit, nunit, rspec, coded UI etc.
Yin and Yang: Metrics within Agile and Traditional LifecyclesTechWell
Metrics are powerful tools when used to effect positive change in a project or organization. However, the value and benefits of metrics are often dependent on the context. While certain metrics provide information and insight to drive decision making for a traditional development approach, they may not be useful in an agile landscape—and vice versa. QA and agile experts Shaun Bradshaw and Bob Galen delve into the value, pitfalls, pros, and cons of various metrics in agile and waterfall development environments. Hear their experiences as they discuss and explore a variety of project-level, software development, and software testing metrics through the lens of both traditional and agile development contexts. Although Bob and Shaun respect each other’s knowledge and skill, they don’t often agree on metrics. And in this showdown, you’ll see why! Be prepared to learn, be entertained, and be ready to get in on the action as these two metrics titans go head-to-head.
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
How can root cause analysis assist a business in its growth?Kumar Satyam
The primary purpose of Root Cause Analysis is simple. Its to determine the underlying cause for any problem and to eliminate it. The process, however, is not quite simple. There are multiple tools and techniques along the road to analyzing a root cause.
Interested in Online Root Cause Analysis Training?: https://www.6sigma.us/product/root-cause-analysis-training-online/
Root Cause Analysis (RCA) Training – Three Day Course: https://www.6sigma.us/root-cause-analysis-methods/
Twelve Tips for Becoming a More Professional TesterTechWell
Many testers feel that their organizations do not treat them with the same level of professionalism and respect that their development peers receive. Testers attribute this to the fact that testing is a relatively “new” profession, that few universities grant a formal degree in software testing, and all sorts of other external factors—things beyond their control. But, to be perceived as professionals, we need to start by becoming more professional. Joel Montvelisky shares a number of things we can do to improve our professionalism while increasing the value of our work in our organizations. These simple yet important things include expanding our technical involvement in projects, increasing the interaction with our users and their representatives, leading the risk assessment process in our projects, and more. Joel reviews twelve specific points—practical tips you can start using right away to become a more professional tester.
Root cause analysis training for beginnersBryan Len
Root cause analysis training for beginners.For what reason Do You Need Root Cause Analysis Training?
On the off chance that you are associated with critical thinking, at any level, in your organization:
To begin with, you have to figure out how to get to the base of every issue to dispose of them forever.
You would likewise need to figure out how to build up a viable restorative activity design and preventive arrangement for every issue or occurrence keeping in mind the end goal to evade a similar issue from happening once more
Root Cause analysis training for beginners shows all of you the above in addition to gives you the chance to hone what you realized on genuine situations in class to guarantee you are prepared to backpedal and apply your insight and abilities at working environment.
Audience :
TONEX root cause analysis training for beginners is a 2-day course designed for:
Quality personnel
R&D team
Production engineers and managers
Design team
All the individuals whose job involve problem solving, safety, reliability, quality control, operations and logistics, and production
Root cause analysis training for beginners course covers the devices and methods to follow issues down to the root cause. Such "in reverse" looking system is helpful particularly in the conditions where there is in excess of one noteworthy cause related with an issue. Some of the time the numerous causes are autonomous of each other, while now and again they all connected together and consequently expelling one cause can bring about settling the entire issue. Root cause analysis training for beginners hands-on workshop will show you how to distinguish every one of the causes, find their association with each other, their consequences for the framework, expel them for all time, and set up preventive activities to keep away from them from happening again in future.
Learn more about Root cause analysis training for beginners
https://www.tonex.com/training-courses/root-cause-analysis-training-for-beginners/
A test strategy is the set of ideas that guides your test design. It's what explains why you test this instead of that, and why you test this way instead of that way. Strategic thinking matters because testers must make quick decisions about what needs testing right now and what can be left alone. You must be able to work through major threads without being overwhelmed by tiny details. James Bach describes how test strategy is organized around risk but is not defined before testing begins. Rather, it evolves alongside testing as we learn more about the product. We start with a vague idea of our strategy, organize it quickly, and document as needed in a concise way. In the end, the strategy can be as formal and detailed as you want it to be. In the beginning, though, we start small. If you want to focus on testing and not paperwork, this approach is for you.
How to Determine the Root Cause Analysis Techniques in a Management System?PECB
The understanding of these techniques and their effective implementation by the auditee (Process owner) in any Management system audit shall go along way to ensure that the problem does not recur and this improves the customer or stakeholder confidence, ensure safety of personnel and saves the organization money.
Main points covered:
• What is the Root Cause Analysis Technique?
• How to Ensure customers and stakeholder confidence
• Why is important to determine the Root Cause Analysis?
Presenter:
This webinar was presented by Eng. Isaac Mbuvi is an Electrical and communications Engineer. A holder of Master’s Degree in Occupational Safety and Health. He is an Environmental consultant, a certified trainer with PECB for ISO 9001, ISO 14001 and OHSAS 18001 Management systems. He is also a certified Lead Auditor in ISO 9001, ISO 14001 and OHSAS 18001.
He has worked in the Oil and Gas industry for the last 14 years and has built his career in the Management systems as an Lead Auditor, Auditor and auditee for more than seven years in various sectors such as Pipeline transport, Health, Construction, Marine, Energy, etc.
Link of the recorded webinar published on YouTube: https://youtu.be/DBljEiv9tAw
EuroSTAR Software Testing Conference 2009 presentation on The Power of Risk by Erik Beolen. See more at conferences.eurostarsoftwaretesting.com/past-presentations/
Lean Six Sigma Course Training Part 16Lean Insight
Here is the Lean Six Sigma Course Training Part 16, presented by Lean-insight.om
Are you looking for six sigma related courses in Bangalore, then consult lean-insight.com
Courses:
Six Sigma Training
Six Sigma Green Belt Training
Six Sigma Black Belt Training
Lean Six Sigma Training
For more details visit: http://lean-insight.com/six-sigma-training-bangalore/
Problem Solving Tools and Techniques by TQMIAndrew Leong
This handy guide is for anyone involved in problem solving and improvement activities. It contains guidelines on the use of many of the tools and techniques which can be used as part of a Continuous Improvement process.
Similar to Root Cause Analysis for Software Testers (20)
Do you ever feel you have lost confidence in your own abilities? Why does this happen? Isabel Evans spends a lot of time painting. Someone once commented, “Why are you doing this, when you are not very good at it?” And gradually she stopped drawing and painting, after being intimidated by a conventional vision of what good art should look like. At the same time, she experienced a parallel loss of confidence in her professional abilities. Attempting creative pursuits like drawing and painting is essential to cognitive, emotional, creative abilities and she began to understand the correlation between her creative activities and her confidence. Making errors, being wrong, failing – that is a generous gift we receive when we practice outside our skill level. By staying in a comfort zone and repeating successes, we stagnate. As Isabel started to create again she thought “I don’t feel good at it, I do feel good doing it” The difference was that she was learning, having ideas and the act of re-engaging with failure, together with the comradeship of friends and colleagues, including at Women Who Test, Isabel has regained her confidence in her professional abilities, and been able to reboot her career and joy. Join Isabel to share a journey from self-perceived failure, to recovery and renewed learning.
Instill a DevOps Testing Culture in Your Team and Organization TechWell
The DevOps movement is here. Companies across many industries are breaking down siloed IT departments and federating them into product development teams. Testing and its practices are at the heart of these changes. Traditionally, IT organizations have been staffed with mostly manual testers and a limited number of automation and performance engineers. To keep pace with development in the new “you build it, you own it” environment, testing teams and individuals must develop new technical skills and even embrace coding to stay relevant and add greater value to the business. DevOps really starts with testing. Join Adam Auerbach as he explains what DevOps is and how it relates to testing. He describes how testing must change from top to bottom and how to access your own environment to identify improvement opportunities. Adam dives into practices like service virtualization, test data management, and continuous testing so you can understand where you are now and identify steps needed to instill a DevOps testing culture in your team and organization.
Test Design for Fully Automated Build ArchitectureTechWell
Imagine this … As soon as any developed functionality is submitted into the code repository, it is automatically subjected to the appropriate battery of tests and then released straight into production. Setting up the pipeline capable of doing just that is becoming more and more common and something you need to know about. But most organizations hit the same stumbling block—just what IS the appropriate battery of tests? Automated build architectures don't always lend themselves well to the traditional stages of testing. In this hands-on tutorial, Melissa Benua introduces you to key test design principles—applicable to organizations both large and small—that allow you to take full advantage of the pipeline's capabilities without introducing unnecessary bottlenecks. Learn how to make highly reliable tests that run fast and preserve just enough information to let testers and developers determine exactly what went wrong and how to reproduce the error locally. Explore ways to reduce overlap while still maintaining adequate test coverage. Take back ideas about which test areas could benefit from being combined into a single suite and which areas could benefit most from being broken out altogether.
System-Level Test Automation: Ensuring a Good StartTechWell
Many organizations invest a lot of effort in test automation at the system level but then have serious problems later on. As a leader, how can you ensure that your new automation efforts will get off to a good start? What can you do to ensure that your automation work provides continuing value? This tutorial covers both “theory” and “practice”. Dot Graham explains the critical issues for getting a good start, and Chris Loder describes his experiences in getting good automation started at a number of companies. The tutorial covers the most important management issues you must address for test automation success, particularly when you are new to automation, and how to choose the best approaches for your organization—no matter which automation tools you use. Focusing on system level testing, Dot and Chris explain how automation affects staffing, who should be responsible for which automation tasks, how managers can best support automation efforts to promote success, what you can realistically expect in benefits and how to report them. They explain—for non-techies—the key technical issues that can make or break your automation effort. Come away with your own clarified automation objectives, and a draft test automation strategy to use to plan your own system-level test automation.
Build Your Mobile App Quality and Test StrategyTechWell
Let’s build a mobile app quality and testing strategy together. Whether you have a web, hybrid, or native app, building a quality and testing strategy means (1) knowing what data and tools you have available to make agile decisions, (2) understanding your customers and your competitors, and (3) testing your app under real-world conditions. Jason Arbon guides you through the latest techniques, data, and tools to ensure the awesomeness of your mobile app quality and testing strategy. Leave this interactive session with a strategy for your very own app—or one you pretend to own. The information Jason shares is based on data from Appdiff’s next-gen mobile app testing platform, lessons from Applause/uTest’s crowd, text mining hundreds of millions of app store reviews, and in-depth discussions with top mobile app development teams.
Testing Transformation: The Art and Science for SuccessTechWell
Technologies, testing processes, and the role of the tester have evolved significantly in the past few years with the advent of agile, DevOps, and other new technologies. It is critical that we testing professionals evaluate ourselves and continue to add tangible value to our organizations. In your work, are you focused on the trivial or on real game changers? Jennifer Bonine describes critical elements that help you artfully blend people, process, and technology to create a synergistic relationship that adds value. Jennifer shares ideas on mastering politics, maneuvering core vs. context, and innovating your technology strategies and processes. She explores how new processes can be introduced in an organization, what the role of organizational culture is in determining the success of a project, and how you can know what tools will add value vs. simply adding overhead and complexity. Jennifer reviews critically needed tester skills and discusses a continual learning model to evolve your skills and stay relevant. This discussion can lead you to technologies, processes, and skills you can stake your career on.
We’ve all been there. We work incredibly hard to develop a feature and design tests based on written requirements. We build a detailed test plan that aligns the tests with the software and the documented business needs. And when we put the tests to the software, it all falls apart because the requirements were changed without informing everyone. Mary Thorn says help is at hand. Enter behavior-driven development (BDD), and Cucumber and SpecFlow, tools for running automated acceptance tests and facilitating BDD. Mary explores the nuances of Cucumber and SpecFlow, and shows you how to implement BDD and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber and SpecFlow bridge the communication gap between business stakeholders and implementation teams. In this workshop, practice writing feature files with the best practices Mary has discovered over numerous implementations. If you experience developers not coding to requirements, testers not getting requirements updates, or customers who feel out of the loop and don’t get what they ask for, Mary has answers for you.
Develop WebDriver Automated Tests—and Keep Your SanityTechWell
Many teams go crazy because of brittle, high-maintenance automated test suites. Jim Holmes helps you understand how to create a flexible, maintainable, high-value suite of functional tests using Selenium WebDriver. Learn the basics of what to test, what not to test, and how to avoid overlapping with other types of testing. Jim includes both philosophical concepts and hands-on coding. Testers who haven't written code should not be intimidated! We'll pair you up to make sure you're successful. Learn to create practical tests dealing with advanced situations such as input validation, AJAX delays, and working with file downloads. Additionally, discover when you need to work together with developers to create a system that's more easily testable. This tutorial focuses primarily on automating web tests, but many of the same concepts can be applied to other UI environments. Demos and labs will be in C# and Java using WebDriver. Leave this tutorial having learned how to write high-value WebDriver tests—and stay sane while doing so.
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Eliminate Cloud Waste with a Holistic DevOps StrategyTechWell
Chris Parlette maintains that renting infrastructure on demand is the most disruptive trend in IT in decades. In 2016, enterprises spent $23B on public cloud IaaS services. By 2020, that figure is expected to reach $65B. The public cloud is now used like a utility, and like any utility, there is waste. Who's responsible for optimizing the infrastructure and reducing wasted expenses? It’s DevOps. The excess expense, known as cloud waste, comprises several interrelated problems: services running when they don't need to be, improperly sized infrastructure, orphaned resources, and shadow IT. There are a few core tenets of DevOps—holistic thinking, no silos, rapid useful feedback, and automation—that can be applied to reducing your cloud waste. Join Chris to learn why you should include continuous cost optimization in your DevOps processes. Automate cost control, reduce your cloud expenses, and make your life easier.
Transform Test Organizations for the New World of DevOpsTechWell
With the recent emergence of DevOps across the industry, testing organizations are being challenged to transform themselves significantly within a short period of time to stay meaningful within their organizations. It’s not easy to plan and approach these changes considering the way testing organizations have remained structured for ages. These challenges start from foundational organizational structures and can cut across leadership influence, competencies, tools strategy, infrastructure, and other dimensions. Sumit Kumar shares his experience assisting various organizations to overcome these challenges using an organized DevOps enablement framework. The framework includes radical restructuring, turning the tools strategy upside down, a multidimensional workforce enablement supported by infrastructure changes, redeveloped collaborations models, and more. From his real world experiences Sumit shares tips for approaching this journey and explains the roadmap for testing organizations to transform themselves to lead the quality in DevOps.
The Fourth Constraint in Project Delivery—LeadershipTechWell
All too often, the triple constraints—time, cost, and quality—are bandied about as if they are the be-all, end-all. While they are important, leadership—the fourth and larger underpinning constraint—influences the first three. Statistics on project success and failure abound, and these measurements are usually taken against the triple constraints. According to the Project Management Institute, only 53 percent of projects are completed within budget, and only 49 percent are completed on time. If so many projects overrun budget and are late, we can’t really say, “Good, fast, or cheap—pick two.” Rob Burkett talks about leadership at every level of a team. He shares his insights and stories gleaned from his years of IT and project management experience. Rob speaks to some of the glaring difficulties in the workplace in general and some specifically related to IT delivery and project management. Leave with a clearer understanding of how to communicate with teams and team members, and gain a better understanding of how you can be a leader—up and down your organization.
Resolve the Contradiction of Specialists within Agile TeamsTechWell
As teams grow, organizations often draw a distinction between feature teams, which deliver the visible business value to the user, and component teams, which manage shared work. Steve Berczuk says that this distinction can help organizations be more productive and scale effectively, but he recognizes that not all shared work fits into this model. Some work is best handled by “specialists,” that is people with unique skills. Although teams composed entirely of T-shaped people is ideal, certain skills are hard to come by and are used irregularly across an organization. Since these specialists often need to work closely with teams, rather than working from their own backlog, they don’t fit into the component team model. The use of shared resources presents challenges to the agile planning model. Steve Berczuk shares how teams such as those providing infrastructure services and specialists can fit into a feature+component team model, and how variations such as embedding specialists in a scrum team can both present process challenges and add significant value to both the team and the larger organization.
Pin the Tail on the Metric: A Field-Tested Agile GameTechWell
Metrics don’t have to be a necessary evil. If done right, metrics can help guide us to make better forward-looking decisions, rather than being used for simply managing or monitoring. They can help us identify trade-offs between options for what to do next versus punitive or worse, purely managerial measures. Steve Martin won’t be giving the Top Ten List of field-tested metrics you should use. Instead, in this interactive mini-workshop, he leads you through the critical thinking necessary for you to determine what is right for you to measure. First, Steve explores why you want to measure something—whether it’s for a team, a portfolio, or even an agile transformation. Next, he provides multiple real-life metrics examples to help drive home concepts behind characteristics of good and bad metrics. Finally, Steve shows how to run his field-tested agile game—Pin the Tail on the Metric. Take back this activity to help you guide metrics conversations at your organization.
Agile Performance Holarchy (APH)—A Model for Scaling Agile TeamsTechWell
A hierarchy is an organizational network that has a top and a bottom, and where position is determined by rank, importance, and value. A holarchy is a network that has no top or bottom and where each person’s value derives from his ability, rather than position. As more companies seek the benefits of agile, leaders need to build and sustain delivery capability while scaling agile without introducing unnecessary process and overhead. The Agile Performance Holarchy (APH) is an empirical model for scaling and sustaining agility while continuing to deliver great products. Jeff Dalton designed the APH by drawing from lessons learned observing and assessing hundreds of agile companies and teams. The APH helps implement a holarchy—a system composed of interacting organizational units called holons—centered on a series of performance circles that embody the behaviors of high performing agile organizations. Jeff describes how APH provides guidelines in the areas of leadership, values, teaming, visioning, governing, building, supporting, and engaging within an all-agile organization. Join Jeff to see what the APH is all about and how you can use it in your team and organization.
A Business-First Approach to DevOps ImplementationTechWell
DevOps is a cultural shift aimed at streamlining intergroup communication and improving operational efficiency for development and operations groups. Over time, inclusion of other IT groups under the DevOps umbrella has become the norm for many organizations. But even broadening the boundaries of DevOps, the conversation has been largely devoid of the business units’ place at the table. A common mistake organizations make while going through the DevOps transformation is drawing a line at the IT boundary. If that occurs, a larger, more inclusive silo within the organization is created, operating in an informational vacuum and causing operational inefficiency and goal misalignment. Sharing his experiences working on both sides of the fence, Leon Fayer describes the importance of including business units in order to align technology decisions with business goals. Leon discusses inclusion of business units in existing agile processes, benefits of cross-departmental monitoring, and a business-first approach to technology decisions.
Databases in a Continuous Integration/Delivery ProcessTechWell
DevOps is transforming software development with many organizations adopting lean development practices, implementing continuous integration (CI), and performing regular continuous deployment (CD) to their production environments. However, the database is largely ignored and often seen as a bottleneck in the DevOps process. Steve Jones discusses the challenges of database development and why many developers find the database to be an impediment to the CD process. Steve shares the techniques you can use to fit a database into the DevOps process. Learn how to store database code in a version control system, and the differences between that and application code. Steve demonstrates a CI process with SQL code and uses automated testing frameworks to check the code. Steve then shows how automated releases with manual gates can reduce the stress and risk of database deployments while ensuring consistent, reliable, repeatable releases to QA, UAT, and production.
Mobile Testing: What—and What Not—to AutomateTechWell
Organizations are moving rapidly into mobile technology, which has significantly increased the demand for testing of mobile applications. David Dangs says testers naturally are turning to automation to help ease the workload, increase potential test coverage, and improve testing efficiency. But should you try to automate all things mobile? Unfortunately, the answer is not always clear. Mobile has its own set of complications, compounded by a wide variety of devices and OS platforms. Join David to learn what mobile testing activities are ripe for automation—and those items best left to manual efforts. He describes the various considerations for automating each type of mobile application: mobile web, native app, and hybrid applications. David also covers device-level testing, types of testing, available automation tools, and recommendations for automation effectiveness. Finally, based on his years of mobile testing experience, David provides some tips and tricks to approach mobile automation. Leave with a clear plan for automating your mobile applications.
Cultural Intelligence: A Key Skill for SuccessTechWell
Diversity is becoming the norm in everyday life. However, introducing global delivery models without a proper understanding of intercultural differences can lead to difficulty, frustration, and reduced productivity. Priyanka Sharma and Thena Barry say that in our diverse world, we need teams with people who can cross these boundaries, communicate effectively, and build the diverse networks necessary to avoid problems. We need to learn about cultural intelligence (CI) and cultural quotient (CQ). CI is the ability to relate and work effectively across cultures. CQ is the cognitive, motivational, and behavioral capacity to understand and respond to beliefs, values, attitudes, and behaviors of individuals and groups. Together, CI and CQ can help us build behavioral capacities that aid motivation, behavior, and productivity in teams as well as individuals. Priyanka and Thena show how to build a more culturally intelligent place with tools and techniques from Leading with Cultural Intelligence, as well as content from the Hofstede cultural model. In addition, they illustrate the model with real-life experiences and demonstrate how they adapted in similar circumstances.
Turn the Lights On: A Power Utility Company's Agile TransformationTechWell
Why would a century-old utility with no direct competitors take on the challenge of transforming its entire IT application organization to an agile methodology? In an increasingly interconnected world, the expectations of customers continue to evolve. From smart meters to smart phones, IoT is creating a crisis point for industries not accustomed to rapid change. Glen Morris explains that pizzas can be tracked by the minute and packages at every stop, and customers now expect this same customer service model should exist for all industries—including power. Glen examines how to create momentum and transform non-IT-focused industries to an agile model. If you are struggling with gaining traction in your pursuit of agile within your business, Glen gives you concrete, practical experiences to leverage in your pursuit. Finally, he communicates how to gain buy-in from business partners who have no idea or concern about agile or its methodologies. If your business partners look at you with amusement when you mention the need for a dedicated Product Owner, join Glen as he walks you through the approaches to overcoming agile skepticism.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Encryption in Microsoft 365 - ExpertsLive Netherlands 2024Albert Hoitingh
In this session I delve into the encryption technology used in Microsoft 365 and Microsoft Purview. Including the concepts of Customer Key and Double Key Encryption.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...
Root Cause Analysis for Software Testers
1. TP
Half-day Tutorials
5/6/2014 1:00:00 PM
Root Cause Analysis for
Software Testers
Presented by:
Alon Linetzki
Best-Testing
Brought to you by:
340 Corporate Way, Suite 300, Orange Park, FL 32073
888-268-8770 ∙ 904-278-0524 ∙ sqeinfo@sqe.com ∙ www.sqe.com
2. Alon Linetzki
Best-Testing
Alon Linetzki, founder and managing director of Best-Testing, has been a coach and consultant in
development, testing, and quality assurance for twenty-eight years. Alon helps organizations
enhance the test engineer’s professional and personal skills, training test managers in optimization
and test process improvement, and optimizing their test operations. His main areas of expertise are
in agile testing and transitioning to agile, exploratory testing, test process Improvement, risk-based
testing, and test automation. Alon is a member of the ISTQB® authors and review team for the
ISTQB® Agile Tester Add-on certification, cofounder of ISTQB® in Israel, leader of the ISTQB®
Partner Program, and founder of the SIGiST Israel conference.
6. March 20144
Limit of responsibility
Best-Testing invests significant effort in updating this material, however, Best-Testing is not responsible of
any errors or material which may not meet specific requirements. The user alone is responsible for
decisions based on the information contained in this material.
Protected Trademark
In this material, protected trademarks appear that are under copyright. All rights to the trademarks in this
material are reserved to the authors.
Best–Testing wishes you success in the course!
Copyrights
8. 6
Alon Linetzki
30 years in IT, 20+ years as a test engineer and a test manager
Certified Scrum Master, Scrum Alliance, 2008
ISQTB® Partner Program leader, ISTQB® Agile Tester
Certification Leader
Specializes in Agile testing test strategy & optimization
test process improvement test management test design
risk based testing test automation Building Smart
Teams
A degree in ‘testing’ – B.Sc. statistics and criminology,
International Speaker worldwide, since 1995
Co-founder of the Israeli Testing Certification Board
(www.itcb.org.il, 2004)
Founder of the SIGiST Israel (testing forum) in Israel
(www.sigist.org.il, 2000)
9. We shall cover…
Introduction
Presenting participants and trainer
Workshop expectations
What is Root Cause Analysis?
How to use RCA for Defect analysis?
7
March 2014
10. We shall cover…
How to Use RCA for analyzing critical problems?
Cause Effect graphing, amended
Case Study #0
Summary
How to use RCA for process improvement?
Case Study #1
Case Study #2
Retrospective
Workshop retrospective
8
March 2014
(*) Bonus topic – only if there is enough time left…
11. Professional Background
Years experience in testing/development/both/other
Responsibilities in current role
Have you implemented RCA? Can you share?
Workshop expectations?
Introduce participants…
9
March 2014
12. Interactive sessions
Discussions, skepticism, curiosity
Examples, demonstration
Thinking, communicating
Keeping an open mind for ideas and concepts
Contribute to the class team
Learn…discuss…review…
Give quick feedback on everything you may think of
Time boxed sessions…breaks…exercises…discussions
Introducing workshop dynamics
10
March 2014
13. There are FAR more slides than we can
cover…
Say if you have something to say… do not
wait till the end of the workshop!
Introducing workshop dynamics
11
March 2014
14. Start : 10:15
Lunch: 11:45 – 12:45
Finish line: 14:15
But… we may have more
breaks if we feel like it…
Logistics…
March 2014
12
16. Root Cause Analysis definition
(My interpretation)
From wiki:
Root cause analysis (RCA) is a class of problem solving
methods aimed at identifying the root causes of problems
or events.
The practice of RCA is predicated on the belief that
problems are best solved by attempting to correct or
eliminate root causes, as opposed to merely addressing
the immediately obvious symptoms.
By directing corrective measures at root causes, it is
hoped that the likelihood of problem recurrence will be
minimized.
14
17. Root Cause Analysis definition
From Bill Willson’s website:
Root cause analysis (RCA) is a methodology for
finding and correcting the most important reasons
for performance problems.
It differs from troubleshooting and problem-solving
in that these disciplines typically seek solutions to
specific difficulties, whereas RCA is directed at
underlying issues
15
18. Root Cause Analysis - definition
Root cause analysis (RCA) is a methodology for finding
and correcting the most important reasons for
performance problems.
It differs from troubleshooting and problem-solving in
that these disciplines typically seek solutions to
specific difficulties, whereas RCA is directed at
underlying issues.
16
19. Root Cause Analysis definition -
summary
As a business process improvement tool, RCA seeks
out unnecessary constraints as well as inadequate
controls.
In safety and risk management, it looks for both
unrecognized hazards and broken or missing barriers.
It helps target CAPA (corrective action and preventive
action) efforts at the points of most leverage.
RCA is an essential ingredient in pointing
organizational change efforts in the right direction.
Finally, it is probably the only way to find the core
issues contributing to your toughest problems.
17
20. Root Cause Analysis
(My interpretation)
A problem solving method/process designed to search
for the root causes of a problem using a predefined
structural thinking process, identifying the underlying
issues, with the expectation that dealing with these
issues will dramatically reduce the likelihood of the
problem to occur.
The process involves data collection, cause charting, root
cause identification and recommendation generation
and implementation
18
21. “Cows falling on a road from a mountain”
– is it a problem or a symptom?
Should we eliminate all cows on
that area?
Should we dig-out the mountain?
Should we rotate the sign?
Should we divert the road
elsewhere?
It seems that sometimes
eliminating the causes is not an
easy task, and finding the problems
is even harder!
19
22. Root causes are underlying causes
The investigator’s goal should be to identify
specific underlying causes
The more specific the investigator can be about
why an event occurred, the easier it will be to
arrive at recommendations that will prevent
recurrence.
Practical RCA – definition guidelines
March 2014
20
23. Root causes are those that can reasonably be
identified
Occurrence investigations must be cost beneficial
It is not practical to keep valuable manpower
occupied indefinitely searching for the root
causes of occurrences…
Structured RCA helps analysts get the most out of
the time they have invested in the investigation.
Practical RCA – definition guidelines
March 2014
21
24. Root causes are those over which management has control
Analysts should avoid using general cause classifications such
as “operator error”, “equipment failure” or “external factor”
Such causes are not specific enough to allow management to
make effective changes
Management needs to know exactly why a failure occurred
before action can be taken to prevent recurrence
We must also identify a root cause that management can
influence:
Identifying “severe weather” as the root cause of parts not
being delivered on time to customers is not appropriate
Severe weather is not controlled by management.
Practical RCA – definition guidelines
March 2014
22
25. Root causes are those for which effective recommendations can
be generated (if cannot be done, keep on searching!)
Recommendations should directly address the root causes
identified during the investigation
If the analysts arrive at vague recommendations such as,
“Improve adherence to written policies and procedures,” then
they probably have not found a basic and specific enough
cause and need to expend more effort in the analysis process.
Practical RCA – definition guidelines
March 2014
23
26. Root causes are underlying causes
Root causes are those that can reasonably be
identified
Root causes are those over which
management has control
Root causes are those for which effective
recommendations can be generated (if
cannot be done, keep on searching!)
Practical RCA – definition guidelines
March 2014
24
28. Root Cause Analysis for Beginners - by James J. Rooney and Lee N. Vanden Heuvel
References – what is Root Cause Analysis?
26
March 2014
29. How to use RCA in Defect Analysis?
March 2014
27
30. Escaping defects occur all the time
We try to contain them, from going to production,
but much efforts should be done in preventing
them going from Design to Code
A set of questions may help out leading us to Data
Collection on those Defects for performing the
RCA – next page…
Defects RCA introduction
March 2014
28
31. Defects RCA guided questions
Data Collection
March 2014
29
Question Who
asks?
Describe circumstances and consequence of the
Problem?
Test Team
Where was the problem introduced? Dev Team
Describe the root cause of the problem Dev Team
What reviews were held for the phase? Dev Team
How and why did the problem escape testing? Test Team
What could be done to prevent this type of error in the
future?
Both
What could be done to find this type of problem in the
future?
Both
John Ruberto – Root Cause for Problems Escape
32. Defect Analysis is the process of analyzing a defect
to determine its root cause.
Defect Prevention is the process of addressing
root causes of defects to prevent their future
occurrence.
RCA – few definitions
March 2014
30
33. Defect Source – Finding defects in the stage they
were introduced and as early in the lifecycle as
possible – Eliminating escaping defects
RCA – few definitions
March 2014
31
35. Canceled Defects Root Cause Analysis
Cancelled defects are not real defects of the
system-under-test
They can be the result of: environment problem
(non product), out of scope, test design or test
execution problem, un-reproducible defect, not
understanding the specifications, etc.
33
37. Code Inspection - Example
March 2014
35
Background:
180 people on the project
3,700 modules interconnecting with each other
Complex infrastructure
25 testers
Using Test Director/Quality Center as reporting
platform
Strategic customer
39. Code Inspection - Example
March 2014
37
Analysis:
Main concern – Complience with design (10%
Medium+)
Investigated RCA:
A few specs were written by same designer
A few modules were written by 3 programmers
Initiated training for designer and programmers
40. Code Inspection - Example
March 2014
38
Background:
Another project,
450 people
working, 55 testers,
4,300 modules,
strategic customer
Focus on:
Performance
Maintainability
Proper algorithm
usage
41. Code Inspection - Example
March 2014
39
Analysis:
Investigated RCA:
Performance defects were on resource usage, memory
leaks
Implementing improper algorithm was mainly due to
specification documents written unclear + implementation
complexity chosen by a few programmers
Initiated training for architects and programmers
42. Adding defect template fields:
Injected, Detected, Removed
Version [build] + Date per field
[Updating the defect lifecycle process (status)]
Changing field CRUD permissions – Dev, Test,
Managers
Defining reports
Updating the Defect Management process
Training the teams
Implementing action plan…
Implementation guidelines –
defects RCA
March 2014
40
48. ‘5ys’ or ‘5 whys’ technique, and the cause-effect diagram.
Presenting a problem,
Asking “why?” it happens, finding the effect that caused it
(1 effect),
Presenting the effect on the diagram,
Asking “why?” it happens… [back to previous step, unless
we ask it for 5 times already]
Done.
Presenting the 5whys Technique
46
49. ‘5ys’ or ‘5 whys’ technique, and the cause-effect
diagram.
Presenting the RCA Technique
47
Cause
Cause Cause Cause
Cause
Problem
Why
#1
Why
#2
Why
#3
Why
#4
Why
#5
Thinking path…
50. ‘5ys’ or ‘5 whys’ technique, and the cause-effect diagram.
1. There is the assumption that a single cause, at each level
of "why", is sufficient to explain the effect in question.
2. What if one of the ‘Why’ is answered wrongly? Maybe
our answer is possible, but what if the actual cause is
something else entirely?
3. When we have found the problem, and draw the route,
how ‘strong’ is this solution? Maybe we should prefer one
over the other?
Challenges: what the method can
not solve48
52. Short structured interview with rep’s of management,
development, release, system, testing, product teams.
Step 1: Draw a cause-effect diagram & exercise the 5whys
Step 2: Investigate the arrows/causes for:
What evidence you have that the cause exist? (relevancy)
What evidence you have that the cause leads to the effect?
(strength)
Is anything else needed together with the cause for the effect to
occur? (strength)
Is there evidence that the cause is contributing to the problem
I’m looking at? How much it contributes? (Impact:
direct/indirect)
Enhancing the Method:
Example project50
53. Enhancing the Method:
Example project51
Type Question Cause-Effect
Relevancy What evidence you have that the cause exist? H/M/L
Strength
(S or W)
What evidence you have that the cause leads to
the effect?
H/M/L
Strength
(S or W)
Is anything else needed, together with the
cause, for the effect to occur?
Yes/No
Impact
(D or I)
Is there a evidence that the cause is contributing
to the problem I’m looking at?
Yes / No
Impact
(D or I)
How much this cause is contributing to a
possible resolution?
Direct /
Indirect
Mark
54. Enhancing the Method:
Example project52
Type Question Cause-Effect
Relevancy What evidence you have that the cause exist? High (3)
Strength
(S or W)
What evidence you have that the cause leads to
the effect?
Medium (2)
Strength
(S or W)
Is anything else needed, together with the
cause, for the effect to occur?
Yes (1)
Impact
(D or I)
Is there a evidence that the cause is contributing
to the problem I’m looking at?
Yes (1)
Impact How much this cause is contributing to a
possible resolution?
Direct (2)
Mark 9
You should mark each arrow using this table.
55. Step 3: Identify the routes leading to the
problem/s,
Step 4: Identify the strength and direction (impact)
they have (calculating the mark for each arrow),
Step 5: Choose the best route to focus on,
[Improve it, and go to the next one].
Enhancing the Method:
Example project53
57. Background:
company was using a very advanced technology, and
a complex product line,
Complex product, uses mechanics, electronics,
hardware, software, devices, cooling device, has water
resistant, has heating resistant, accurate up to
1:1,000,000 cm,
In the last 0.5 year, 50% of released machines
returned from the floor (clients) for fixing,
Example project – Hi-Tech Company
55
58. SQA manager was at a course I gave, and liked
one of the tools,
He thought automation can solve many of his
problems, because:
A lot more tests running,
Identifying more defects before the clients do,
Less products coming back,
Clients are happy!
Example project – Hi-Tech Company
56
59. I investigated their automation
needs,
Followed the steps of the
enhanced method,
Found out their problems might
be elsewhere…
Example project – Hi-Tech Company
57
Lets see the drawing board from
that meeting…
61. The RCA meeting (company exec’s and directors):
At first, the belief was that the primary problem
was:
Partial Test Planning (less tests are executed)
Example project – Hi-Tech Company
59
Lets see an illustration diagram …
62. 1st drawing – RCA meeting
60
Many clients
ask for
different Sw
of the
product
Many
versions
open in
parallel
Complexity of
version control
management is
very high
Defining req’
not good
enough by
client
Spec Lvl 0
No specs
in lvl 1
Spec Lvl
1 not
complete
or does
not fit
Spec Lvl
2 not
written
Good
definition of
Spec Lvl 0
Spec Lvl
1 fits
Spec Lvl
2 fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not full
coverage
Partial test
case planning
and coverage
Partial test
execution
and low
coverage
Our way of thinking1 2
63. 1st drawing – RCA meeting
61
Many clients
ask for
different Sw
of the
product
Many
versions
open in
parallel
Complexity of
version control
management is
very high
Defining req’
not good
enough by
client
Spec Lvl 0
No specs
in lvl 1
Spec Lvl
1 not
complete
or does
not fit
Spec Lvl
2 not
written
Good
definition of
Spec Lvl 0
Spec Lvl
1 fits
Spec Lvl
2 fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not full
coverage
Partial test
case planning
and coverage
Partial test
execution
and low
coverage
Our way of thinking1 2
64. 1st drawing – RCA meeting
62
Many clients
ask for
different Sw
of the
product
Many
versions
open in
parallel
Complexity of
version control
management is
very high
Defining req’
not good
enough by
client
Spec Lvl 0
No specs
in lvl 1
Spec Lvl
1 not
complete
or does
not fit
Spec Lvl
2 not
written
Good
definition of
Spec Lvl 0
Spec Lvl
1 fits
Spec Lvl
2 fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not full
coverage
Partial test
case planning
and coverage
Partial test
execution
and low
coverage
Our way of thinking
1
2
65. 2nd drawing – RCA meeting
63
Many clients
ask for
different Sw
of the
product
Many
versions
open in
parallel
Complexity of
version control
management is
very high
Defining req’
not good
enough by
client
Spec Lvl 0
No specs
in lvl 1
Spec Lvl
1 not
complete
or does
not fit
Spec Lvl
2 not
written
Good
definition of
Spec Lvl 0
Spec Lvl
1 fits
Spec Lvl
2 fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not full
coverage
Partial test
case planning
and coverage
Partial test
execution
and low
coverage
Our way of thinking1 2
66. After a while, we shifted the focus and agreed that
the real problem was actually:
Poor Product Quality
Because that was the reason the clients returned
their product.
And we started RCA from there.
After a while, we started to see the light – real
problems started to crystallize, problems that
involved people and processes
Example project – Hi-Tech Company
64
68. Our way of thinking
3rd drawing – RCA meeting
66
Many clients
ask for
different Sw
of the
product
Many
versions
open in
parallel
SCM - Complexity
of version control
management is very
high
Defining req’ not
good enough by
client
Spec Lvl 0
No
specs in
lvl 1
Spec Lvl 1
not complete
or does not
fit
Spec Lvl
2 not
written
Good
definition
of Spec
Lvl 0
Spec Lvl
1 fits
Spec Lvl
2 fit
Spec Lvl 2
does not
fit/complete
Code written
with low
match to
client req’
Only
Partial Test
planning
and not full
coverage
Partial test
case
planning and
coverage
Partial test
execution
and low
coverage
1 2
Tight
schedule
projectPrioritization
and
compromise
on scope to
clients
Low
Quality
Product
Req’
managemen
t not good
enough
Lack of methods
and techniques
in testing
Low lvl of test
identification
69. We then defined the relevancy, strength and
impact of each arrow (cause),
And calculated the grades for the arrows (which
are not seen here),
Example project – Hi-Tech Company
67
Back to the board…
71. 5th drawing – RCA meeting
69
Many
clients ask
for
different
Sw of the
product
Many
versions
open in
parallel
SCM - Complexity of version control
management is very high
Defining
req’ not
good
enough by
client
Spec Lvl 0
No specs in
lvl 1
Spec Lvl 1
not
complete
or does not
fit
Spec Lvl 2
not written
Good
definition
of Spec Lvl
0
Spec Lvl 1
fits
Spec Lvl 2
fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not
full
coverage
Partial test
case
planning
and
coverage
Partial test
execution
and low
coverage
Our way of thinking1
2
Tight
schedule
project
Prioritization
and
compromise on
scope to clients
Low
Quality
Product
Req’
management
not good
enough
Lack of methods and
techniques in testing
Low lvl of test
identification
S/D
W/D
W/I
S/I
72. We went back to double check the RCA of the
routes leading to the primary problem, marking
the arrows with their grades (from the table,
remember?)
We ended up circling the main causes, that have
initiated the strongest routes that are directly
impacting our problem,
Example project – Hi-Tech Company
70
75. Many
clients ask
for
different
Sw of the
product
Many
versions
open in
parallel
SCM - Complexity of version control
management is very high
Defining
req’ not
good
enough by
client
Spec Lvl 0
No specs in
lvl 1
Spec Lvl 1
not
complete
or does not
fit
Spec Lvl 2
not written
Good
definition
of Spec Lvl
0
Spec Lvl 1
fits
Spec Lvl 2
fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not
full
coverage
Partial test
case
planning
and
coverage
Partial test
execution
and low
coverage
Our way of thinking1
2
Tight
schedule
project
Prioritization
and
compromise on
scope to clients
Low
Quality
Product
Req’
manageme
nt not
good
enoughLack of methods and
techniques in testing
Low lvl of test
identification
S/D
W/D
W/I
S/I
Last drawing – RCA meeting
73
76. Many
clients ask
for
different
Sw of the
product
Many
versions
open in
parallel
SCM - Complexity of version control
management is very high
Defining
req’ not
good
enough by
client
Spec Lvl 0
No specs in
lvl 1
Spec Lvl 1
not
complete
or does not
fit
Spec Lvl 2
not written
Good
definition
of Spec Lvl
0
Spec Lvl 1
fits
Spec Lvl 2
fit
Spec Lvl 2
does not
fit/complete
Code
written
with low
match to
client req’
Only
Partial Test
planning
and not
full
coverage
Partial test
case
planning
and
coverage
Partial test
execution
and low
coverage
Our way of thinking1
2
Tight
schedule
project
Prioritization
and
compromise on
scope to clients
Low
Quality
Product
Req’
manageme
nt not
good
enoughLack of methods and
techniques in testing
Low lvl of test
identification
S/D
W/D
W/I
S/I
74
4/6
Last drawing – RCA meeting
Lets see the routes…
3/3
77. 5 major Root Topics were Identified, explained and prioritized:
1. Produce requirements from client definitions
2. Requirements management
3. Either ‘No Spec Level 1’, or ‘Spec level 1 not matching
requirements’
4. Lack of methods and techniques in testing for development
and testing teams
5. Allot of clients define slightly different requirement for the
SW – allot of specials
We defined a pragmatic corrective actions plan, with priority items.
Example project – Hi-Tech Company
75
78. Major Areas of Concern identified and prioritized:
1. Requirements Management
2. Configuration Management
3. Design Documentation and Flow
4. Testing Methodologies, techniques and tools
Not discussed:
- Release Management
- Risk Management + Risk Based Testing
- Requirements Definition
- Project Management
- Professional Development
Example project – Hi-Tech
Company76
Organization
Language!
80. If we follow the questioning and grading
process, than problems shall be the ‘leafs’
of the cause-effect diagram, with:
A positive answer to the questions:
Relevancy – ‘yes’
Highest strength mark (direct/Indirect),
and
Direct impact on the undesired
outcome (initial hypothesis)
Highest grade per route guideline,
Translate into company language (areas
of concern)
Enables an Immediate vs. long term
action plan
Differentiating Problems from
Symptoms78
Just what our office needs..
82. Cause-effect & RCA may eliminate the problems of the model
when answering the questions and marking them on the diagram
for the best route(s),
(but) We must deal with symptoms some time, in the short term,
We should estimate effort needed (or money required) for each
route, and integrate that into our decision (i.e. 60/40 weight)
The questions (answers) make sure that our analysis is with
minimal deviations, and that the route we take is a ‘strongest’ one,
It is a constructive process that leads to Understanding, Clarity,
Focus and the right Priority setting
Summary
80
83. Further enhancing the mode, we must think of the following:
What about the junctions points (inbound and outbound):
direct impact of routes with those? Indirect? Impact on speed of
performance (bottle-necks)?
What is the ROI of this method within context?
Can we validate a route? Can we tie it to be a successful
problem eliminator?
How much the method is context dependant?
Can we hook it to Test Process Improvement methods or other
Key Performance/Area Indicators?
Other?
Food for Thought…
81
85. RCA and Process Improvement?
March 2014
83
Introduction
Case Study #1
Case Study #2
86. Process improvement should use data and RCA
outputs
CI example… - process was changed, training was
done to relevant people
Defects example… - lessons learned, training was done
to relevant testers, discussions with development
made it clear which information is required more on
the defect template
RCA and Process Improvement?
March 2014
84
88. Analysis:
Small, yet impacting, breaks in work, caused huge
impact on the release (big team of testers)
Breaks were 15-45 min each
Areas of impact were: performance, network, DB
Analyzing test environments
utilization downtime
March 2014
86
89. Improved process:
Defined measurements for monitoring downtime
of test environments
Identify trend of areas of impact on infrastructure
Used it weekly to establish Status of Downtime, to
decrease technical impacts (reached -25% waste
on next release).
Analyzing test environments
utilization downtime
March 2014
87
90. Analyzing development effort
with defects found
March 2014
88
15
26
11
120
65
43
32
187
12
38
210
294
588
2184
504
210
126
1344
336 378
80%
99%
21%
62%
145%
230%
286%
156%
40%
113%
0%
50%
100%
150%
200%
250%
300%
1
50
SC MAF FBF CSM E-Care E-Support Rater AR Reports BL Interface
Investment vs Defects
Defects Dev Effort Def % vs Dev Eff %
~28 years development.
~150 people in development
team.
91. Analysis:
Areas of defects clustering mainly in: Rater, E-
Support, E-Care, AR
Relative % of defects are much higher than % of
development effort (days)
Investigated UT and Staging (integration test)
phases, found missing testing types done, UT &
INT regression testing, performance testing,
interface testing
Further considerations: Complexity, New/Legacy
code, # people touching code
Analyzing development effort
with defects found
March 2014
89
92. Improved process:
Defined Unit test and Integration test process and
strategy guidelines and work instructions
Trained programmers in UT and INT techniques and
new processes
Aligned effort estimation and duration with project
management and product management
Defined coverage criteria for UT and INT
Initiated test automation project on UT and INT levels
Analyzing development effort
with defects found
March 2014
90
94. Root Cause Analysis techniques can help us in
finding the underlying problems (root causes), and
get to deal with real problems
Structured RCA methods support productive
thinking, identifying problems and identify more
symptoms
Cause Effect Graphing (amended), Defects RCA
RCA and process improvement
Summary
Retrospective
March 2014
92
95. “It is not the strongest of the species that
survives, nor the most intelligent but the one
that is most responsive to change”
Charles Darwin
A changing world…
93
96. Or perhaps . . .
94
. . . the one who had anticipated all possible
requirements !