When developing new products and services, situations can arise in which the team feels insecure: In which direction should we develop? Shall we take route A or route B? How much potential lies in each different idea? What does the market really need? This uncertainty about the development path in one of our product teams has led to a design sprint.
The core of agile software development according to Scrum is regularly releasing product increments to the customer. The software’s functions are gradually extended, but the customer receives a version of their software right after the first sprint. That’s why at the end of each sprint, a review meeting is held where the development team presents the new functions to the customer. In this article, we will explain why it makes sense for the customer to participate in the reviews and why they should test the software created for them intensively and at an early stage.
A usability test, that only takes five seconds? Admittedly, it is almost too good to be true. The reservation against Five Second Tests, a specific form of remote usability testing, is great by and large. Experts traditionally place a lot of value on a clean methodology and clean results. Skepticism toward a new and simpler method is understandable. The attractiveness of Five Second Tests lies undisputedly in its simplicity. Through a link, participants are referred to a page on which they are shown a screenshot of a web site for exactly five seconds. Following, they have to answer questions to this page. Finished.
What before was true for the video recorder is unfortunately again true for many current websites: users have difficulties in completing tasks and reaching their goals. How to use those formerly expensive video recorders was just something the user had to learn, for better or for worse; after all, the piece of equipment was paid for. But the next website – and therefore the next provider of comparable services – is only a click away.