English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Global: Zendy Plus annual

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Global: Zendy Plus monthly

Global: Zendy Tools annual

Global: Zendy Tools monthly

Global: Zendy Free Plan

Although integrating UX practices into software development processes is atype of Software Process Improvement (SPI) activity, this has not yet beentaken into account in UX publications. In this study, we approach UXintegration in a software development company in Sweden from a SPI perspective.Following the guidelines in SPI literature, we performed a retrospectivemeeting at the company to reflect on their decade of SPI activities forenhancing UX integration. The aim of the meeting was to reflect on, learn from,and coordinate various activities spanned across various organizational unitsand projects. We therefore supported the meeting by a pre- generated timelineof the main activities in the organization that is different from commonproject retrospective meetings in SPI. This approach is a refinement of asimilar approach that is used in Agile projects, and is shown to improveeffectiveness of, and decrease memory bias. We hypothesized that this methodcan be useful in the context of UX integration, and in this broader scope. Toevaluate the method we gathered practitioners' view through a questionnaire.The findings showed our hypothesis to be plausible. Here, we present that UXintegration research and practice can benefit from the SPI body of knowledge;We also show that such cross-section evidence-based timeline retrospectivemeetings are useful for UX integration, and in a larger scale than one project,especially for identifying and reflecting on 'organizational issues'. Thisapproach also provides a cross- section longitudinal overview of the SPIactivities that cannot easily be gained in other common SPI learningapproaches.

Cross-Section Evidence-based Timelines for Software Process Improvement Retrospectives: A Case Study of User eXperience Integration