«From Waterfall to Agile/Scrum: the impact on testing»

1,420 views
1,163 views

Published on

by Oksana Vey

Published in: Software, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,420
On SlideShare
0
From Embeds
0
Number of Embeds
10
Actions
Shares
0
Downloads
14
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

«From Waterfall to Agile/Scrum: the impact on testing»

  1. 1. FROM WATERFALL TO AGILE/SCRUM: IMPACT ON TESTING
  2. 2. TRADITIONAL DEVELOPMENT • KNOWING EVERYTHING • FIXED REQUIREMENTS, ESTIMATES AND RESOURCES • FREEZING REQUIREMENTS • STATUS MEASURED • WORKING SOFTWARE AT THE END OF DEVELOPMENT LIFECYCLE
  3. 3. AGILE METHODOLOGIES Process and Tools Comprehensive Documentation Following Plan Contract Negotiation Individuals & Interaction Working Software Responding to Change Customer Collaboration Teamwork and Responsibility Business value Partnership Elaboration Prepare for Change TRADITIONALDEVELOPMEN
  4. 4. MANAGEMENT Traditional DevelopmentAgile/SCRUM Command and Control Collaborativ e Leadership
  5. 5. TEST MANAGER Traditional DevelopmentAgile/SCRUM Test Strategy Test Plan Product Risks Test Estimatio n Resourc es ... Planning & estimatio n Detailed Product risks Analysis How to get right tester? How to keep testing knowledge up-to-date? Info out of the team – eye view on testing process …
  6. 6. TESTER Traditional DevelopmentAgile/SCRUM Requirements analysis Test Documentatio n Requiremen ts Analysis Communicati on Testing Estimating Test Documentati on Testing/ Regression/ Automation …
  7. 7. CHANGING ROLE OF TESTER Traditional DevelopmentAgile/SCRUM  Work in team of testing prof’s  Role predominantly involves testing  Last line of defense for software quality  Test case prepared from well documented req’s and designs  Clearly defined entry and exit criteria  Work in cross functional team of analysts, developers, testers …  Expanded role - design def/review, write/review code and testing  Quality responsibility of entire sprint team  Test cases prepared from user stories, req. & design discussions, minimal docs  Testing is collaborative effort with other functions, no phase gate
  8. 8. CHANGING ROLE OF TESTER Traditional DevelopmentAgile/SCRUM  Test execution after code complete  Testing essentially Top-Down  Minimal involvement in Unit testing  System level Automation test scripts, after code is stabilized  Report progress by testing phase  Iterative testing by feature and not entire project  Testing essentially Bottom-Up  Active participation in Unit testing  Automation from unit testing level  Report progress by Feature complete rather than testing completion
  9. 9. KEY SUCCESS FACTOR  Test in small but do not lose sight of big picture  Ability to work in team and to get things dove  Communication and Collaboration  Comfortable with speed and just in time delivery  Design and Coding skills, at minimum - good analytical and review s  Minimal reliance on documentary support  Focus on project deliverable, not on phase deliverables
  10. 10. QUESTIONS ? Thank You! Any Questions?

×