Conflict of interests on the retrospectives

Lately Patrick Kua described a retrospective that went all wrong after a tech lead (i.e. person who has strong personal/technical interests in the project) was leading a retro into a direction he wanted.

I also witnessed similar situation in my own practice. At times a person that "just knows how to do it right" is tempted to push his solution no matter what. Often it is the person most competent technically that is assigned to the Scrum Master or Coach role. Such an assignment creates a conflict between his personal interests and interests of the whole team.

Did you experience such situations? What was the result? How did the situation change over time?

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.

More information about formatting options

Captcha
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Security question, designed to stop automated spam bots
Syndicate content