Qa Going Agile Sharing The Experience

619 views
548 views

Published on

Qa Going Agile Sharing The Experience

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
619
On SlideShare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Qa Going Agile Sharing The Experience

  1. 1. Going Agile: Sharing the Experience Anat Karsch QA Manager, IBM Software
  2. 2. The QA Group <ul><li>9 team members in Israel, 2 in China </li></ul><ul><li>Two projects. One co-located, one Israel/China </li></ul><ul><li>Most of the team doing manual testing </li></ul><ul><li>Some are doing automated testing </li></ul>
  3. 3. The Projects <ul><li>Metadata Workbench & Business Glossary - Metadata Tools - Metadata Tools </li></ul><ul><li>Products are web application (running on WebSphere) </li></ul><ul><li>Mostly Java based. One product has a .NET client </li></ul><ul><li>Different database on multiple platforms </li></ul><ul><li>One product is for the business user, the other one, more complicated and intended for the technical user. </li></ul>
  4. 4. Motivation – Why Agile? <ul><li>Camelot </li></ul><ul><li>- Waterfall project - Dev task planned for 3 month - 6 month and still no QA… </li></ul><ul><li>Pandora Box </li></ul><ul><li>Project died… </li></ul>
  5. 5. How we’re implementing Agile <ul><li>PDM suggests scope based on stake holders </li></ul><ul><li>QA involved from planning phase </li></ul><ul><li>Specs and Solution doc with User Stories </li></ul><ul><li>3 weeks iterations </li></ul><ul><li>QA write test plan </li></ul><ul><li>Dev write unit tests </li></ul><ul><li>Continuous Integration - Unit tests run after each check-in - Nightly builds </li></ul>
  6. 6. How we’re implementing Agile – Cont. <ul><li>Manual FVT and SVT </li></ul><ul><li>Automated testing: - Rational Functional Tester (RFT) for UI Automation - in-house eclipse based plug-in </li></ul><ul><li>Scrum meetings </li></ul><ul><li>RTC to manage user stories, defects, task and burn rate </li></ul><ul><li>Reflection </li></ul><ul><li>Coffee mug testing </li></ul><ul><li>Stabilization - dev helps with FVT and defect verification </li></ul>
  7. 7. Iteration Plan in Rational Team Concert (RTC)
  8. 8. What didn’t work <ul><li>Self managed teams – not by the book </li></ul><ul><li>ID was not involved properly </li></ul><ul><li>Features were not complete for the reflection </li></ul><ul><li>Technical debt from sprint to sprint </li></ul><ul><li>Not enough automated tests </li></ul><ul><li>UI Automation was not in the same sprint </li></ul>
  9. 9. Challenges or What needs to be addressed… <ul><li>Legacy </li></ul><ul><li>Patches, Translation Testing and other releases </li></ul><ul><li>Gaps due to other tasks </li></ul><ul><li>Performance </li></ul><ul><li>Integration with other components </li></ul><ul><li>Need in more automation and earlier </li></ul><ul><li>Better integration with ID </li></ul><ul><li>Looking into integrating RQM and RTLM in Agile testing </li></ul>
  10. 10. What has changed in the group? <ul><li>Team collaboration - One team within QA and within Dev </li></ul><ul><li>Responsibility </li></ul><ul><li>High visibility and communication </li></ul><ul><li>Better understanding of the product </li></ul><ul><li>A more balanced work load and defect backlog </li></ul><ul><li>Better Quality! </li></ul><ul><li>The goal is not to BE Agile . </li></ul><ul><li>The goal is to USE Agile in order to get a better product </li></ul>
  11. 11. And trust me on the sunscreen… Thank You!

×