Adapting lightweight user-centered design with the scrum-based development process

Abstract

User-centered design (UCD) 1 addresses the design of interactive systems placing the users in the center of the design with the aim of improving usability and user experience. Developing economies are in dear need of UCD; low IT literacy, low infrastructure and funds; and heterogeneity in culture and livelihood result in special requirements on usability in order to harvest the possible beneTits of IT. Traditional UCD methods, however, are often regarded as heavy-weight and expensive. Agile software development methods are light-weight, Tlexible and iterative in order to accommodate the changing requirements and unsure funding and are therefore important for IT companies in developing economies. Can we adjust UCD methods to Tit the need of developing economies and with agile development while taking advantage of the iterative character of agile development methods? The research appropriated an action research approach called Cooperative Method Development (CMD). Based on the empirical investigation, UCD challenges were identiTied, innovative use of light-weight UCD methods was deliberated and implemented. The improvements include: working with local IT personnel, light-weight and incremental use of personas, support departments performing acceptance testing on release versions, culturally adapted user testing in pairs and heuristic evaluation as adapted UCD practices. The evaluation together with the involved practitioners shows improvements in the development process including reduced reworks; satisTied users; better collaboration with stakeholders; and a close understanding of users and their needs. The evaluation of the resulting integrated approach with the involved practitioners as well as

Setting Requirements for a Dashboard to Inform Portuguese Decision-Makers About Environment Health in an Urban Setting

“…Consistent with prior research (32,59), the user-centered approach allowed the participants to understand the dashboard's aim and easily define the elements and requirements for its design. The participants drew on their professional expertise to critically analyse the data, and were able to collaboratively reach an agreement about the most preferred visualization option for all the indicators and about the critical features to be included in the dashboard.…”

Capturing User Experience of Customer-Centric Software Process through Requirement Process: Systematic Review

“…References Total Agile [41], [42], [43], [44], [45], [46](2), [47], [48](2), [49](3), [50], [51](2), [52](2), [53](2), [54](2), [55], [56], [57](2), [58], [59], [60], [61], [62], [63], [38], [64], [65](2), [66], [67] 28 Scrum [68](1), [69], [70], [48](1), [49](2), [71](1), [54](1), [72], [73](1)…”