The document discusses the prevalence and impact of software bugs, noting that they cost the US economy approximately $59 billion annually and the global economy $1.1 trillion in 2016. It emphasizes the importance of integrating testing throughout the development lifecycle, promoting agile practices, and fostering collaboration between development and testing teams. Strategies for identifying and addressing issues early, understanding business impacts, and effective communication are highlighted as critical for successful software development.

1. John Pourdanis

2.  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 result, or to behave in
unintended ways
 An elusive creature living in a program that
makes it incorrect. The activity of
"debugging", or removing bugs from a
program, ends when people get tired of
doing it, not when the bugs are removed.

7.  Unhandled exceptions aka 500 internal server
error , depends mostly to code error.
 Ui broken layouts depends mostly on CSS and
to Internet Explorer.
 Logical errors depends to misunderstanding
of flow.
 Usability issues that make users have the
worst opinion for software.
 Security issues.

11.  In 2002, a study commissioned by the US
Department of Commerce's National Institute
of Standards and Technology concluded that
"software bugs, or errors, are so prevalent
and so detrimental that they cost the US
economy an estimated $59 billion annually,
or about 0.6 percent of the gross domestic
product.
 If debugging is the process of removing
bugs, then programming must be the process
of putting them in.( Edsger W. Dijkstra)

12.  Starting with the big picture, software failures
cost the worldwide economy $1.1 trillion in
2016. These failures were found at 363
companies, affected 4.4 billion customers,
and caused more than 315 years of lost time.
 Found at design phase by a walkthrough - $4
 Found during coding by a walkthrough - $10
 Found by unit test - $24
 Found by integration test - $1600
 Found by a customer after product shipped -
$6,000

13.  Adopt Agile as your culture
 Agile is not processes
 Agile != Jira
 Developed != Done
 Legacy project? Just start from something.

15.  Business - What problem are we trying to
solve?
 Development - How might we build a
solution to solve that problem?
 Testing - What about this, what could
possibly happen?

16.  It is the first half of the maxim “Test early and
often.”
 Inject testing to the whole development life
cycle.
 45%-65% percent of defects are introduced in
the requirements, architecture, and design
activities
 Work closely with Developers as a Team
 Development Team != Testing Team

22.  Respect other person’s work.
 Be patient.
 Ask for help and opinion.
 Don’t patch but create!

24.  Physical proximity: Communication is the very
foundation for Agile!
 Definition of Done: Clearly defined guidelines
that indicate when a feature is consider being
ready for release
 Early QA involvement: Testers should take an
active part already when new features are being
discussed in the sprint pre-planning meetings
and provide feedback from a testing perspective
as well as starting to work on test scenarios.
 Risk-Based Testing: Risk-Based Testing provides
an effective way to decide what to test, how
much, and in what order.

27.  Speak to your CTO about problems that you
have.
 Document issues with business affect tittles.
 Translate issues to money loss.
 If they press for a release show to them the
issues.
 If they agree “we are good to release” its not
your problem.
 Adopt the business model.

28.  It’s not a shame to change from dev to
testing.
 Try to fit your personal skills to software
industry.
 Cross functional teams help avoiding people
getting bored. T-shaped skilled persons.

30. If you want to ask something follow the 1st rule of
Agile. Just ask and communicate!