UCD Glossary

Within the SAMS project, a UCD Glossary was developed to make sure that the project team has the same understanding of UCD terminologies. The glossary of UCD terms was first created as one of the strategies to achieve effective teamwork within the international UCD group, considering different background knowledge, understanding, and way of working. It was important for the UCD team to have the same understanding and definition of each term used in the working process; and from time to time in the research and reporting process, the UCD team in each country referred to the UCD Glossary in order to make sure that the research process is still following the agreed methodologies.

In order to make the UCD collaborative process more understandable, Some of the terms in the UCD Glossary was enriched with stories on how the terms and methodologies were used within the SAMS project.

These are several terms that are being used during the SAMS project timeline: #Lean UX, #Market Requirement, Organizational Requirement, Persona, Product Backlog, Qualitative User Requirement, Quantitative User Requirement, Requirement, Stakeholder Requirement, User Group, User Need, User Requirement, User Role, User Want.

Lean UX

Why lean UX for SAMS

The SAMS team has professional experience in all components of lean UX. All partners have adapted the lean startup practice of rapid prototyping. This opens up the opportunity to create a common understanding of the SAMS product development strategy very fast and use methods for research, prototyping and documentation that are already known and established.

Definition

A keyword used to describe an approach for human-centred design that is based on a combination of different approaches (agile development, design thinking, lean startup) and tries to integrate principles and methods for usability and user experience into agile development, thereby achieving economic advantages from a cost-benefit perspective. ( CPUX-UR – Curriculum (Version 1.3, June 2016))

Notes of CPUX-UR Curriculum (uxqb.org):

1. The user requirements engineer must know about Lean UX so as to be able to communicate with members of a Lean UX project in a professional way.

2. Agile development processes are the basis for Lean UX, as the iterative approach in teams and the realisation of small, well-defined packages makes it possible for small and quick tests to be regularly carried out. The results from tests are then directly used in the next iteration (called “sprint”) for the further development. See also SCRUM.

3. Design thinking is the basis for Lean UX, as it helps project members to incorporate the users’ perspective into the development process through its solution-oriented way of thinking based on an in-depth understanding of the problem context.

4. Lean startup is the basis for Lean UX, as it suggests that at first, everything is a hypothesis and consequently needs to be validated. The team learns through experiments about the user and the market. Failure is part of the learning process – not every hypothesis is validated, not every experiment provides the desired results.

Market Requirement

Definition

A requirement for an interactive system based on the marketing policy of the supplier aimed at maximizing business opportunities, purchase and use of the interactive system.

Note: Market requirements are often referred to as customer requirements.

Example in SAMS context

1. “The advisory support system must be at least as usable as those of the two strongest competitors”

(CPUX-UR – Curriculum (Version 1.3, June 2016))