Facit Agile Sprint Testing

Facit Agile Sprint Testing

Agile Development – Highest Efficiency

In an agile development, there is often not enough time to involve users in the sprints. This frequently results in a less than optimal usability and user experience of the work packages.



F.A.S.T. permits the quick testing of user experiences in agile projects

While we will see to the recruitment of suitable test participants, the work on the test prototype can be continued. The final test material will be discussed in the beginning of the FAST week. At the end of the FAST week, the insights from the user test will be integrated directly in the development. 

This way, there will hardly be any interruptions in the development. Optimisations of usability and UX will be incorporated at once. In the tests using prototypes, solutions can furthermore be tried out directly in the prototype. This results in extremely effective optimisation loops.

Insights will be noted by observers already during the tests.

We use the competence of everyone involved in the project

FAST offers UX close-up: All stakeholders witness the interviews in our test studio, product owners, developers, researchers and others cooperate actively in our results workshop and the shared development of feasible approaches to solution will lead to the entire team supporting the optimisations. This requires a willingness to discuss things and the readiness to make decisions.

Our testing is especially sensible if it is done repeatedly. We therefore recommend setting fixed testing dates (e.g. four times per year, each month). This is the best approach to ensure that testing will in fact be conducted (and not postponed time and again). Clear deadlines for submitting the test material and research questions are a part of this. By means of container tests, several user stories and templates are covered in one test.

What is as important at FAST as in the classic lab test: trained behavioural observation

FAST vs. classic UX lab test

In the course of FAST, (“formative”) user tests take place primarily as in parallel to the development by means of prototypes, while the explorative use and evaluation of a running system is often in the foreground in the (“summative”) classic UX-Test.

Therefore, also a few user stories, UI patterns and templates are frequently selected in FAST, while the classic test rather maps the complete user journey.

The repeated active cooperation of stakeholders is at the centre of attention in the FAST because it enables the a rapid continuation of work in the development sprint. In classic “turnkey” UX tests, in contrast, the customers receive a comprehensive report after the analysis and a detailed interpretation and presentation of the findings.

Reference projects

Contact us

Michael Wörmann

Michael Wörmann

Managing Partner

+49 89 740 420 5560