Online QADay 2023 ІГОР КОШЕЛЄВ «Built-In Quality» telegram: wwww.t.me/goqameetup fb: www.fb.com/goqaevent fb: www.fb.com/qaday.org linkedin: https://www.linkedin.com/company/goqa/ Сайт: www.online.qaday.org

1. SOFTWARE DEVELOPMENT COMPANY

2. Ihor
Kosheliev
Director of QA Office

3. What is Quality?

4. Cost of Bug/Change
Cost of
Fixing
Software
Bugs
Design Development Integration Deployment

5. Quality is a “state” ….
when expectations matches the reality.
Not just software defects, but stakeholders
expectations as well

6. Why Quality is Important?

7. How to make quality controlled ?

8. Built-in Quality

9. Why do teams choose to use
built-in quality?

10. What to do when the volume of regression
testing is constantly growing?

11. How to release more easily and with fewer bugs?

12. What is the
difference?
QUALITY ASSURANCE
TESTING

13. Manifesto for Agile Software Development vs
Quality?

14. Agile SDLC - nothing about
quality, only testing
AGILE
3
Development
2
Design
4
Testing
1
Requirements
5
Deployment
6
Review

15. Lean Agile

16. WHAT IS
LEAN?
Lean Production since 1950. Toyota
developed a new concept of “lean
manufacturing”. Toyota recognized that
inventory was a major cost factor for
production. Consequently, they reduced
waste, and the largest waste of them all
was excess material. By optimizing this
excess, Toyota developed lean
production.

17. 7 Wastes of Lean
OVER-
PRODUCTION
DEFECTS
WAITING
INVENTORY
MOTION TRANSPORTATION
OVER-
PROCESSING

18. Why is Lean important to us?
Kanban
Scrum
Agile
Lean
Systems thinking

19. People involvement
Short Lead Time
Continuous
Improvement
Built-In Quality
Standardization
Lean
Manufacturing
System

20. How to implement built-in
quality in scrum?

21. Traditional Agile
Fixed
Variable
Scope
Quality ?
Time Cost
Time Cost
Quality
Scope

22. Backlog
Definition of Ready
Iteration
Definition of Done
Feature
Done

23. Purpose of a Sprint Retrospective
Inspect
how the last Sprint
went with regards
to people,
relationships,
process, and tools.
Identify and order
the major items that
went well and
potential
improvements.
Create
a plan to improve
the way the
Scram team
does its work.

24. Differences between Timebox and Deadline
Agile
Deadline Timebox
Time for
working

25. Graphing productivity and overtime

26. Overtime & Tech debt

27. Overtime & Velocity

28. How to fix built-in quality in the project
so that teams can solve their problems?

29. BDD Lean UX
TDD
Acceptance
Criteria
1. Open 2. Requirements 3. Development
4. Acceptance
testing
5. Demonstration 6. Done
Definition of
Done
Весь процес
потребує якості.

30. Acceptance Criteria
Clear
Acceptance
Criteria
Development
Checking of
Results
Unclear
Acceptance
Criteria
Development
Checking of
Results
Request for
Change
Checking of
Results

31. BDD Lean UX
TDD
Acceptance
Criteria
1. Open 2. Requirements 3. Development
4. Acceptance
testing
5. Demonstration 6. Done
Definition of
Done
Весь процес
потребує якості.

32. TDD
1.
Write Test
2. Test
Fails
3. Write
Code
4. Test
Passes
5. Refactor

33. BDD Lean UX
TDD
Acceptance
Criteria
1. Open 2. Requirements 3. Development
4. Acceptance
testing
5. Demonstration 6. Done
Definition of
Done
Весь процес
потребує якості.

34. BDD
BDD
Issue
Tracker
Failing
Scenario
Coding
Phase
Passing
Scenario
Refactor

35. BDD and TDD
1. Issue
tracker
2. Failing
scenario
3. Coding
phase
4. Passing
scenario
5. Refactor
3.1 Failing
Unit Test
3.2 Green
Unit Test
3.3
Refactor

36. BDD Lean UX
TDD
Acceptance
Criteria
1. Open 2. Requirements 3. Development
4. Acceptance
testing
5. Demonstration 6. Done
Definition of
Done
Весь процес
потребує якості.

37. Why use lean UX?
LEANUX
THINK
MAKE
CHECK

38. Lean UX and Agile
MVP
2
3
1
LEAN UX
User
Stories
Release
Measure
&
Learn
Measure
Product
Increment
Daily
Scrum
Sprint
Backlog
24
Hours
2-4
Weeks
Test
Build
Design
Sprint Planning > Review > Retrospection
Product
Backlog

39. BDD Lean UX
TDD
Acceptance
Criteria
1. Open 2. Requirements 3. Development
4. Acceptance
testing
5. Demonstration 6. Done
Definition of
Done
Весь процес
потребує якості.

40. How to avoid Ice-Cream effect?
Manual Tests
Automated
GUI Tests
Integration
Tests
Unit
Tests

41. Test Automation Pyramid
Automated Unit
Tests
Automated Component Tests
Automated Integration Tests
Automated API Tests
Automated
GUI Tests
Manual
Session
Based
Testing

42. Achieving Flow with Test-First and a Continuous
Delivery Pipeline
Define Build Test Deploy Release
Product
Owner
Customer
Lean
UX
BDD
TDD
Developers
Developers /
Testers

43. Write
Feature
Test
Feature
Write Story Test Story
Write Code Test Code
Tradition “V” model delays feedback
Think Test-First

44. Think Test-First
Write
Feature
Test
Feature
Write Story Test Story
Write Code Test Code
Shift left for fast feedback

45. Think Test-First
Write
Feature
Test
Feature
Write Story Test Story
Write Code Test Code
Write
Feature
Test
Feature
Write Story Test Story
Write Code Test Code
Tradition “V” model delays feedback Shift left for fast feedback
Feature Test
Story Test
Code Test
Behavior - Driven
Development (BDD)
Behavior - Driven
Development (BDD)
Test - Driven
Development (TDD)

46. BDD and TDD shift testing left
Large
(Slow)
Medium
Small (Fast)
$$$
C
Typical Large
End-to-end UI
Typical Medium External
Services Single UI
Typical Small
Individual Classes

47. 1. Consistent quality
2. Cost savings
3. Customer satisfaction (developer as well)
4. Sustainable pace
5. More frequency releases
6. Reduced risk

48. My thoughts
Tester QA

49. Inspection does not improve the quality, nor
guarantee quality. Inspection is too late. The quality,
good or bad, is already in the product. Quality cannot
be inspected into a product or service; it must be built
into it.
—W. Edwards Deming

50. THANK YOU!