So, you think you are ready to manage a team? Maybe learned Scrum, or so me other Agile methodology. Maybe that failed, you hired the scrum consultant who either told you, you are not following it correctly, or you haven't modified it to your needs. Read.. it doesn't work, but we will blame you anyways.

Software project management is anything but easy, and definitely not something you can just learn in a weekend.

When I interview software managers or even lead engineers, I ask a few basic questions.

1. Given 10 features that *must* go into a product, due by end of the year, what order do you have your team do them in.
2. Given a set of bugs, what order do you fix them in, and why.
3. In motivating a team there are intrinsic and extrinsic motivators. What are some examples?
4. Given a group of software engineers, and the popular mythical man month belief that the more engineers you put on a project the less efficient they get, why do you think this is? What are some of the factors that cause 1+1+1+1+1=3D3 as far as productivity? Conversely, what are some of the ways, as a project manager you instead can get synergy such that 1+1=3D3?

A programmer whom you simply push stories to, will never grow into a lead, nor reach their full potential.

Nor will you gain the synergy, and upwards transfer of knowledge you will require to truly have a successful team.

I'm on a mission to build developers up.