Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Testing in Agile Projects – Case Study<br />Armands Baranovskis<br />Sanda Linde<br />TietoEnatorAlise<br />
Page 2<br />We are Agile – we don’t need testing!<br />
Page 3<br />Agile Principles<br />Incremental development<br />Delivering a series of (useful, usable) deliveries<br />Ite...
Page 4<br />Case 1<br />
Page 5<br />Case 2<br />
Page 6<br />Case 3<br />
Page 7<br />Case 4<br />
Page 8<br />We are Agile – we don’t need testing!<br />
Page 9<br />Do we?<br />
Page 10<br />How agile does it?<br />
Page 11<br />Agile versus Waterfall<br />
Page 12<br />Benefits<br />Quality of the product is insured at the end of every iteration<br />All team members gain sign...
Page 13<br />Problems<br />Historical stratification among roles<br />Agile is especially hard for testers:<br />Why shoul...
Page 14<br />Testing is a function, not a role.<br />
Thank you.<br />Armands Baranovskis<br />Sanda Linde<br />TietoEnator Alise<br />www.alise.lv<br />
Upcoming SlideShare
Loading in …5
×

Testing in agile projects – case study

1,539 views

Published on

Presentation for 10th Annual Conference for Software Testing Professionals in Riga, Latvia, 2009

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Testing in agile projects – case study

  1. 1. Testing in Agile Projects – Case Study<br />Armands Baranovskis<br />Sanda Linde<br />TietoEnatorAlise<br />
  2. 2. Page 2<br />We are Agile – we don’t need testing!<br />
  3. 3. Page 3<br />Agile Principles<br />Incremental development<br />Delivering a series of (useful, usable) deliveries<br />Iterative development<br />Allowing requirements to evolve and be added to<br />Responding quickly to new business priorities<br />People-oriented development<br />People’s qualities rather than heavy process<br />Allowing the agile team to manage themselves<br />Daily interactions between developers and the business<br />Technical excellence and built-in quality<br />Personal responsibility, craftsmanship and simplicity<br />Lean approach<br />Measure progress by delivered product<br />Minimize waste<br />
  4. 4. Page 4<br />Case 1<br />
  5. 5. Page 5<br />Case 2<br />
  6. 6. Page 6<br />Case 3<br />
  7. 7. Page 7<br />Case 4<br />
  8. 8. Page 8<br />We are Agile – we don’t need testing!<br />
  9. 9. Page 9<br />Do we?<br />
  10. 10. Page 10<br />How agile does it?<br />
  11. 11. Page 11<br />Agile versus Waterfall<br />
  12. 12. Page 12<br />Benefits<br />Quality of the product is insured at the end of every iteration<br />All team members gain significant business knowledge<br />All team members are multifunctional<br />Both, project team and client, have more impact on the product and the outcome<br />Satisfied client due to transparency and trust<br />Less is more<br />
  13. 13. Page 13<br />Problems<br />Historical stratification among roles<br />Agile is especially hard for testers:<br />Why should I test something that isn’t ready?<br />Why should I do someone else's job?<br />How can I test without documentation?<br />Agile demands high individual and team discipline and initiatives<br />
  14. 14. Page 14<br />Testing is a function, not a role.<br />
  15. 15. Thank you.<br />Armands Baranovskis<br />Sanda Linde<br />TietoEnator Alise<br />www.alise.lv<br />

×