Another way: introduction to new employees

Posted on Leave a commentPosted in management

Decided to change a bit how i introduce myself to new employees. Going to share problems and challenges during first introduction days for #developers. Main question at the end: “Do you have ideas how to help me?” What do you think?job_sux


  • Previous one was boring even for myself: history of the company, structure, process, bla bla…
  • Want to share what we tried already recently and explain why certain things succeeded or failed
  • Want to be on the same page
  • Think that good people are inspired by problems and challenges
  • Want to share my point of view
  • Want to hear alternative solutions and ideas
  • Don’t always have a chance to participate in an interview

Just started and instantly got a feedback. “Didn’t expect it’s going to be interesting…”. Hm.. so it should work…

Teamwork: Product Manager vs Development manager

Posted on Leave a commentPosted in management

I am often asked what are the responsibilities of Product Manager and Development Manager? What a weird question!

Responsibility is the same! Both have to deliver great product!

Skillset is different! Both bring different value to a team! One knowledge about product and domain. Another knowledge about process, people and tech. subtleties

Do we confuse responsibility with skillset while working in a team?

P. S. Same with developers

Part 1: When and Why to fire a Scrum Master?

Posted on Leave a commentPosted in management

Previous post on this topic: Part 0: When and Why to fire a Scrum Master?

Next post on this topic: Part 2: When and Why to Fire a Scrum Master? – Decision Making

I love football and realized recently that problems and challenges we face in our organizations (at least those that working in creating software products) are very similar to those that football club has.

  • Complexity: strategy, tactics, finance, human factor. Waterfall doesn’t fit well, flexibility is a key
  • Product by people: all results depend only on the team, but not machinery
  • Uncertainty: you cannot predict with 100% how your team will look like by the end of the season

football stadium

I think we can learn a lot from Football to improve our daily work. Football is a lot about management on different levels. And as you can suppose Coach (called Manager in UK) is the key role that guides the team to success. I am sure you cannot imagine world level team without the coach.

“Why do most think it’s possible in software development?”

I want to do following thing. Grab certain statements that we hear quite often in our daily work and take a look at them from Football manager perspective. To do that i need to share analogies i use in my head. Not sure if it’s 100% fit. But it’s a thinking tool, not a proven theory:

football and dev analogy

After making this analogy we can twist a question a bit, which will help to validate common statements from our daily work:

When and Why to Fire a Football Coach?

You don’t need a manager

Posted on 2 CommentsPosted in management, quick thoughts

Why? Because most probably he will:

  • Work on processes, not on value creation
  • Be responsible for a certain centralized function: IT, Dev, PMO, Process Improvement department; which is not valuable without others (or just not valuable and gives overhead)
  • Try to coordinate communication among different teams
  • Have desire to push down decisions
  • Have own goals


But you need leaders who will:

  • Help to form cross-functional teams and delegate decisions to them
  • Make information transparent and easily accessible
  • Encourage collaboration
  • Focus on value creation, not process improvements
  • Build shared goals