Learn More
—User stories are a widely used notation for formulating requirements in agile development. Despite their popularity in industry, little to no academic work is available on determining their quality. The few existing approaches are too generic or employ highly qualitative metrics. We propose the Quality User Story Framework, consisting of 14 quality(More)
Choosing a content management system on which you rely your business is challenging because they need a healthy software ecosystem in order to function efficaciously. Unawareness of this will result in content managers having uncertainty about the future suitability of their chosen content management system. This study describes an empirical, inductive(More)
Despite the widespread adoption of business modeling techniques in academic research and business, no research has been done into how efficient and effective business modeling techniques document and communicate business models. This paper compares three visual business modeling techniques with a visual approach and identifies the strong and weak points of(More)
—How to achieve alignment of software product management with software architecture and whether there is a business case for doing so is scientifically unknown. Yet, software architecture has large, direct impact on product success factors: creating a winning product and delivering value to customers. In this exploratory case study paper we identify the(More)
User stories are a widely adopted requirements notation in agile development. Yet, user stories are too often poorly written in practice and exhibit inherent quality defects. Triggered by this observation, we propose the Quality User Story (QUS) framework, a set of 13 quality criteria that user story writers should strive to conform to. Based on QUS, we(More)
Context and motivation. User stories are an increasingly popular textual notation to capture requirements in agile software development [6]. User stories only capture the essential elements of a requirement: who it is for, what is expected from the system, and, optionally, why. Popularized by Mike Cohn [2], the most well-known format is: " As a type of user(More)