The document discusses the importance of quality in software development, defining it as meeting customer needs and providing satisfaction through various perspectives and approaches. It emphasizes the continuous cycle of learning, planning, executing, and validating processes, while highlighting the roles of team collaboration and various testing methods to ensure both functional and structural quality. The document stresses that everyone is responsible for quality, encouraging early user involvement and frequent testing to enhance product outcomes.

1. Crafting Quality Software
Best Good Practices

2. Intro - Tarcio

3. Intro - Adam

4. What is Quality?

5. What is Quality?
Meets
customer needs
and provides
satisfaction
“Fitness for use”
(Juran)
“Conformance
to requirements”
(Crosby)
“Quality is pride
of workmanship”
(Deming)
Freedom from
defects of
deficiencies
Value of
worthiness
Definition of
quality

6. How good or bad
something is?
What is Quality?

7. What is Quality?

8. What is Quality?

9. What is Quality?

10. ● Perceptions
● Preconditioned
● Experiences
● Education
● Culture
● Opinions
Individual Traits

11. A Historical Perspective of Quality

12. A Historical Perspective of Quality

13. A Historical Perspective of Quality

14. A Historical Perspective of Quality

15. A Historical Perspective of Quality
Integrate learnings
Renew theories
Adjust methods
Do we need to
learn more?
Act
Study
(Check)
Do
Plan
Monitor outcomes, test
validity
of theory. Test the plan.
Examine success or
unexpected outcomes.
Look for new lessons or
problems to solve.
Execute the plan,
carry out the
activities, apply our
best knowledge,
pursue the desired
purpose and goals.
Identify purpose and
goals. Formulate
theories and
proposals. Define
measures of success
(and how to measure
them). Plan activities.

16. A Historical Perspective of Quality

17. ● Team motivation.
● Increased customer satisfaction.
● Return on investment.
What are the Benefits of Quality?

19. ● Individual and collective responsibility.
● Individuals can contribute in different ways.
● Starts when an idea is conceived and
continues throughout a product’s lifecycle.
Who is Responsible?

20. Applying Quality

21. 3 Aspects of Software Quality
Process
Structural Functional
What can we do to
ensure quality?
Does the software do what
is supposed to do?
Is the software easy to
modify and enhance?

22. Functional and Structural Traits
Correctness
Usability
Efficiency
Reliability
Integrity
Adaptability
Accuracy
Robustness
Maintainability
Flexibility
Portability
Reusability
Readability
Testability
Understandability
Security
FunctionalStructural

23. Process’ activities
Inception
Iteration
Zero
Iteration
Kick Off
Story
Kick Off
Story
Walkthrough
Release
Development Retrospective

24. Functional + Structural Quality
UnderstandabilityKnowledge share
Pairing
Better
written software
Team Collaboration

25. Pair Programming
Nope, not like this

26. Pair Programming
Yeah, more like this

27. Pair Programming Traits
● Emotionally demanding
● Constant learning
● Conversational
● Collaborative
● High quality output
● Costly (2 heads per problem)
TIME
Productivity
Q
uality
Cost

28. Testing
Functional + Structural Quality
TestabilityValidates requirements
Confidence
Robustness

29. ● Costs more
● No real focus
● Slow to run
● Longer to write
● Too Integrated
Testing Sad Reality

30. Testing Ideal
Exploratory
Testing

31. Test Driven Development

32. Test Driven Development
● Not a silver bullet
● Know when to use it
● Understand first, TDD later

33. Unit Testing
Small
Fast
Isolated
Cost effective
Focused

34. Unit Testing
Helps design
Find issues early
Facilitate change
Facilitate integration

35. Integration Testing
Two unit tests, no integration test.

36. Acceptance Testing

37. Exploratory Testing
Test Design
Test Execution
Analysis
Learn

38. Other Types of Testing
“You never know what a customer will do
to your product until they do it”
- Adam Crough
● Smoke testing.
● Penetration testing.
● Performance testing.
● User testing.
● Accessibility testing.
● Regression testing.
● A/B testing.
● Functional testing.
● Acceptance testing.
● Security testing.

39. Continuous Integration
● Automate code checks
● Exercise regression testing
● Improves team confidence

40. Visibility

41. Continuous Delivery
Plan Build
Release Test

42. One more thing

43. User Validation

44. User Validation - Types
Q & A Observation Prototyping Release early

45. User Validation - Benefits (Case Study)
18 Month Project
3 months 6 months 9 months

46. Final thoughts
Collaborate often
Test, test, test
Automate checks
Visualize results
Involve users early
Everyone is responsible for quality

47. Thank you!
@tarciosaraiva
http://bit.ly/acrough