Iteration manager. New role?
On many job descriptions lately I see position "Iteration manager". It should be something similar to Scrum Master, but in my opinion the term itself contradicts scrum values. Dev team is responsible to deliver relisable increments every iteration. Why do we need someone to "manage" the iteration? The word "manage" also doesn't corespond to servant leadership position that scrum master should have.
Can someone give justification about this position? Also, what this position says for the company itself?
I suppose it can be justified in so far as it is not apparenty claiming to be a Scrum role. If Scrum language is not being subverted, as it so often is, then I would view that positively.
The underlying situation may be any of:
- the organization is not ready for Scrum
- the domain does not relate to a complex software product where Scrum would be appropriate
- they are experimenting with fake agile
- they have their own or another agile process which is genuinely fit for purpose