This past winter I received a great piece of advice from an Agile Coach. It was not to get hung up on titles, to consider a gig based on whether or not you feel it will be a great learning opportunity for you. There can be very big differences in what a person with a given title does at one company as opposed to another.
I saw a post last week where the sharer was dissing the role of an Agile Project Manager. In many ways promoting their own beliefs by trashing something different that they actually didn’t fully understand.
I came really close to breaking a rule I have that my comments on other people’s posts are positive. Though that rule doesn’t translate to preventing myself to take on the subject in my own separate post, lol.
Basically… I didn’t find it very agile with a small a.
This past winter I received a great piece of advice from an Agile Coach. Not to get hung up on titles. To consider a gig based on whether or not you feel it will be a great learning opportunity for you. There can be very big differences in what a person with a given title does at one company as opposed to another.
The Agile maturity at one company can be very different than another. Though it’s a learning opportunity to work at a company going through change. Another reason to decide what and how you want to learn. An Agile Project Manager might be a transition role.
Candidates need to dig a little deeper to hear about what the expectations are for the role. Conversely, Managers need to listen to someone’s experience to measure their fit.
In some ways it’s both a strength and a fault in the tech industry that we don’t turn out people in cookie cutter shapes.
