Fighting bugs or piling them? Anton Březina

Slides:



Advertisements
Similar presentations
By Rick Clements Software Testing 101 By Rick Clements
Advertisements

Agile PM Basics Dr. Vijay Kanabar © Boston University
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
Computer Engineering 203 R Smith Agile Development 1/ Agile Methods What are Agile Methods? – Extreme Programming is the best known example – SCRUM.
1 Testing. 2 About Testing  The reason the program is in testing is that it probably doesn’t work!  We test to find bugs before our users and hope that.
Discover how to improve productivity by going DevOps and SAFe.
Xtreme Programming. Software Life Cycle The activities that take place between the time software program is first conceived and the time it is finally.
Paweł Słowikowski What can Agility do for YOU. Who am I Have been: Software tester Verification Project Manager Scrum Master Agile Coach Currently: Scrum.
Agile Testing with Testing Anywhere The road to automation need not be long.
CS4723 Software Validation and Quality Assurance Lecture 9 Bug Report Management.
Chapter 9 – Software Evolution and Maintenance
CS527: (Advanced) Topics in Software Engineering Overview of Software Quality Assurance Tao Xie ©D. Marinov, T. Xie.
1. Topics to be discussed Introduction Objectives Testing Life Cycle Verification Vs Validation Testing Methodology Testing Levels 2.
1 “ Understanding leads to perfection” Author: Herb Isenberg Ph.D A Bird’s Eye View Quality Foundations January 2011.
SYSTEM DYNAMICS MODELING OF AGILE CONTINUOUS DELIVERY PROCESS 資工 4A 鄭鈞輿.
 CS 5380 Software Engineering Chapter 8 Testing.
1 - Agile in a nutshell. 2 - Basic principles ●Relies on an iterative, incremental development mechanism with continuous adaptation to customer requirements.
Basic of Software Testing Presented by The Smartpath Information System An ISO 9001:2008 Certified Organization
C O N F I D E N T I A L 22-Oct-15 1 StarCite Engineering Weekly Meeting StarCite Engineering Feb 9, 2009.
1 FROM DEVELOPERS TO ENGINEERS ENGINEERING ROLE IMPLEMETED AT EXPEDIA August 26, 2015.
DEBUGGING. BUG A software bug is an error, flaw, failure, or fault in a computer program or system that causes it to produce an incorrect or unexpected.
Software Testing and Maintenance 1 Code Review  Introduction  How to Conduct Code Review  Practical Tips  Tool Support  Summary.
Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 16, Methodologies: Putting it all together.
Inspection and Review The main objective of an Inspection or a Review is to Detect Defects. (Today -there may be some other goals or broader definition.
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Bringing Sense, Sensibility, and Sanity to projects.
Theories of Agile, Fails of Security Daniel Liber CyberArk.
Stand Up Comedy Project/Product Management
Software Quality Assurance SOFTWARE DEFECT. Defect Repair Defect Repair is a process of repairing the defective part or replacing it, as needed. For example,
1 Software Engineering. 2 Software Engineering is the study of activities related to the development of a software product.
Phoenix Scrum User Group Simplifying Scrum Online May 21 st 2009.
How to Build Test Inventory Test inventory is built and updated as the software project moves from phase to phase –Start with Requirements List the actual.
Intelligence and Information Systems 1 3/17/2004 © 2004 Raytheon Company USC/CSE Executive Workshop on Agile Experiences March 17, 2004 A Raytheon Agile.
TestZilla A Test Manager System Kevin Huang Sam Van Dalfsen.
What is a software? Computer Software, or just Software, is the collection of computer programs and related data that provide the instructions telling.
MAJOR SOFTWARE FAILURES, WHY THEY FAILED AND LESSONS LEARNED BY AKPABIO UWANA.
Chapter 25 – Configuration Management 1Chapter 25 Configuration management.
© 2012 IBM Corporation Rational Insight | Back to Basis Series Working on Enhancement/Defect Nick Hu Shuai 2012/05/17.
Open source development model and methodologies.
Peter Varhol Solutions Evangelist
Configuration Management
SOFTWARE TESTING Date: 29-Dec-2016 By: Ram Karthick.
Software Configuration Management
Software Engineering (CSI 321)
Wael Ellithy, Ph.D. Arx ICT
Testing More In CS430.
Agile Development -- an overview
Lessons learned from testability failures
Chapter 18 Maintaining Information Systems
Configuration Management
CS 577b: Software Engineering II
UML Activity Diagram Documents the Flow the of Program
Taking an Iteration Down to Code
Business Should Adopt Agile Testing. Test Driven Development is an essential software development way that is made by an automated test program which.
What do you need to know about XP?
Software Quality Engineering
AutomIQ Inc. Proprietary & Confidential – DO NOT DISTRIBUTE
UML Activity Diagram Documents the Flow the of Program
Automation Of Software Test
Automated Testing and Integration with CI Tool
Chapter 9 – Software Evolution and Maintenance
CSSSPEC6 SOFTWARE DEVELOPMENT WITH QUALITY ASSURANCE
CS240: Advanced Programming Concepts
Welcome to Corporate Training -1
Scrum Science NGSS: Engineering, Technology, Applications of Science
Chapter 8 Software Evolution.
Bringing more value out of automation testing
CS5123 Software Validation and Quality Assurance
White Box testing & Inspections
Walking dead. How to save project?
Presentation transcript:

Fighting bugs or piling them? Anton Březina Bugfighter 101 Fighting bugs or piling them? Anton Březina September 12, Agile Prague 2017 Avast Confidential

Miscommunication of requirements Design Lack of version control error, flaw, failure or fault in a computer program or system that causes it to produce an incorrect or unexpected result, or to behave in unintended ways [wiki] Miscommunication of requirements Design Lack of version control Buggy third-party tools Human factors Poor testing Unrealistic time schedule Last minute changes … Avast Confidential

Avast Confidential

Avast Confidential

Avast Confidential

Avast Confidential

Avast Confidential

Avast Confidential

Avast Confidential

Avast Confidential

Admit it’s buggy and … …won’t fix the bugs! transparently and per informed decision based on age recent activity customers affected business impact complexity of the fix reproducibility bizarre environments time constraints … Avast Confidential

Use common sense consider application’s market value is it worth fixing old issues? is it worth fixing new issues? is it worth refactoring? be prepared to reopen won’t fixed bugs if it makes sense play fair with your customers admit it is legacy software propose migration to new solutions play fair with your employees and colleagues admit you have limited resources working on new features is more fun than fixing old issues 60:20:20 Avast Confidential

Bugs will keep coming Reported from: automated tests manual testing bug bashes support & customer reports integration … Avast Confidential

Bug triage – who? developer tester product manager scrum master team leader support engineer customer representative Avast Confidential

Bug triage – what? well described? reproducible? new or duplicate? correct project? correct priority? impact ability to fix complexity of the fix Avast Confidential

Bug triage – what am I doing wrong? bug triage ≠ status meeting responsibility vs. authority keep it short and focused too many attendees attendees not involved in the triaged project too many P1s bug volleyball Avast Confidential

Summing it up get your current bug backlog under control get the flow of new bugs under control get used to keeping it under control promptly react to sudden bug infestations keep an eye on old issues Avast Confidential

Q&A Avast Confidential