The document discusses product quality in agile projects. It covers traditional vs agile testing approaches, the four quadrants of agile testing (test-driven development, data-driven development, exploratory testing, and non-functional testing), the importance of automation in agile testing, and key success factors. It also discusses quality factors, the quality triangle in agile projects, and common problems that can occur in agile projects like defects and lack of testing if not properly managed.

1. Product Quality In Agile Project
By Nhan Nguyen

2. Contents
Quality Overview (Traditional vs Agile)
Agile Testing Quadrants
Automation In Agile Project
Key Success Factors Of Agile Testing

3. Quality?

4. Quality Factors

5. Quality Triangle
Quality
Scope
Cost Schedule
Evolve from Traditional… To Agile…
Value
Quality Constraints
Scope
Cost Schedule
Agile Iron Triangle

6. Traditional vs Agile Testing
Traditional Agile

7. Cost Of Less Quality

8. Traditional vs Agile Testing
R
D
C
T
RL
R
D
C
T
RL
Time Scale (Day)
R
C
T
RL
R
C
T
RL
R
C
T
RL
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
RL
Waterfall
Model
Agile
Model
Sprint-1 Sprint-2 Sprint-3
Agile: Adapt change, Deliver early & continuously
R: Requirement D: Design C: Coding T: Testing RL: Release
D D D D D D D D D D D

9. Traditional vs Agile Testing
Developer
Requirement Spec
Design Spec
Source Code
Test Plan
Tester
Customer
Traditional
Release
Build
Fix
Developer

10. Traditional vs Agile Testing
Developer
Backlog
Design Test
Source Code
Test Plan
Release
Build
Tester
Customer
Fix
Agile
(Card, Confirmation, Conversation)
Developer
Communication
Development team

11. Quality Is Planned In, Isn’t
Inspected In

12. Agile Testing Quadrants

13. Q1: Test Driven Development
 Tools:
 Source code control tools: SVN,
CVS, ClearCase, Perforce…
 IDEs: Eclipse, NetBean, Visual
Studio, IntelliJ IDEA…
 Build and Automation Build tools:
Ant, Nant, Maven, Hudson,
Bamboo…
 Unit Test Tools: Junit, Nunit,
TestNG
 Purpose:
 Ensure quality by
helping programmer
create right code and
right design

14. Q2: Data Driven Development
 Tools:
 Elicit requirements tools: Mind
maps, Spreadsheets, Mock-up,
Flow diagram…
 Automation test tools: JBehave,
Nspec, Fit/Fitnesse, Selenium,
RubyWatir …
 Strategies for writing tests
 Build tests incrementally
 Keep the tests passing
 Use right test design patterns
 Keyword and data-driven tests
 Purpose:
 Help to develop the
right functionality by
business-facing test

15. Q3: Exploratory testing
 Test types
 Demo with customer
 Scenario testing
 Usability testing
 Who does these tests:
 Requires good skills, experience,
intuition, critical thinking
 Involve the customers
* Quadrant 2 tools may apply
 Purpose:
 Recreate actual user
experiences
 Realistic use
 Constructive

16. Q4: Non-functional testing
 Test types
 Performance, Stability, Reliability,
Maintainability…
 Who does these tests:
 Experienced testers with tools
support
 Experts (database, security…)
 Tools
 Loadrunner, jMeter, the Grinder,
JunitPerf…
 Purpose:
 Non-functional testing

17. Why Automate?
Manual testing takes too long
Manual process are error prone
Automation free people to do their best work
Automated regression tests provide a safety NET
Automated tests give feedback, early and often
Tests and examples that drive coding can do more
Tests are great documentation
ROI and Payback

18. What Can We Automate?
Continuous Integration, Builds, and Deploys
Unit and component tests
API or Web services testing
Testing behind the GUI
Testing the GUI
Load tests
Comparisons
Repetitive Tasks
Data creation and setup

19. Common Problems In Agile Projects
Integration
Defect
No Time Left for
Testing or Fixing
Large Testing
Effort
Late Defect
Detection
R
C
T
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
R
C
T
RL
RLAgile
Cycle
Sprint-1 Sprint-2 Sprint-3
Time Scale (Day)
D D D D D D D D D D D D
…

20. Test Driven Development (TDD)
Tools/Frameworks: csUnit (.Net), CUnit, JUnit, NUnit, OUnit, PHPUnit, PyUnit (Python), TestNG,
Test::Unit (Ruby), VBUnit, xUnit.net…

21. Test Driven Development (TDD)
Advantages
◦ TDD shortens the programming feedback loop
◦ TDD promotes the development of high-quality code
◦ Reduced interface misunderstandings
◦ TDD provides concrete evidence that your software works
◦ Reduced software defect rates
◦ Better code
◦ High test coverage
◦ Less debug time.
Disadvantages
◦ Programmers like to code, not to test
◦ Test writing is time consuming
◦ TDD may not always work

22. Acceptance Test Driven Development
(ATDD)
Tools/Frameworks: FIT/FitNesse, SpecFlow, thucydides, Selenium…

23. Acceptance Test Driven Development
(ATDD)
Advantages:
◦ Definitive requirements reduce misunderstandings
◦ Delivers efficiencies by taking care of requirements and test design as a single activity
◦ Promotes collaboration in the team
◦ Prevents project defocus (feature creep)
◦ Enhances customer awareness and understanding of the product’s capabilities and
limitations
◦ Simplifies documentation development and maintenance
◦ Enables earlier testing, earlier defect detection
◦ Automated regression testing is delivered as part of the project
Typical Challenges:
◦ Getting the entire team to follow the process
◦ Implementation of ATDD tools for process management and automation
◦ Maintenance of automated test scripts

24. Continuous Integration (CI)
Tools/Frameworks: Hudson, Jenkins, Bamboo, Cloudme…

25. Continuous Integration (CI)
Advantages:
◦ When unit tests fail or a bug emerges, developers might revert the codebase to a bug-
free state, without wasting time debugging
◦ Developers detect and fix integration problems continuously
◦ Early warning of broken/incompatible code
◦ Early warning of conflicting changes
◦ Immediate unit testing of all changes
◦ Constant availability of a "current" build for testing, demo, or release purposes
◦ Immediate feedback to developers on the quality, functionality, or system-wide impact
of code they are writing
◦ Metrics generated from automated testing and CI
Disadvantages
◦ Initial setup time required
◦ Well-developed test-suite required to achieve automated testing advantages

26. TDD, ATDD and CI in Combined Model
`
`
`
Source Control
Server
Development with
TDD, local build
Development with
TDD, local build
CI Server
Get the latest source code
Tag the stable build
Development with
TDD, local build
Acceptance test
Server
Production
Server
Build Script
Feedbacks
Automated Unit
test
Automated Unit test
(integrated code)
Automated build
Automated
Acceptance test

27. Agile Testing Pyramid
xUnit, SoapUI
Fitnesse
Selenium, Cannoo
Webtest

28. Quality Activities in SCRUM
Unit Test - TDD Continuous IntegrationPair-Programming
Sprint Planning
Sprint Review
Retrospective
ATDD - Acceptance Testing
Planning Poker
Bug Analysis
Coding standard

29. Agile Testing “Manifesto”
 Testing through over at the end.
 Preventing bugs over finding bugs.
 Testing understanding over checking
functionality.
 Building the system over breaking the system.
 Team responsibility for quality over tester
responsibility.

30. The top 12 causes of agile failure
1. Lack of commitment on organizational change or support.
2. Culture doesn't support change.
3. Culture does not have retrospectives or performs them
poorly.
4. Standards and quality are lost in a race to project closing.
5. Lack of collaboration in planning.
6. None or too many Product Owners.

31. The top 12 causes of agile failure
7. Poor project leadership or scrum master
8. No on-site agile promoter or coach.
9. Lack of a well built, high-performance team.
10. Accrued technical debt if strict testing standards are not
upheld.
11. Culture maintains traditional performance appraisals where
individuals are honored and the team aspect is lost.
12. A reversion to the traditional or 'old-way' of doing business
occurs because change is hard

32. Thank You!