Conducting usability testing in agile software development environment
Järvelä, Sakari (2021-06-10)
Järvelä, Sakari
S. Järvelä
10.06.2021
© 2021 Sakari Järvelä. Tämä Kohde on tekijänoikeuden ja/tai lähioikeuksien suojaama. Voit käyttää Kohdetta käyttöösi sovellettavan tekijänoikeutta ja lähioikeuksia koskevan lainsäädännön sallimilla tavoilla. Muunlaista käyttöä varten tarvitset oikeudenhaltijoiden luvan.
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:oulu-202106178505
https://urn.fi/URN:NBN:fi:oulu-202106178505
Tiivistelmä
This Master’s thesis conducted a qualitative approached case study with triangulation to action research for usability testing in Agile software development. First, there was done literature review to create theoretical basis for research. After literature review, the research method was constructed from usability testing methods and qualitative research tools. When research method was explained, the implementation of the research method was opened to tell how the created research method was used. Explained implementation was followed by presenting the findings. Then discussion conducted cohesion between literature, research method, implementation, and findings. Finally, conclusions summarized the main points of the thesis.
Literature review brought up several usability testing methods. Research method formed to use UCD, interview, SUS, and TAP from the usability testing methods that were found. Implementation conducted eight questions for semi structured interview, five tasks for second sprint’s TAP and four tasks for third sprint’s SUS.
It was identified that TAP and SUS can be used in the same usability testing session. Moreover, there were found nine hypotheses to be tested. Eight of those hypotheses were successfully tested. It was also found that action research requires adaption during the research and Agile generates changes in the plans successfully.
Usability testing should be done by using at least one usability testing method and taking end user into test sessions as soon as possible. Semi structured interview’s benefit is to have more open conversation type moment with the test user. TAP achieves descriptive analysis considering how test user experiences usability of the application. SUS offers general usability level of the application in the numeric scale. Improving steps for usability testing can be seen from type of the need for the different usability responses. Another way to identify improvement is to test a new usability testing method. One way to bring usability testing in Agile software development is to conduct usability testing at the end of every sprint.
Literature review brought up several usability testing methods. Research method formed to use UCD, interview, SUS, and TAP from the usability testing methods that were found. Implementation conducted eight questions for semi structured interview, five tasks for second sprint’s TAP and four tasks for third sprint’s SUS.
It was identified that TAP and SUS can be used in the same usability testing session. Moreover, there were found nine hypotheses to be tested. Eight of those hypotheses were successfully tested. It was also found that action research requires adaption during the research and Agile generates changes in the plans successfully.
Usability testing should be done by using at least one usability testing method and taking end user into test sessions as soon as possible. Semi structured interview’s benefit is to have more open conversation type moment with the test user. TAP achieves descriptive analysis considering how test user experiences usability of the application. SUS offers general usability level of the application in the numeric scale. Improving steps for usability testing can be seen from type of the need for the different usability responses. Another way to identify improvement is to test a new usability testing method. One way to bring usability testing in Agile software development is to conduct usability testing at the end of every sprint.
Kokoelmat
- Avoin saatavuus [31657]