team

Two years ago, I was working as a teacher. Initially, I liked my job, but as time went on, the overwhelming desire to use a baseball bat while at work became too much. I returned home in a bad mood, which didn’t help home life. There were only two ways out of this situation. The easier one was to turn on autopilot at school every morning, solve nothing and hope I didn’t end up in a madhouse or alcohol treatment center. I chose the second option, decided to leave the education field, and completely change careers.

Do you need to quickly develop or kick off a tiny feature? Would you like to create an MVP, but don’t have the time? Do you not really want to do Design Sprints and at the same time can’t afford to spend lots of money? Do you want to unite your team? In that case, shut your programmers, testers, field experts, and designers in a conference room, make sure they have enough to eat and drink, and look forward to receiving promising results by the evening. It sounds simple, right? Luckily for you, it really is quite simple.

Testing should be an indispensable part of developing any product. Sometimes it’s circumvented, sometimes viewed as a necessary evil so that we can get our invention to people. And other times, testing can be fun, and if the processes are set correctly you don’t need to even know it’s going on. Which is our case.