Although I didn’t really know it at the time, I’ve long been a proponent of agile methods at work. Which is why it’s ironic that, now we’ve started actually doing agile development, my role in the company (thank you Dr. Laurence J. Peter) basically prevents me from having anything to do with it.
To fill that gap, I’ve been reading agile blogs, and listening to (and occasionally transcribing or summarizing) agile podcasts. Although agile is very much about working with a team, I’m trying to use its team-based strategies to manage my own work… although without a defined customer, a prioritized task backlog looks an awful lot like a to-do list. I go to standups and medium-level meetings about the challenges people face trying to implement agile in the company. And I’ve taken to reading books like Influence Without Authority, since I have none of either.
I think the correct term is glutton for punishment.
Or….. you could just get yourself onto a Feature Team for a few months and actually experience it first-hand!
Any team would be happy, and proud, to have you as a member, even if it was only for a few Iterations! Even my excellent team, I’m sure!
/me blushes. 🙂
An opportunity to join a feature team arose recently, but when I put my name forth it was fairly strongly suggested by various parties that it wouldn’t be appropriate. (That’s actually the event that prompted this entry.) I’ve reviewed my new formal job description since then, and I think I’ve found a better way to make the argument that joining a team is exactly what the role demands; we’ll see what transpires.