Efficient agile organizations focus on defect prevention rather than downstream defect discovery, because discovering defects during or after testing adds to development costs. Delaying discovery and repair of defects can make an agile team feel like they are operating in a mini-waterfall. Sharing his experience with Scrum/ Kanban teams, Leveraging the lean concept of limiting work in progress, David Jellison describes how grouping defects into two major categories—work-in-progress defects and escaping defects—reduces development costs and improves reliability in the field. Dave illustrates how to manage problem discovery early and minimize the existence of escaping defects. Treating escaping defects as the exception rather than the norm results in a much smaller defect backlog and increased customer satisfaction. This approach encourages increased collaboration between quality engineers and developers, and shifts the focus of team measures from defect counts to product delivery velocity and cycle time, with increased confidence in quality as the work is completed.
Develop a Defect Prevention Strategy—or Else!TechWell
Defects occurring throughout the development of a software project penalize the project. The effort spent remediating these defects robs the project team of valuable time, resources, and money that could otherwise be used for further innovation and delivering the highest possible quality product to wow the customer. The occurrence of a large percentage of these defects can be avoided with preventive defect removal strategies. Scott Aziz describes various methods for removing defects during the early design and development phases―long before testing. Methods include requirements-based testing that eliminates 95 percent of requirements defects prior to the coding phase, code reviews and inspections, and establishing model-based test design practices that allow for testing business requirements before any code is developed. Take back and adopt in your environment some of the most effective early defect prevention practices known and practiced in the industry today.
This is a free module from my course ISTQB CTAL Test Manager revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
Develop a Defect Prevention Strategy—or Else!TechWell
Defects occurring throughout the development of a software project penalize the project. The effort spent remediating these defects robs the project team of valuable time, resources, and money that could otherwise be used for further innovation and delivering the highest possible quality product to wow the customer. The occurrence of a large percentage of these defects can be avoided with preventive defect removal strategies. Scott Aziz describes various methods for removing defects during the early design and development phases―long before testing. Methods include requirements-based testing that eliminates 95 percent of requirements defects prior to the coding phase, code reviews and inspections, and establishing model-based test design practices that allow for testing business requirements before any code is developed. Take back and adopt in your environment some of the most effective early defect prevention practices known and practiced in the industry today.
This is a free module from my course ISTQB CTAL Test Manager revised to 2012 syllabus. If you need full training feel free to contact me by email (amraldo@hotmail.com) or by mobile (+201223600207).
Lightweight approach to defect management using Kanban. Presentation was originally for a build team to manage build requests, please excuse any typos which still references the build process.
Scrum está próximo de completar 20 anos. De lá pra cá o framework saiu do anonimato e passou a emplacar as discussões em organizações de todos os portes nos mais variados seguimentos. Tendo o Scrum mudado tão pouco desde a sua criação, será que suas práticas e conceitos ainda são os mais adequados depois de tudo que aprendemos sobre agilidade nos últimos anos? A ideia desta apresentação é revisitar algumas das principais práticas e determinações do Scrum, avaliando o contexto da sua criação e a sua aplicabilidade no mercado de hoje. Uma provocação contrastando o que diz a teoria com o que mostra a prática.
Palestras ministrada no ALM RoadShow Campo Grande, aonde foi apresentado o que é ser ágil e como os processos estão interligados. Com sugestões para melhorias futuras.
High Quality Software Development with Agile and ScrumLemi Orhan Ergin
Module 1. Born to fail
- Why projects are failing
- Waterfall & traditional software development
Module 2. Agile
Module 3. Scrum
Module 4. Writing high quality software with Agile
- XP
- How Google Write Software
Module 5. Do's and dont's
- How Scrum might fail
- Myths and realities
Module 6. How to kick off Scrum
This is a "Best Of" list of my (and others) failures over the years in attempting to adopt test automation. In it, you'll find 13 categories of What Not to Do. Presented at Turku Agile Day 2012 (#tad012).
Traditional approaches to quality and risk management involve quality gates, change control boards, feature freeze and code freeze milestones, and independent QA or Test groups. These approaches stabilize quality at by sacrificing agility.
Yet buggy fragile code is even more dangerous for Agile teams where so much is changing so often. Quality and risk management are critically important for agility.
This leads to the inevitable question: if the traditional approaches to quality and risk management don't work in an Agile context, what does?
Practices vary across organizations, but all successful teams emphasize the same underlying principles of fast feedback, high visibility, collaboration, and alignment. This talk examines various approaches Agile teams have taken to increase quality, mitigate risk, and ultimately ensure they are delivering the highest possible value for their stakeholders.
Build-in Quality!? SAFe® Testing im Finnova-Express (Swiss Testing Day 2017)Christoph Wolf
Testing im skaliert-agilen Umfeld (SAFe): Finnova ist ein führender Anbieter von Bankensoftware auf dem Finanzplatz Schweiz. Vor über zwei Jahren wurde begonnen, auf skaliert-agile Software-Entwicklung umzustellen. Es wurde SAFe mit derzeit ca. 25 Scrum-Teams und drei Agile Release Trains eingeführt. Dabei muss natürlich sichergestellt sein, dass sowohl die einzelnen, von den Teams gelieferten Module als auch das integrierte Produkt eine hohe Qualität haben. In diesem Vortrag präsentieren wir Antworten auf die Frage, wie wir Quality Assurance bzgl. Organisation, Methoden, Dienstleistungen und Strategie auf der SAFe Team- und Programm-Ebene gestalten.
www.mimacom.com
“F*** the process“? - Oder was für eine funktionierende Organisation benötigt wird
Referenten: Felix Kubasch und Joscha Jenni, mimacom GmbH
Abstract: Der Vortrag erzählt eine Geschichte aus dem Eco-System der mimacom und fokussiert auf die Verbindung von sogenannten „traditionellen“ und „modernen“ Welten. In diesem Fall CMMI und Agilität.
mimacom ist seit dem August 2012 als einzige Schweizer Unternehmung CMMI Level 5 zertifiziert und hat es als eines von wenigen Unternehmen weltweit geschafft, Level 5 auf der Basis von agilen Frameworks zu erreichen.
Bloss eine weitere Zertifizierung oder was hat dies der mimacom für einen Nutzen gebracht? Wurde überhaupt ein Nutzen generiert? Was sind die Schattenseiten dieser Implementation?
Insbesondere diesen Fragen möchten wir Manage-Agile Vortrag auf den Grund gehen und einen Beitrag aus der Praxis für die Praxis leisten. Die gewonnenen Erfahrungen werden aus einer Management Sicht präsentiert, ohne das Detail aus den Augen zu lassen, denn es sind die kleinen Dinge, die schlussendlich zählen.
Bezug zum Management: Insbesondere werden die folgenden 3 Fragestellungen behandelt:
1. Wie mit agilen Frameworks und CMMI gearbeitet werden kann.
2. Wieso CMMI keine starren Prozesse voraussetzt.
3. Wie die Organisation trotz Prozessframework flexibel gestaltet werden kann und wo die Gefahren eines Over-Engineering liegen.
Joscha Jenni ist Referent der Manage Agile 2015
Joscha Jenni leitet den Bereich Projekte & Projektmanagement in der mimacom ag und ist Mitglied des Management Teams. Er arbeitet als Projektleiter und Berater im Bereich Software Entwicklung und ist ein Enthusiast für schlanke und agile Ansätze. Seit mehreren Jahren beschäftigt er sich mit der Implementierung von agilen Frameworks in KMUs und im Enterprise Bereich.
Felix Kubasch ist Referent der Manage Agile 2015
Felix Kubasch ist Geschäftsführer der mimacom Deutschland GmbH. Er verfügt über langjährige Erfahrung in verschiedensten Disziplinen bei der Einführung von komplexen und grossen Software Entwicklungsprojekten. Vor seiner Tätigkeit bei mimacom war er verantwortlich für die Umstellung von Entwicklerteams vom Wasserfall-Prozess hin zu zu Agiler Entwicklungsmethodik bei unterschiedlichen Unternehmen in Deutschland und den USA. Er beleuchtet die Vorteile von CMMi Level 5 auf die Geschäftsführung.
BizDevOps – Delivering Business Value Quickly at ScaleQASymphony
BIZDEVOPS – DELIVERING BUSINESS VALUE QUICKLY AT SCALE
65+% of surveyed organizations are currently on the path to switch to DevOps or have already implemented the process, and the benefits of a properly implemented DevOps program are clear – quicker time to customer value, better alignment between businesses and customers, and a better ability to respond to customer input. However, when it comes to DevOps adoption, many teams rush to focus on one specific issue within one area when they would actually benefit more from aligning business, development, testing, and operations up front. The five major problems in DevOps adoption include:
Lack of Test Automation Coverage
Lack of Visibility into Testing
Maintaining Various Test Versions and Aligning Tests with Versions of Source Code
Maintaining a Single Source of Truth in the Testing Process
Understanding Where Business Value Currently is in the “BizDevOps” Pipeline
After helping hundreds of customers in their DevOps journeys, these three industry experts will cover these major problems, as well as innovative strategies to overcome them:
Bobby Smith – Director of R&D, QAS Labs
Brandon Cipe – VP DevOps, cPrime
Kevin Dunne – VP Business Development, QASymphony
Tune in to learn more about the state of the industry, the direction that DevOps adoption is moving toward, and what we like to call “BizDevOps”. You won’t want to miss this session!
Every QA/QE professional has encountered a flaky test at least once in their career. It may be a small, harmless bug that can be fixed in an instant, or it may take months to identify and fix it. This can be very costly and take a toll on your reputation and budget.
Don’t you want to know why flaky tests exist, how to identify them at an earlier stage, or even avoid them? I’ll walk you through automated and manual UI testing.
Join the investigation of web applications and their UI, and we will figure it out together with you to find out the origins and roots of common flaky tests; to explore real cases and their solutions; to learn good practices.
The DevOps disaster: 15 ways to fail at DevOps - Bert Jan Schrijver - Codemot...Codemotion
Getting DevOps right isn't easy. It's downright hard. In this talk, I'm not going to explain how to 'do' DevOps in your organisation, since there is not just one 'right' way to do it. What I can show you however, is how NOT to do DevOps. This session shares 15 common misconceptions, call them anti-patterns, of DevOps. I'll talk from my own experiences in getting things wrong, explain why they are wrong and prevent you from making the same mistakes. You'll leave this session with a basic understanding of how (not) to fail at DevOps and hopefully, a smile on your face ;-)
Software projects were historically managed on a bet the farm model. They succeeded or they failed. And when they failed (as big software projects often did), the consequences were typically dire for, not only organizations as a whole, but for many of the individuals involved. Today, by contrast, many software and the development projects have evolved toward a much more incremental, iterative, and experimental process that takes cues from the open source model which excuses (and even rewards) certain types of failure.
In this session, we’ll discuss how failure can be turned into a positive. This includes the organizational dynamics associated with tolerating uncertain outcomes, the need to define acceptable failure parameters, and the technical means by which experimentation can be automated in ways that amplify the positive while minimizing the effect of negative outcomes.
The original promise of TDD was that it would assist in guiding the development of clean code, but it often ends up polluting our architecture with excessive composition, is expensive to write, and becomes an obstacle to change, not an aid to refactoring. In this talk, we look at the fallacies of TDD and learn about the key principles that we should be following for mastery of this practice. This talk is intended for those who have been practicing TDD, or who have tried TDD and given up because of shortcomings in the approach they were taught.
Behavior Driven Development is one of the most commonly misunderstood techniques in DevOps, but it is also one of the key enablers of both an Agile culture and true continuous deployment. This talk will attempt to fill in the missing pieces on exactly what BDD is and how your teams can use it to increase communication, drive quality, and reduce waste. We will also connect the dots on why you need a test-first strategy to enable trunk-based development, continuous integration, and continuous deployment. If your business still struggles with monthly or quarterly big-batch releases, this talk will show you what your teams must do to evolve to the next stage of continuous delivery.
Similar to StarWest 2012 - Agile Defect Management: Focus On Prevention (20)
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
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
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.
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.
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.
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.
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
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.
De-mystifying Zero to One: Design Informed Techniques for Greenfield Innovati...
StarWest 2012 - Agile Defect Management: Focus On Prevention
1. Agile Defect Management
Focus On Prevention
David Jellison
Director, Quality Engineering
djellison@constantcontact.com
Twitter: davidjellison
2. You Will Learn
Categorizing defects drives defect context
management
Testing is part of delivering a story or feature
Detecting and resolving defects as the work is
delivered prevents backlog
Attaching an in-progress defect to a current story
encapsulates the defect in the current work
Escaping defects become the exception rather than
the norm
2 Twitter: davidjellison
3. The One Finding The Most Bugs Wins!
Downstream Testing Approach
Lord of the Rings: Legolas & Gimli counting kills
Twitter: davidjellison
4. Preventing Bugs is Craftsmanship
upstream Testing Approach
Twitter: davidjellison
5. Quest for Zero Defects
You can only manage what is known
Crosby’s “Zero Defect” standard manages to requirements
(http://en.wikipedia.org/wiki/Zero_Defects)
Agile changes the game, managing business value to
the customer frequently
Need a pattern to manage defects that we inevitably
discover during and after release
Never really reach 0 Defects
5 Twitter: davidjellison
8. Late Defect Discovery Costs
Opportunity cost
Not working on other things
Developer Context switching
Time to get acclimated and then back again
Rebuild and test time
More cycles to deliver the fix
Damage control
Support time and reputation
Other hidden costs…
8 Twitter: davidjellison
9. Traditional Defect Discovery Trends
Defect debt accumulation
Delay in resolution
Defects resolved
Dev/QE aligned
9 Twitter: davidjellison
10. Defect Discovery Improvement Plan
Stop defect debt accumulation
Move defect discovery up in the development cycle
Embed QE into teams with Dev/QE alignment
Prevent defects through design review & test automation
Write failing regression tests as defects are discovered
Test in sandbox
Don’t wait for final integration environment to test
Continuous build and continuous integration patterns
Whole-team responsibility for quality
Clear acceptance criteria for all new work
Everyone tests
Automated test code reviews with developer
10 Twitter: davidjellison
17. Categorizing Defects
Escaping Defects
Discovered defects allowed into the field
Undiscovered defects found in the field
17 Twitter: davidjellison
18. Categorizing Defects
WIP (work in progress) Defects
Defects discovered in new code not yet delivered to field
Becomes additional acceptance criteria for delivery
Treat as subtasks of feature work
Caged by the parent work in progress
18 Twitter: davidjellison
19. Managing Defect Discovery
Its OK to not write
defects if there are
failing automated tests
to manage
Promote failing tests to
WIP defects if need to
manage separately
Promote WIP defects
that are still failing at
time of delivery to
escaping defects and
added to the backlog
19 Twitter: davidjellison
20. Focus on Prevention
Develop failing
regression tests when
discovered manually
Continuous feedback
through failing test run
reports
Associate WIP defects
with feature work in
progress
20
21. Managing Escaping Defects
Delivering business
value over no defects
No unknown failures in
regression tests
Coordinate planned
escaping defects with
customer support
Reduce escaping
defects to less than you
can count on two hands
21
24. Escaping Defect Reduction Plan
Set expectation in the teams that fixing WIP defects
is part of the acceptance criteria
Add escaping defects in the field to the backlog and
rank along with other work
Plan to fix some number of escaping defects from
the backlog in each development cycle
Treat escaping defects as the exception rather than
the norm
24 Twitter: davidjellison
26. Example: WIP Defects/Escaping Defects
Shifting the focus to WIP defects results in far fewer
escaping defects in the field, even with increased
discovery
WIP Defects [blue]
Escaping Defects [red]
26 Twitter: davidjellison
27. Example: WIP Defects/Escaping Defects
Each team may be in a different place with business
risk and can manage escaping defects differently
Develop a theme strategy
WIP Defects [ red & blue]
Escaping Defects [green]
27 Twitter: davidjellison
28. What We Covered
Categorizing defects drives defect context
management
Testing is part of delivering a story or feature
Detecting and resolving defects as the work is
delivered prevents backlog
Attaching an in-progress defect to a current story
encapsulates the defect in the current work
Escaping defects become the exception rather than
the norm
28 Twitter: davidjellison
29. Contact:
David Jellison
Dir, QE
Constant Contact, Inc.
1601 Trapelo Road
Waltham, MA 01451
djellison@constantcontact.com
P: 339-222-5712
Blog: http://davidjellison.wordpress.com
Twitter: davidjellison
http://ConstantContact.com/Careers
29 Twitter: davidjellison
Editor's Notes
Phillip Crosby’s “Absolute Defect Management” with a “Zero Defect” quality standard can only be met when validating against very clear and precise requirements and standards.
The relative cost of defect discovery at least doubles at each stage of .