15. AGILE MANIFESTO 2.1
Teamwork & responsibility over Individuals and Interaction - You
need great individuals and the better they interact the better it is.
Business Value over Working software - Software in itself has no
value. Its what you do with it.
Partnership elaboration over Customer collaboration - Collaborating
with your customer is important, but working on a partnership is better.
Prepare for change over Respond to Change - Its even stronger to
create a setting where change is normal.
32. C O L L A BO R ATI O N W I TH
DEVELOPERS
Testing earlier, sometimes on
their machines
Developers gain insight into
potential problems
Developer
Together can succeed with
automated testing
Reuse unit testing frameworks
Tester Do acceptance tests in the
same programming
environment
33. Use checklists and testing dashboards
if you have no time for detailed test
cases
34. Assign testing tasks to
Developer
Not sure if it is good decision in our Reality
35. How defects are managed
Defects within the Iteration
On the fly
Defect on a story, after the
story is signed off
Prioritize and play the story
Add a test
Significant misunderstanding in
how the functionality was
intended to work
Create a new story and
prioritize
36. Agile Testing Success Factors
Testers are part of Be cathedral builders not stone cutters
the team Collective ownership
Drop the Quality Police mindset
Agile testing mindset Focus on team goals & customer value
Automate tests wherever practical
Automate tests Need rapid feedback
Balance against developer focus on
Look at the big technical implementation
picture Use agile test matrix as guide
37. Agile Testing Success Factors
Collaborate with customers
Collaborate Collaborate with BA
Collaborate with Customer
Team retrospectives
Continually improve Personal training: reading, blogs, QAI, local
QA groups