Sunday, May 2, 2010

Impediment Driven Development

I was wandering for some weeks what's the core of my new role in my company.

Now I've got it: I'm doing IMPEDIMENT DRIVEN DEVELOPMENT.

I maintain a list of impediments which disturb our developers and tackle the impediments one by one.

To be honest, I usually tend to tackle several impediments at the same time rather than one by one, but I try hard to limit the work in progress.

It sounds a little bit like the usual Scrum master role (the guy who tries to resolve all impediments of one team), but my role is to resolve the impediments related to a few topics (build mgmt and test automation) of many teams.

No comments:

Post a Comment