Elsevier

Entertainment Computing

Volume 5, Issue 4, December 2014, Pages 335-345
Entertainment Computing

Gamifying requirement elicitation: Practical implications and outcomes in improving stakeholders collaboration

https://doi.org/10.1016/j.entcom.2014.04.002Get rights and content

Highlights

  • The paper aims to evaluate effectiveness, acceptance of collaborative.

  • Two field studies showed a successful discussion of stakeholders towards requirements.

  • The use of Six Thinking Hats method aided guiding stakeholders’ discussion towards relevant perspectives of elicited requirement.

  • In the field studies, project managers reported high degree of satisfaction on amount and quality of generated requirements.

  • The amount of valid requirements and requirements feedback was reported to be similar or better than using traditional tools.

Abstract

The requirements engineering process is a key phase of the Information System development since it determines its functionalities and its operation. Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user or stakeholder by just asking them what the system should do. Requirements elicitation practices include interviews, questionnaires, user observation, workshops, brainstorming, use cases, role playing and prototyping. However, these common procedures are still prone to be ambiguous or incorrect which can lead the Information Systems to failure. It is consensual that one of the major problem of this activity relates to the communication and collaboration between different and distant stakeholders. Thus, recent studies have been proposing web collaborative tools to gather these stakeholders in order to elicit requirements. The paper aims to evaluate the effectiveness and acceptance of such a collaborative tool which was developed by using a gamification approach and the Six Thinking Hats method. The document also makes a discussion of the implication and outcomes of improving stakeholders collaboration.

Introduction

Today we live in an Information Age where people rely on computers and technology to work, socialize or live [1], [2]. This technology quite often comes to us through Information Systems. Building such systems is usually a complex and difficult task, demanding a significant effort on planning and managing their development process. Therefore, system designers and developers use the System Development Life Cycle (SDLC) framework which breaks down the development process into a pipeline of activities. Several SDLC models have been created (waterfall, fountain, rapid prototyping, incremental, etc.) but all of them have the requirements elicitation activity as the earliest stage in the pipeline. Before requirements can be analyzed, modeled, or specified they must be gathered through an elicitation process. The aim here is to understand and define how the system will operate [4]. Requirements elicitation is based on an intense communication between stakeholders and between stakeholders and analysts. Therefore, cooperation and collaboration are vital in this process [5]. Requirements elicitation is non-trivial because you can never be sure you get all requirements from the user or stakeholder by just asking them what the system should do. Several studies have been conducted with the goal of edifying common limitations in this process, mainly aiming at understanding the role of communication, collaboration and cooperation between stakeholders. Nevertheless, despite of the research efforts, it still remains unclear how to overcome limitations that can account for 60–70% of projects that fail to deliver on time, on cost and with the scope originally promised [3], costing around 80–100 times more if discovered at the implementation stage and are very hard to fix [4].

Since communication is critical, requirement elicitation tools must ease this communication between stakeholders in order to articulate their needs collaboratively, allowing their meetings even at a different time and place to discuss those needs. In this context, game-based tools can bring numerous benefits to this process since they typically provide immediate feedback, active participation and the high motivation promoted by the competitive environment [5], [6], [7].

Recent research as proved the benefits of adding game mechanics to common tasks outside the traditional video games environments [8], including motivational benefits to participate in online communities. This approach is commonly referred in the literature as “gamification”, a concept that is already used in numerous applications ranging across productivity, finance, health, education, sustainability, as well as news and entertainment media [9].

The paper aims to evaluate the effectiveness and acceptance of iThink system [13], a RE tool, which was developed by using a gamification approach and the Six Thinking Hats method. The document also makes a discussion of the implication and outcomes of improving stakeholders collaboration. The evaluation was based on Action Research in real world organizations: Action Research allowed us contributing with practical actions on the organization and generating knowledge about its context on the real world situations. We performed two Action Research cycles: we studied the problematic situation of the first environment, applied an action, evaluated the results and extracted lessons learnt. In the second cycle we also studied the situation taking into account the lessons learnt from the first cycle, applied an action with iThink, evaluated the results and extracted other lessons [10], [11].

Section snippets

Requirements elicitation

As stated by Avison and Fitzgerald [4], “the definition of requirements can be problematic, but in relation to information systems, it can be said to be everything that the set of relevant stakeholders want from a system”. Requirements are, indeed, the key information in Information Systems Development: they translate stakeholders’ needs, determining what and how the Information System will operate [12], [13].

Despite many years of computing and research efforts in the requirements elicitation

Gamification

Serious games and virtual-based environments are an important response from the technologist to the “digital natives” [36], [37], a generation who were raised on interactive games and expect the same kind of interactive experiences in every information system. Indeed, it may not be entirely correct to call the use of serious games a novelty, since by nature young children begin to gain interest in several topics through games during their earlier years [38].

The field of business is not an

Requirements elicitation with visualization techniques

Before our game-based studies, our previous web-based Focus Groups [23], [24] were successful on eliciting requirements from distant stakeholders. Those Focus Groups promoted discussion towards relevant issues in order to formalize requirements for an outdated Information System. Moreover, all stakeholders could participate in this discussion and not only key stakeholders, which allowed being more confident on the results. Nevertheless, the participation rate was not satisfactory. Therefore, we

iThink

iThink is a web-based gamified environment designed for supporting collaborative requirement elicitation. By combining several game mechanics with the use of a creative thinking technique, called “The Six Thinking Hats” [62], it attempts to tackle the collaboration and user involvement problems previously described. iThink presents to the user, the requirement elicitation process as a game, through which the player is rewarded not only by the generations of new requirements, but also by the

Case studies

iThink is a web-based gamified environment designed for supporting collaborative requirement elicitation. By combining several game mechanics with the use of a creative thinking technique, called “The Six Thinking Hats” [62], it attempts to tackle the collaboration and user involvement problems previously described. iThink presents to the user, the requirement elicitation process as a game, through which the player is rewarded not only by the generations of new requirements, but also by the

Results

In order to obtain some feedback on the game and on the information that resulted from the game two different questionnaires were made, the first was directed to the players and the second was aimed at the project manager.

Discussion

iThink emerged from our previous studies [66], [67]. These studies advanced with requirements elicitation challenges, namely stakeholders’ difficulties articulating and recognizing own needs; stakeholders’ conflicts of interests; and analysts’ misinterpretations. Beginning with a regular Focus Group to better elicit requirements, we then moved to web based Focus Groups. With these studies, we identified a number of techniques and features that should be part of the discussion to ease

Limitations

Our research is a qualitative research and, therefore, it lacks statistical significance, hypotheses, a control group, of systematic choice of subjects, experts and projects. Actually, we followed triangulation to validate our qualitative research. Therefore, we used two sources of studies of the same phenomenon to evaluate different data and environments. The different data concern different stakeholders and different research topics. The different environment concern different locations of

Conclusion

This paper presents two case studies aimed at evaluating a requirement elicitation tool based on gamification concepts and the Six Thinking Hats method. These case studies were successful in promoting discussion of stakeholders towards requirements. Consequently, several requirements were orderly elicited as well as arguments that support and refute those requirements. Moreover, the results demonstrate a good number of contributions and that this approach may enhance the user involvement in

Acknowledgments

This work was supported by the Portuguese Fundação para a Ciência e a Tecnologia (INESC-ID multiannual funding) under the project PEst-OE/EEI/LA0021/2013. The authors also would like to acknowledge to the European funded Project Games and Learning Alliance (FP7 258169) the Network of Excellence (NoE) on Serious Games.

References (67)

  • S. Deterding, R. Khaled, L. Nacke, D. Dixon, Gamification: toward a definition, in: CHI 2011 Gamification Workshop...
  • S. Deterding et al.

    From game design elements to gamefulness: defining gamification

  • V. Koshy

    Action Research for Improving Practice: A Practical Guide

    (2005)
  • M. Brydon-Miller et al.

    Why action research?

    Action Res.

    (2003)
  • B. Davey et al.

    Requirements elicitation – what’s missing?

    Issues Inf. Sci. Inf. Technol.

    (2008)
  • D. Zowghi et al.

    Requirements elicitation: a survey of techniques, approaches, and tools

    Eng. Managing Softw. Requir.

    (2005)
  • I. Sommerville

    Software Engineering

    (2001)
  • J. Coughlan et al.

    Focus Groups: A Practical Guide for Applied Research

    (2002)
  • J.A. Goguen et al.

    Techniques for requirements elicitation

    Requir. Eng. IEEE Comput. Soc.

    (1993)
  • A. Crabtree et al.

    Ethnomethodologically-informed ethnography and information system design

    J. Am. Soc. Inf. Sci.

    (2000)
  • A. Crabtree, Ethnography in participatory design, in: Participatory Design Conference Seattle, 1998, pp....
  • N. Maiden et al.

    Requirements engineering as creative problem solving: a research agenda for idea finding

    Requir. Eng.

    (2010)
  • L. Pennell, N. Maiden, Creating requirements – techniques and experiences in the policing domain,...
  • D. Morgan

    The Focus Group Guidebook, Focus Group Kit

    (1997)
  • C. Farinha, M.M.d. Silva, Requirements elicitation with web-based focus groups,...
  • C. Farinha, M.M.d. Silva, Web-based focus groups for requirements elicitation, in: Sixth International Conference on...
  • J. Whitehead, Collaboration in software engineering: a roadmap, in: Future of Software Engineering, 2007. FOSE ’07,...
  • S.L. Lim, D. Damian, A. Finkelstein, Stakesource2.0: Using social networks of stakeholders to identify and prioritise...
  • D. Yang, D. Wu, S. Koolmanojwong, A.W. Brown, B.W. Boehm, Wikiwinwin: a wiki based system for collaborative...
  • S. Lohmann, J. Ziegler, P. Heim, Involving end users in distributed requirements engineering, in: Proceedings of the...
  • E. Knauss, I.K.O. Brill, T. Flohr, Smartwiki: Support for high-quality requirements engineering in a collaborative...
  • C. Solis, N. Ali, Distributed requirements elicitation using a spatial hypertext wiki, in: 5th IEEE International...
  • R. Asarnusch, M. David, W. Jan, B. Astrid, Visual requirement specification in end-user participation, in: Proceedings...
  • Cited by (34)

    • How games induce cooperation? A study on the relationship between game features and we-intentions in an augmented reality game

      2017, Computers in Human Behavior
      Citation Excerpt :

      Concerning video games, it can be observed that, in many games, cooperation emerges effortlessly; people start to pool individual efforts, cooperate seamlessly even against the most unimaginable odds, and express strong enthusiasm while acting together (Chen, Sun, & Hsieh, 2008; Cole & Griffiths, 2007; Ducheneaut, Yee, Nickell, & Moore, 2006; Scharkow, Festl, Vogelgesang, & Quandt, 2015; Teng & Chen, 2014; Yee, 2006). Thus, today, practitioners turn to games for inspiration on how to design information systems, services, and organizational structures more cooperatively (Bui, Veit, & Webster, 2015; Morschheuser, Maedche, & Walter, 2017; Ribeiro, Farinha, Pereira, & Mira da Silva, 2014; Schacht, & Maedche 2015; Thom, Millen, Dimicco, & Street, 2012). This trend can be understood as part of the gamification movement, which represents the use of game elements and mechanics outside traditional video game environments (Hamari, Koivisto, & Sarsa, 2014; Huotari & Hamari, 2017).

    • Knowledge meaning and management in requirements engineering

      2017, International Journal of Information Management
      Citation Excerpt :

      The third approach is supported by methods associated with dynamic–game techniques (gamification), empowered by the use of agile software development methodologies and frameworks. The latter are founded on the fact that elicitation is not a trivial process because it cannot be guaranteed that all requirements are obtained in the interaction with the interested parties, when one simply considers questions related to what the system to be developed is expected to do (Ribeiro, Farinha, Pereira, & Mira, 2014). In addition, the process of communication and knowledge transfer can become a problem in requirements engineering because the cultural, temporal, geographic and socio-economic diversity of the interested parties are obstacles that must be overcome (Ghanbari, Simila, & Markkula, 2015).

    • Using gamification to transform the adoption of servitization

      2017, Industrial Marketing Management
      Citation Excerpt :

      As a result, the structural role of internal research staff and external user communities can be transformed, with internal employees taking care of mundane tasks (e.g. documentation) and customers/contributors having a rewarding, enjoyable and creative experience (Raasch & von Hipple, 2013). Furthermore, Ribeiro, Farinha, Pereira, and Mira da Silva (2014) suggest that, in terms of promoting social interactions, gamification can help to improve the process of requirement engineering by enabling better collaboration between different, distant stakeholders. The benefits of integrating user engagement into value chains, from user-led innovation to user-generated content, can be significant (Deterding, 2015).

    View all citing articles on Scopus

    This paper has been recommended for acceptance by Matthias Rauterberg.

    View full text