• Like
Agile vs Waterfall From A Tester's Eyes by Shweta Parashar & Abhishek Agrawal
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Agile vs Waterfall From A Tester's Eyes by Shweta Parashar & Abhishek Agrawal

  • 2,322 views
Published

AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This …

AgileNCR 2010 conference was held in Gurgaon on 17th & 18th July 2010. This largest community driven conference was the Fourth edition of Agile NCR and was organized in collaboration with ASCI. This time the event was based on four major themes : 'Agile for newbies', ' Agile Adoption Challenges', 'Workshops and Software Craftsmanship', and ' Post Agile'.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,322
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
45
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
  • Waterfall has the famous - "Developer vs Tester" and "Bug vs Feature" war whereas, Agile sees a lot of "developer-tester" pairing and an environment of harmony (Good for companies as it leads to lesser number of broken furniture and broken bones!!)
  • Documentation overhead in waterfall (P1 vs P2 SLC, 1.0.2.5.6.bla.bla) vs common-sense prioritization in Agile
  • Waterfall testing is just one phase, towards the end of the project by which time, everyone is anyways too bored to make any changes, whereas Agile testing in an integral part of the development process
  • Waterfall testing has a goal of scoring brownie points by finding bugs or marking maximum stories "ok - tested" On the contrary, agile testing has a goal of ensuring the product is shipped in a high quality and with all features
  • Waterfall has the famous - "Developer vs Tester" and "Bug vs Feature" war whereas, Agile sees a lot of "developer-tester" pairing and an environment of harmony (Good for companies as it leads to lesser number of broken furniture and broken bones!!)
  • Waterfall only gives u water, Agile gives you bear!!!! (you celebrate success every 2 weeks)

Transcript

  • 1. Agile vs Waterfall From A Tester's Eyes AGILE NCR 2010
  • 2. Waterfall: Bug !! - No its a feature . . .
  • 3. Documentation Overhead
  • 4. Information Loss: Chinese Whispers
  • 5. Contrast
  • 6. Agile Manifesto , a quick recap . . .
    • Individuals and interactions over processes and tools
    • Working software over comprehensive documentation
    • Customer collaboration over contract negotiation
    • Responding to change over following a plan
  • 7. Waterfall Way Developer happy Tester happy Client Unhappy
  • 8. Agile Way Developer happy Tester happy Client happy
  • 9. Role Reversal
        • Tester, the eyes of PO
  • 10. Higher Client Involvement Tester needs more inputs from the client
  • 11. Waterfall: Testing is Just one Phase
  • 12. Agile: Tester, an integral part of Development Process Tester closely observes the developments in the project all the time and hence there are no surprises 5 minutes before the release
  • 13. Towards Developer – QA Harmony . . .
  • 14. Agile: Pairing
  • 15. Water or Beer ??
  • 16. Questions ???