Professional Documents
Culture Documents
Explained
jean.tabaka@rallydev.com
Slide 2
Slide 3
zhttp://agilemanifesto.org/principles.html
Slide 5
Slide 6
PM
Process
Critical
Path through
Phases
Iterative
Iterative and
Incremental
Parallel
Acceptance
Test Driven
Critical
Drop
Schedule
Time Boxes
Continuous
Flow
Automated
Flow
Requirements
& Design
Process
Phase 2
Phase 2
Detailed
Design
Inside
Iteration
Just-in-time
Elaboration
Acceptance
Test Cases
Development
Process
Phase 3
All Features
in Parallel
Multiple
Drops to QA
Increment
at a time
DesignBuild-Test
Test
Design Build
Phase 4
only
Drops in
Phase 3
Acceptance
Test Inside
the Iteration
Failing Test
Cases as
Defects
By
Exception
Slide 7
Slide 8
Slide 9
Accept
Iteration N-1
Accept
Detailed Iteration
Planning & Design
Prepare for
features
and tests
Dev Feature
Dev Feature
Priority 1
Priority 4
Auto. Tests
Auto. Tests
Feature 1
Feature 4
Dev Feature
Dev Feature
Priority 2
Priority 5
Auto. Tests
Auto. Tests
Feature 2
Feature 5
Dev Feature
Priority 3
Auto. Tests
Feature 3
Iteration N+1
Iteration N
Manual GUI
Acceptance
Tests
Automated
GUI Tests
Unit
Tests
Slide 10
Easy to Create
Very familiar what we always do
Typically tedious
How do we know coverage?
Automation good for performance
Need Automation specialists
Seems like we always rewrite
Sometimes fragile
What is Dev testing?
How do we know what these are?
Dev resistance to writing tests
Manual GUI
Acceptance
Tests
Automated
GUI Tests
& FitNesse
Unit Tests
Slide 11
Increased Coverage
Features under test more stable
Slide 12
Frequent builds
Continuous integration
Without continuous testing, we never truly know
where we stand, how much work is left to do
Slide 14
Slide 15
Feature
Iteration
Release
Slide 16
Slide 17
Slide 18
Slide 19
Slide 20
10
Unit tests
Automated test suites
Full regression tests
4. You find ways to work that dont require such long delays
before development work is tested
Slide 21
www.fitnesse.org
Slide 22
11
doneness criteria
Testing helps elaborate requirements and makes
sure they are testable
Testers find holes in the requirements prior to start
of development
Test and dev sit together to elaborate the tests
Lisa Crispin The whole team approach is critical.
XP Testers Bill of Rights http://home.att.net/~lisa.crispin/XPTesterBOR.htm
Assign a team to each story to determine testing
Slide 23
12
Slide 25
development is Done.
7. We commit to not allowing surprises to accumulate
for large end-to-end testing (mock it now).
8. We commit to not leaving the riskiest tests to the
end.
9. We commit to being an equal participant with the
customer and the developer in defining Doneness.
10.We commit to not taking this oath lightly, i.e. no
AUI!
Slide 26
13
Slide 27
Thank you
jean.tabaka@rallydev.com
Copyright
Slide 28 2003-2005, Rally Software
Copyright
Development
2007, Rally
CorpSoftware Development Corp
14