Your SlideShare is downloading. ×
Testing in agile projects – case study
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Testing in agile projects – case study

1,023
views

Published on

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

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

Published in: Technology, Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,023
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

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