Figure - uploaded by Pariya Kashfi
Content may be subject to copyright.
A part of the indirect-events timeline. Indirect-events are activities that have been performed for other purposes but indirectly influenced UX integration. Each box represents one event, and is color coded to reflect in which unit of the company that has happened. Indicated events are those events that
Source publication
Although integrating UX practices into software development processes is a type of Software Process Improvement (SPI) activity, this has not yet been taken into account in UX publications. In this study, we approach UX integration in a software development company in Sweden from a SPI perspective. Following the guidelines in SPI literature, we perf...
Similar publications
The necessity of software as stand-alone products, and as central parts of non-traditional software products have changed how software products are developed. It started with the introduction of the agile manifesto and has resulted in a change of how software process improvements (SPI) are conducted. Although there are agile SPI methods and several...
Small-sized software enterprises have tried for years to make major changes to improve the software development process and, consequently, the quality of their products. Many small companies are focusing their efforts on conducting software process improvement initiatives to mature their software processes and to deliver products on time and on bud...
Software development organizations take great risks when are faced with process improvement projects and the inclusion of best practices. Such risks include the selection of a standard, framework or model for the improvement process. Some organizations decide to integrate best practices from different sources to be non-dependent on a particular mod...
The software development industry is dominated by a myriad of small- and medium-sized enterprises (SMEs). The main goal of this chapter is to provide a characterization of SMEs based on previous studies. It also includes an overview of a number of software process models and software process improvement (SPI) models, which are aimed at assisting SM...
The International Conference on Software and System Processes (ICSSP), continuing the success of Software Process Workshop (SPW), the Software Process Modeling and Simulation Workshop (ProSim) and the International Conference on Software Process (ICSP) conference series, has become the established premier event in the field of software and systems...
Citations
... Second, companies should concentrate on the interplay between UX experts, developers and other stakeholders during the actual design and development . We present our early breaking results on stakeholder involvement that are found through a case study in a Swedish software development company (for more details, see [14]). ...
... The idea behind SPI is that development processes often need to be managed and improved in order for the outcome software to be of better quality [22]. Therefore, UX integration can be considered as a type of SPI [14] , and SPI body of knowledge can inspire UX integration research and practice. In particular, since the software development community already has access to ample SPI guidelines and best practices [22] . ...
... In particular, since the software development community already has access to ample SPI guidelines and best practices [22] . Since SPI guidelines are generic and they do not directly address UX or other specific software quality characteristics [14], they need to be customized to better suit UX integration. ...
Stakeholder involvement is one of the major success factors in integrating user experience (UX) practices into software development processes and organizations. It is also a necessity for agile software development. However, practitioners still have limited access to guidelines on successful involvement of UX stakeholders in agile settings. Moreover, agile UX literature does not well address the specific characteristics of UX and it does not clearly differentiate between UX and usability work. This paper presents two guidelines for supporting stakeholder involvement in both UX integration and the daily UX work. In particular, we focus on the special characteristics of UX: being dynamic, subjective, holistic, and context-dependent. The guidelines clarify practical implications of these characteristics for practitioners. In addition, they can help researchers in addressing these characteristics better in agile UX research.
