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.

You might be wondering what on earth an Australian is doing on the other side of the world, working at a PPC company that consists almost solely of Czechs. It’s a pretty good question — one I get a lot. I like to quote Kafka: “Prague never lets you go. This dear little mother has sharp claws.” I feel privileged to be working for PPC Bee, and I adore my work.

How many lines of source code does PPC Bee consist of? How many new partners have joined our team? And how many pounds of honey have made the day of our clients and others?

Last year we placed great emphasis on strengthening our product with regards to functionality and usability, stabilizing the application in terms of hardware as well as from the perspective of the admin, and reinforcing key positions in our team.

There’s nothing difficult about it. You take data from the application, get data from the client, and voilá, the case study is in the world! However, it isn’t so simple, unfortunately. There’s always work that has to be done that has higher priority right at the moment you’d like to start working on a case study. This was exactly our and our client’s case. For a long time, we had been racking our brains trying to figure out how to get on top of our priorities — as well as not bothering our clients — with whom we wanted to cooperate with on the case study.