How Tivoli Provisioning Manager integrated usability testing in Agile - Part 2
DeliaRusu 270000WFUG Visits (1959)
In How Tivoli Provisioning Manager integrated usability testing in Agile - Part 1 we talked about 3 points on how usability testing fits into the development cycle. In part 2, I will be sharing some other points to make this activity successful.
4. We tested “anything”
For example, we tested various designs to validate the general flow of a task from the business perspective. The feedback received from a design validation session helped us determine the right choices to provide. We also tested draft documentation to identify gaps and to validate the effectiveness of search results.
In addition to testing working code and documentation during usability sessions, our team conducts validation sessions for features that are in the design phase. In these sessions, we are gathering feedback from customers from the start. This way, they are helping to shape the product functions.
5. We involved everybody
For all usability sessions, in-person and remote, our team encourages stakeholders to participate in listen-only mode. This process helps the team understand the customer’s perspective because everybody can see where the users are confused and if they are struggling to complete their tasks.
6. We recorded feedback
Our team uses a wiki to store the information that we collect for each sprint, session, and feature tested. We are using IBM Rational Team Concert (RTC) to open defects, to track how many defects have been fixed at any point in time (and for which feature), and to remind us what issues still need to be addressed.
7. We presented results
In the report, we summarize the ratings and overall task success, the positive feedback, and the number of defects opened. We also store this report in the wiki along with the notes from the sess
We took the following actions based on usability issues identified in our testing: