Integrating Agile and User-Centered Design: a Systematic Mapping and Review of Evaluation and Validation Studies of Agile-UX
Total Page:16
File Type:pdf, Size:1020Kb

Load more
Recommended publications
-
User Psychology of Emotional User Experience JYVÄSKYLÄ STUDIES in COMPUTING 213
JYVÄSKYLÄ STUDIES IN COMPUTING 213 Jussi P. P. Jokinen User Psychology of Emotional User Experience JYVÄSKYLÄ STUDIES IN COMPUTING 213 Jussi P. P. Jokinen User Psychology of Emotional User Experience Esitetään Jyväskylän yliopiston informaatioteknologian tiedekunnan suostumuksella julkisesti tarkastettavaksi yliopiston Agora-rakennuksen auditoriossa 2 kesäkuun 6. päivänä 2015 kello 12. Academic dissertation to be publicly discussed, by permission of the Faculty of Information Technology of the University of Jyväskylä, in building Agora, auditorium 2, on June 6, 2015 at 12 o’clock noon. UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2015 User Psychology of Emotional User Experience JYVÄSKYLÄ STUDIES IN COMPUTING 213 Jussi P. P. Jokinen User Psychology of Emotional User Experience UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2015 Editors Marja-Leena Rantalainen Department of Mathematical Information Technology, University of Jyväskylä Pekka Olsbo, Ville Korkiakangas Publishing Unit, University Library of Jyväskylä Cover picture: CC-BY-SA by Jussi Jokinen from following images: Coghead: CC-0 Cellphone icon: CC-BY-SA WZ Computer icon: CC-BY-SA Carlosdevivo URN:ISBN:978-951-39-6225-8 ISBN 978-951-39-6225-8 (PDF) ISBN 978-951-39-6224-1 (nid.) ISSN 1456-5390 Copyright © 2015, by University of Jyväskylä Jyväskylä University Printing House, Jyväskylä 2015 “For all men begin, as we said, by wondering that things are as they are, as they do about self-moving marionettes, or about the solstices or the incommensura- bility of the diagonal of a square with the side; for it seems wonderful to all who have not yet seen the reason, that there is a thing which cannot be meas- ured even by the smallest unit.” (Aristotle, Metaphysics, 983a15) ABSTRACT Jokinen, Jussi P. -
A Glossary of User-Centered Design Strategies for Implemen- Tation Experts
TBM ORIGINAL RESEARCH A glossary of user-centered design strategies for implemen- Downloaded from https://academic.oup.com/tbm/advance-article-abstract/doi/10.1093/tbm/iby119/5232646 by guest on 07 December 2018 tation experts Alex R. Dopp,1, Kathryn E. Parisi,1 Sean A. Munson,2 Aaron R. Lyon3 1Department of Psychological Abstract Science, University of Arkansas, User-centered design (UCD), a discipline that seeks to ground Implications Fayetteville, AR 72701, USA the design of an innovation in information about the people 2 Practice: Use of shared language around user-cen- Department of Human Centered who will ultimately use that innovation, has great potential tered design (as presented in this glossary) can Design and Engineering, University of Washington, Seattle, WA to improve the translation of evidence-based practices from maximize the usefulness of interdisciplinary 98195, USA behavioral medicine research for implementation in health care efforts to promote the implementation of evi- 3Department of Psychiatry and settings. UCD is a diverse, innovative field that remains highly dence-based practices through improved design. Behavioral Sciences, University of variable in terms of language and approaches. Ultimately, we Washington School of Medicine, produced a glossary of UCD-related strategies specifically for Seattle, WA 98195, USA experts in implementation research and practice, with the goal Policy: Policymakers who wish to promote a of promoting interdisciplinary collaboration in implementation user-centered culture in health services should efforts. We conducted a focused literature review to identify consider the value of tools like this glossary in key concepts and specific strategies of UCD to translate into developing shared language and interdisciplinary the implementation field. -
Games User Research and Physiological Game Evaluation
Chapter 4 Games User Research and Physiological Game Evaluation Lennart E. Nacke Abstract This chapter introduces physiological measures for game evaluation in the context of games user research (GUR). GUR consists of more than playtest- ing game; it comprises a collection of methods that allow designers to bring their creations closer to the initial vision of the player experience. With the prices of physiological sensors falling, and the advancement of research in this area, physi- ological evaluation will soon become a standard tool in GUR and game evaluation. Since mixed-method approaches are of increasingly prominent value, this chap- ter describes core GUR methods with a special focus on physiological evaluation, keeping in mind both benefits and limitations of the approach in academic and industrial applications. 4.1 Introduction From the academic domains of human-computer interaction, human factors, and social psychology, robust and scientific user-testing approaches have been adopted in a game industry field called games user research (GUR) to ensure optimal qual- ity of the user experience (UX) in games and virtual entertainment products. In the games industry, the domains of quality assurance (QA) and game testing are focus- ing on finding technical errors in the game code (i.e., bugs) and ensuring smooth execution of the game on a technical level. By contrast, GUR is concerned with evaluation through the observation and analysis of players. A game designer com- municates their thoughts to the player using the game. In turn, the user researcher applies methods that are inspired by psychology and user-centered design to evalu- ate the player. -
Interaction Design Studio - 711 Instructor: Patrick Thornton Email: [email protected] Thursday 6-8:45 Pm Location: Pac 1815 - Clarice Smith Performing Arts Center
Interaction Design Studio - 711 Instructor: Patrick Thornton Email: [email protected] Thursday 6-8:45 pm Location: Pac 1815 - Clarice Smith Performing Arts Center Course Description Interaction design is the process of defining products and the broad services built around them. When interacting with systems, people build expectations and mental models of how things work. They learn what they can and cannot achieve. This course is about how to design for interactions that will resonate with your audiences: How the features and functions of a product get translated into something people find usable, useful, and desirable. Through a series of lectures, discussions, in-class design practice, and projects, students will explore the role of interaction designers. Students will learn how to prototype interactive products, systems, and services, and how to defend their work through the cycle of brainstorming and shared critique. This is a studio class, focusing on production processes that are required to develop public-facing work. The studio is important both as a working space and a space for collaborative reflection. Studio practice also describes a working method. As such, the INST711 classroom will focus on two activities: ● Externalization: You will put your ideas and conceptualizations into tangible materials. ● Critique: You will both give and receive constructive feedback on your own work and the work of other students in class. Student Learning Outcomes On the successful completion of this course, students will be able to: ● Explain basic concepts, techniques, and knowledge of interaction design. ● Critically discuss common methods in the interaction design process ● Use visual thinking and communication techniques to develop design concepts ● Build prototypes at varying levels of fidelity and can evaluate them using appropriate methods ● Develop critiquing skills to analyze interaction design artifacts and concept design. -
User Interaction Design for Secure Systems
User Interaction Design for Secure Systems Ka-Ping Yee Report No. UCB/CSD-02-1184 May 2002 Computer Science Division (EECS) University of California Berkeley, California 94720 Supported by NSF award #EIA-0122599 ITR/SI: Societal Scale Information Systems: Technologies, Design and Applications User Interaction Design for Secure Systems Ka-Ping Yee [email protected] Computer Science Department University of California, Berkeley Abstract Perhaps the most spectacular class of recent security problems is the e-mail virus, which is a good real-life The security of any computer system that is configured example of a security violation in the absence of software and operated by human beings critically depends on the errors. At no point in the propagation of the virus does information conveyed by the user interface, the decisions any application or system software do anything other of the computer users, and the interpretation of their than exactly what its programmers would expect: the e- actions. We establish some starting points for reasoning mail client correctly displays the message and correctly about security from a user-centred point of view, by decodes the attached virus program; the system correctly modelling a system in terms of actors and actions and executes the virus program. Rather, the problem has introducing the concept of the subjective actor-ability occurred because the expectations of the programmer state. We identify ten key principles for user interaction became inconsistent with what the user would want. design in secure systems and give case studies to Our purpose here is to present a way of thinking about illustrate and justify each principle, describing real-world this type of issue. -
Lmc 6313 Principles of Interaction Design
Principles of Interaction Design – LMC 6313 Syllabus Course Number: LMC 6313 Location: Skiles 346 Times: T/Th – 3:00p-3:50p F (lab) – 11:15a-2:00p Instructor: Dr. Anne Sullivan Instructor Email: [email protected] Office Hours: By Appointment (Mondays are the best bet) Office Location: TSRB 317C TA: Takeria Blunt TA Email: [email protected] Course Website: http://canvas.gatech.edu Course Description: What is interaction, what is design, where did these notions come from, and where are they going? Through the activities in this course, you will return to questions of what kind of designer you are and wish to be, what you believe in, and how that will extend to your research and practice. You will also develop your own critical take on the material in the class and sharpen your voice and arguments about your perspectives. Interaction design wasn’t invented from scratch as a singular, monolithic practice. It was born out of the intersection of a number of disciplines from within design and human-computer interaction, and also from art, media, architecture, politics, and philosophy, and beyond. There are many different definitions of what it is and where we fit into it, and no two people we meet in this class will likely have the same definition. And that’s the way it should be. Through my suggestions and yours, we will also turn to design questions in digital culture, film, tv, fiction, gaming, music, art and beyond as we together frame our understandings. As you read, The syllabus, dates, times, assignments, and details are subject to change by instructor notification through Canvas or email. -
How Interaction Designers Use Tools to Manage Ideas Preprint
How Interaction Designers Use Tools to Manage Ideas NANNA INIE, Aarhus University PETER DALSGAARD, Aarhus University This paper presents a grounded theory-analysis based on a qualitative study of professional interaction designers (n=20) with a focus on how they use tools to manage design ideas. Idea management can be understood as a subcategory of the field Personal Information Management, which includes the activities around the capture, organization, retrieval, and use of information. Idea management pertains then to the management and use of ideas as part of creative activities. The paper identifies tool-supported idea management strategies and needs of professional interaction designers, and discusses the context and consequences of these strategies. Based on our analysis, we identify a conceptual framework of ten strategies which are supported by tools: saving, externalizing, advancing, exploring, archiving, clustering, extracting, browsing, verifying, and collaborating. Finally, we discuss how this framework can be used to characterize and analyze existing and novel idea management tools. CCS Concepts: • Human-centered computing~User studies KEYWORDS Idea management; design ideas; design process; design tools; ideation ACM Reference format: 1 INTRODUCTION The fields of HCI and interaction design are well-known for studying impacts of novel interfaces and tools, and perhaps less known for studying the impact of tools that are already used in professional practice (Smith et al. 2009; Pedersen at al. 2018; Dalsgaard 2017). In the words of Stolterman, this ofen leads to research outcomes that are difficult to apply in practice, because the research is based on an inadequate understanding of how design happens in professional setings (Stolterman 2008). -
Toward Unified Models in User-Centered and Object-Oriented
CHAPTER 9 Toward Unified Models in User-Centered and Object-Oriented Design William Hudson Abstract Many members of the HCI community view user-centered design, with its focus on users and their tasks, as essential to the construction of usable user inter- faces. However, UCD and object-oriented design continue to develop along separate paths, with very little common ground and substantially different activ- ities and notations. The Unified Modeling Language (UML) has become the de facto language of object-oriented development, and an informal method has evolved around it. While parts of the UML notation have been embraced in user-centered methods, such as those in this volume, there has been no con- certed effort to adapt user-centered design techniques to UML and vice versa. This chapter explores many of the issues involved in bringing user-centered design and UML closer together. It presents a survey of user-centered tech- niques employed by usability professionals, provides an overview of a number of commercially based user-centered methods, and discusses the application of UML notation to user-centered design. Also, since the informal UML method is use case driven and many user-centered design methods rely on scenarios, a unifying approach to use cases and scenarios is included. 9.1 Introduction 9.1.1 Why Bring User-Centered Design to UML? A recent survey of software methods and techniques [Wieringa 1998] found that at least 19 object-oriented methods had been published in book form since 1988, and many more had been published in conference and journal papers. This situation led to a great 313 314 | CHAPTER 9 Toward Unified Models in User-Centered and Object-Oriented Design deal of division in the object-oriented community and caused numerous problems for anyone considering a move toward object technology. -
Persona Creation Based on Secondary Data: a Study on Perceived Reliability in UX Design
Aalto University School of Science Degree Programme in Information Networks Pekka Siika-aho Persona Creation Based on Secondary Data: A Study on Perceived Reliability in UX design Master’s Thesis Espoo, May 24, 2016 Supervisor: Professor Marko Nieminen Thesis advisors: Sami Vihavainen, D.Sc. (Tech) Hanna-Riikka Sundberg, D.Sc. (Tech) This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 687921. Abstract of master’s thesis Author Pekka Siika-aho Title of thesis Persona Creation Based on Secondary Data: A Study on Perceived Reliability in UX design Master’s programme Degree Programme in Information Networks Thesis supervisor Professor Marko Nieminen Major or Minor/Code T3008 Department Department of Computer Science Thesis advisors Sami Vihavainen, D.Sc (Tech) Hanna-Riikka Sundberg, D.Sc (Tech) Date Number of pages Language 24. 5. 2016 V + 67 English Abstract While personas are a widely used tool in the UX industry, they are expensive and time- consuming to create. This study examines utilization of secondary data as a less resource and time-consuming method for creating personas. Typically personas have been created from qualitative data that is gathered specifically for persona creation. By using secondary data, the time for user research can potentially be reduced thus bringing down also the cost and time needed to create the personas. In this study, personas were created based on secondary data available from public sources. The personas were then evaluated qualitatively by UX designers on their perceived reliability. Prior to this study, UX designers’ perceived reliability of personas created on secondary data hasn't been studied. -
Introduction to User Research
Introduction to User Research USER RESEARCH CAN HElP you acquire a deep understanding of your users' needs and how these needs are being met. With this research foundation, you can make informed design decisions throughout the product development process. Moreover, research can reveal opportunities for new apps and inspire innovative solutions that improve upon existing apps. This chapter wilt review a variety of user research methods such as shadowing, field interviews, and diary studies and will suggest ways to tailor these methods for your app. After reading this chapter, you should be able to develop and execute a user research plan for your own app. Chapter 4, "Analyzing User Research:' will subsequently explain how to interpret user research findings and incorporate them into your app designs. 39 Common User Research Questions- As you start planning your user research, you may have questions concerning the benefits and costs. Answers to these questions and others are included in this section. WHAT WILL I LEARN? The outcome of user research will depend on a number offactors, such as the methods used, the domain explored, and your research goals. Common themes uncovered through early-stage user research include user needs, context of use, perceptions, pain points, language, and norms. User Needs At the most basic level, user research will help you understand your users' needs. Questions you may be able to explore include how they do things today, what's important to them, and what needs have not been met. Having this knowledge will help you make both high-level (e.g., overall app concept) and low-level (e.g., screen layout) design decisions. -
Interaction Design
Interaction Design Do you want to design products that are easy to use? Through this course you’ll develop an understanding of the patterns and principles that govern interaction design. You’ll become familiar with a framework for assessing the success of interaction design, you’ll learn to structure the design of products around the goals of users, and you’ll learn to sketch and wireframe your design ideas. OVER FOUR WEEKS, WE WILL COVER Introduction Interaction design is a major component of the user experience. It incorporates information architecture and usability to define how a product will behave. Projects: Business Goals, Competitive Analysis, Context of use Scenarios Usability To create products that are easy to use, designers obey a set of usability guidelines. These rules of thumb are good points of reference for making decisions, and for communicating and justifying design decisions to others. Project: Usability Competitive Analysis Intro to Sketching Sketching is a fast and easy way for designers to get their ideas out and discuss them collaboratively with team mates. Project: Sketching Exercise Information Architecture Information Architecture is the structural design of an interface that allows a user to access the right content at the optimal time so that she can navigate the product most effectively. Projects: Card Sorting, Sitemap User Flows User flows are the paths that a user takes through a product in order to complete her tasks. Project: User Flows Wireframes Once a designer hashes out the overall structure and navigation patterns of a product, she draws up the product’s blueprints, or wireframes. -
Design, Prototyping and Construction
Overview • Prototyping and construction Design, prototyping and • Conceptual design construction • Physical design • Generating prototypes • Tool support Prototyping and construction What is a prototype? • What is a prototype? In other design fields a prototype is a small- • Why prototype? scale model: • Different kinds of prototyping • a miniature car low fidelity • a miniature building or town high fidelity • Compromises in prototyping vertical horizontal • Construction What is a prototype? Why prototype? In interaction design it can be (among other things): • Evaluation and feedback are central to interaction • a series of screen sketches design • a storyboard, i.e. a cartoon-like series of scenes • Stakeholders can see, hold, interact with a prototype • a Powerpoint slide show more easily than a document or a drawing • Team members can communicate effectively • a video simulating the use of a system • a lump of wood (e.g. PalmPilot) • You can test out ideas for yourself • a cardboard mock-up • It encourages reflection: very important aspect of design • a piece of software with limited functionality written in • Prototypes answer questions, and support designers in the target language or in another language choosing between alternatives What to prototype? Low-fidelity Prototyping • Technical issues • Uses a medium which is unlike the final medium, e.g. paper, cardboard • Work flow, task design • Is quick, cheap and easily changed • Screen layouts and information display • Examples: sketches of screens, task sequences, etc • Difficult, controversial, critical areas ”Post-it‘ notes storyboards ”Wizard-of-Oz‘ Storyboards Sketching • Often used with scenarios, bringing more • Sketching is important to low-fidelity detail, and a chance to role play prototyping • Don‘t be inhibited about drawing ability.