Agile vs Waterfall From A Tester's Eyes by Shweta Parashar & Abhishek Agrawal
•Als PPT, PDF herunterladen•
0 gefällt mir•1,886 views
The document compares the Agile and Waterfall development methodologies from a tester's perspective. It notes that Waterfall can result in bugs being called features, documentation overhead, and information loss over time. Agile focuses on individuals, working software, customer collaboration, and response to change. Following Agile results in developer, tester, and client happiness, while Waterfall often leaves the client unhappy. Agile involves testers more closely in the development process from the start.
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (7)
Ähnlich wie Agile vs Waterfall From A Tester's Eyes by Shweta Parashar & Abhishek Agrawal
Ähnlich wie Agile vs Waterfall From A Tester's Eyes by Shweta Parashar & Abhishek Agrawal (20)
Mehr von Xebia IT Architects
Mehr von Xebia IT Architects (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Agile vs Waterfall From A Tester's Eyes by Shweta Parashar & Abhishek Agrawal
- 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
- 7. Waterfall Way Developer happy Tester happy Client Unhappy
- 8. Agile Way Developer happy Tester happy Client happy
- 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 ???
Hinweis der Redaktion
- 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)