Top 7 Myths of Agile Testing - Busted!

1,535 views

Published on

Agile development poses several challenges to effectively testing software. Many myths have become "common wisdom" about how testing is much more difficult, even impossible, in an agile environment. Aricent's software testing experts look at 7 of these myths, and based on their years of experience debunk them.

Published in: Technology
0 Comments
3 Likes
Statistics
Notes
  • Be the first to comment

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

No notes for slide

Top 7 Myths of Agile Testing - Busted!

  1. 1. 7 Myths of Testing in Agile… LIVE WEBINAR June 15th 2010
  2. 2. Aricent GroupThe Aricent Group is a global innovation and technology services company that helps clients to imagine, commercialize, and evolve products and services for the connected world Aricent Testing Services We have more than 15,000 person-years of testing experience and a dedicated team of more than 1,800 testing specialists. With domain expertise in telecom technologies, test tools,automation, and test equipment, we form strategic alliances with our clients. Proprietary & Confidential. ©Aricent Group 2011 2
  3. 3. A Quick Overview of Agile Proprietary & Confidential. ©Aricent Group 2011 3
  4. 4. Agile: What and Why? Agile is an iterative and incremental approach for executing projects in a highly collaborative manner by self-organizing teams to adapt to changing requirements Agile Manifesto Individuals and Working software Customer Responding to interactions over over collaboration over change over processes and comprehensive contract following a plan tools. documentation. negotiation Proprietary & Confidential. ©Aricent Group 2011 4
  5. 5. Agile: What and Why? Requirement Outline Iteration 1 Iteration 2 Iteration 3 Design •Analysis, •A, B •A, B, C •A, B, C, D, Design, E Build Plan Test Release/Deploy Waterfall Model Agile Model • Phased or Gated • Iterative and Incremental • Big up-front analysis/design • Adaptable to requirement changes • Communication through • Communication through individual documentation interactions and working closely Agile helps to Overcome Manage rapidly Manage time- Accelerate wastages of changing bound Improve quality time-to-market software priorities deliverables development Proprietary & Confidential. ©Aricent Group 2011 5
  6. 6. MYTHS OF TESTINGIN AN AGILEENVIRONMENT Proprietary & Confidential. ©Aricent Group 2011 6
  7. 7. Myth 1Agile = Scope is Unmanageable “Market changes influence the requirements too often” “Dynamic development encourages scope creep” Proprietary & Confidential. ©Aricent Group 2011 7
  8. 8. Myth 2Agile = Unsuitable for Distributed Environments “Agile requires co-location of teams, so cannot scale” “Cannot be implemented for remote location delivery ” Proprietary & Confidential. ©Aricent Group 2011 8
  9. 9. Myth 3Agile = Poor Code Coverage “Testing is done on an unfinished product” “Testing and development of code occurs simultaneously” Proprietary & Confidential. ©Aricent Group 2011 9
  10. 10. Myth 4Agile = Test Driven Development “Agile is Test Driven Development (TDD) repackaged” “Agile = XP and XP = TDD, so Agile = TDD” Proprietary & Confidential. ©Aricent Group 2011 10
  11. 11. Myth 5Agile = No Documentation, No Metrics “Agile Manifesto – Working Software over Comprehensive Documentation”“Agile processes consider documentation a hindrance to speed and flexibility” Proprietary & Confidential. ©Aricent Group 2011 11
  12. 12. Myth 6Agile = Compromise in Quality “Since delivery time is less, quality must be poor” “Iterative approach harms product quality” Proprietary & Confidential. ©Aricent Group 2011 12
  13. 13. Myth 7Agile = Over Communication “Co-location of development, testing, and customers creates too many touch-points” “Speed and flexibility of agile processes creates too much noise” Proprietary & Confidential. ©Aricent Group 2011 13
  14. 14. Closing Thoughts Proprietary & Confidential. ©Aricent Group 2011 14
  15. 15. Agile: Evaluate and Adopt METHODOLOGIES PRACTICES • Scrum • Definition of Done (DoD) • Extreme Programming • Test Driven Development • Hybrid Agile (Scrum/XP) • Pair Programming/Testing • Scrumban • Automated Regression Test Suite • Lean • Adaptive Planning/Scrum Scaling • Continuous Integration/Refactoring Succeeding with Agile TOOLS TO USE ENGAGEMENT MODELS • Planning tools: MS Excel, Scrum Works, • Project Nature: R&D, maintenance, ST, Whiteboard deployment testing • CI tools : Hudson, Maven • Team distribution: collocated or • Technical debts: Sonar geographically distributed • Collaboration tools: Wiki, GoToMeeting, SameTime, MS Communicator Proprietary & Confidential. ©Aricent Group 2011 15
  16. 16. We Can Help Success stories across customers of all sizes25-30% reduction in time-to-market Improved productivity and quality20+ certified scrum masters Team empowerment750+ internally trained scrumprofessionals High CSAT Proprietary & Confidential. ©Aricent Group 2011 16
  17. 17. Watch the video and download the full presentation at: http://info.aricent.com/Aricent_Webinar_top-7-myths-of-agile- testing-busted_SS.html For any information, please send your questions to: elizabeth.singh@aricent.com Or Call us at: +1-650-391-1615

×