#1 Background and experience as a classical IT project manager

Let’s get back in time. Before quitting my job as a classical project manager for an IT team at my former workplace (http://www.zieltraffic.de), I didn’t have that much clue about agile development or let’s say in other words agile project management. The agency I worked for before PAYMILL, was more or less working after waterfall principle (which of course has its pros and cons).

Imho it always depends which company you are working in, because agile is something completely different to classical project management and I think it’s better for IT teams to work with it than with classical project management methods. But that’s not a discussion I wanted to start, it always depends and Scrum is not the only possibility working agile.

#2 Work as a Scrum Master at PAYMILL

So I was relatively seen as a newbie in this field. In retrospective to my first year at PAYMILL I had my lessons to learn and am still constantly willing to learn and improve with a team of forward-thinking and innovative developers, designers and so in a way seen product managers. This should be a primary goal in every IT team.

Not only coding for its coding sake but also not losing focus and improving ourselves towards our company’s goals and especially required customer needs. It doesn’t matter if you have 100 lines of beautiful code when it takes 1 year to work on it and then deploy it when needs for a specific products are fulfilled by a competitor.

#3 Get into material

I’m coding in my free-time to get to know new programing languages (thanks to codeacademy and some other great services out there) to understand where people in our team are facing problems in different cases and how I’m able to help them to get their stuff done. It’s always been a must-have for myself to understand and discuss with developers but also don’t lose focus on business and optimizing product itself. Thanks for this opportunity to be a part of the PAYMILL team, guys.

#4 Short facts I’ve learned so far:

  • Don’t blame means get fame
  • Learn from power of collective knowledge of developers
  • Moderate, don’t delegate
  • Strength and weaknesses in a team are different and individual
  • Home office and flexible working times are inevitable
  • Create a work atmopshere for innovations and forward-thinking development
  • Respect different characters and habits

#5 More than a workplace

You don’t always have to be best friends, but it should be a professional but also friendly atmosphere in your team. It’s not always about money and positions. It’s also about having fun at what you’re doing and developing new products on yourself which makes it worth to work.

If you’re part of PAYMILL, you’re also part of epic “Biergarten”-sessions with funny karaoke sing-alongs, but also can discuss with colleagues about new products in your free-time and develop new ideas for the company.

So far a great experience for myself. If you’re a developer, come to us and join our great IT team and get to conquer the e-payment world.

Oh, forgot that I’ve learned some new great acronyms like bofh or tl;dr.

My name is Dominic Krasnopolski and I’m working at PAYMILL as a Scrum Master

Guest Blogger

This is a guest post written by one of our contributors. To find out how you can get your post published on the PAYMILL Blog check out the Guest Blogging Guide