Solving conflicts in Agile

Many times Scrum is imposed in companies so the duty of

Scrum Master become very important and hard as well.


As one of his duties the scrum master has to resolve conflicts between members of the team and

between Product Owner and team members.

I like to talk about a few personal experiences that I had recently.


Personal examples

I used to work with a lazy product owner who barely commits to write

user stories or to prioritize the backlog. Indeed, he forgot sometimes to assist to Sprint demo or arrived later to some Retrospectives.


One day in one retrospective the whole team complained about his behavior.


Based on my suggestion the team met with its Product Owner and they discussed

a way to improve Product owner’s job with the help of business Analyst.


Once I had team members which were not aligned with one another. Furthermore,

they didn’t like to help each other. So I recommended them to have a share vision of

the development team. Later it was easy to introduce pair programming and peer review.


Other time the developers estimated so wrong because of lack of knowledge in

business, technological platforms and corporate procedures.

The issues were solving adding one meeting before estimating to clarify the doubts and

validate the approach to attack the development of each user story.


Mario Lucero

Mario Lucero

I am all about helping companies to adopt agile as methodology in Chile.


I believe many organizations think that agile is not for Chilean companies because of Chilean culture is totally
different from i.e. USA culture but I worked with Chilean professionals who after using agile realized it is feasible
to implement it.

Agile works in small and large projects and there are many evidences which demonstrate this.

Leave a Reply

CommentLuv badge