back to notes

Conflicts - Source and Solution in Agile SCRUM

Conflicts Source and Solution in Agile SCRUM
Published on May 17, 2018

Uttam ThakurFollow
Environment Strategist |TDM | Project Management | Agile practitioner | QA | PMP®️ CSM®️

In Agile Scrum collaboration is key success starting point, as we know collaboration itself means a conflict when group of people from different streams, technology, Mindset come together to solve a Business problem for stakeholders, Customers or end users it is obvious conflicts are coming upfront.
As a servant Leadership-Scrum Master needs to identify with Analytically & collaborative approach, by thinking and observing if the Conflict is Constructive or Destructive? Once Identified evaluate and identify what is the source of Conflict. In Agile Scrum what I believe and understood per my experience Sources are any on these three:
Product
Process
People
I am just outlining in a simple way and very generic on these three point.
Product:
Product Conflict relates conflict risen from the Requirement, in agile term we can say Product backlog. It means requirement is not clearly understood, shared vision is not clearly understood & defined, Definition of Done (DOD) and Acceptance criteria are not clearly setup upfront collaboratively, poorly written EPIC’s, User stories, Structure of Product backlog is not consistent, Prioritized List of backlog Shuffles so frequently without conducting and involving Scrum team’s discussion and changes are not maintained properly based on Business values priority.
Single solution for this problem is Work collaboratively, discuss frequently with stakeholders, End Users and Scrum Team, use different tools and techniques which is best suitable for your team to understand product backlog, setup DOD and acceptance criteria at all levels Upfront achieve shared Visions (Final product Release, Release, Sprint Levels)
Technique can be used > Brainstorming, End user Interviews, User story Workshops, Product backlog Refinement etc.
List can be go beyond listed points, you can use following generalized approach
Identify >Evaluate > Implement.
Process
Next conflict come from Process, in newly adopting Organization I observe many people are rigid to adopt Agile methodology so if any organization decide to adopt Agile Scrum, C-level management should be supportive and provide their buy in and support from all levels. Next is to educate all in the organization about Agile Scrum values and principles so they are very clear what is Agile and what are Do’s and Don’t.
I suggest start Small select some key pilot project after careful consideration for AGILE Implementation as per company strategic policy (Universal Thumb rule).
Sudden drastic change in practices of organization can cause serious issues and dissatisfaction at all level.
Apply fast fail approach for pilot projects and see the value achieved and act accordingly. There are many ways to evaluate use whatever suitable for Team e.g. Scrum have Sprint Planning, Daily Stand-ups, Backlog refinement, Specifically for process Sprint retrospective and Project retrospective etc.
People:
In Agile people are more important as they are the one who develop and run the show. I believe we need to closely watch & understand them. As a servant leader provide them a safe environment where they feel their thoughts are listened and taken care. Help them professionally and personally to achieve their goals, Align their personal goal towards project goals.
Educate them on Agile Methodologies and terms as and when got time for discussion, ask them their understanding and feeling about Agile and their terms, how we can improve etc. there are so many games and technique you can use available in market. Chose whatever suitable and best for your team.
Never Burn-down the team on maximum level I believe best approach 4 two weeks’ iteration/Sprint followed by 1 Week iteration/sprint to settle down all the last 4 iteration work and relax time to learn and share learning with team member before start next Sprint. (as we know Scrum follow back to back sprints if you continue in same way it may Burn-down your team, so decide a good approach to make them accountable by providing healthy environment and consistent pace)
Give Rewards to Team instead of individual and appraise the team or member for their effort time to time don't wait till end of sprint or project.
If above points are not taken care and identified you can see following common impact, people may leave the Team/Organization, dissatisfaction and low Team performance, destructive conflicts, Low moral etc.
Note: These are my personal experience during assignments and the thoughts I refer and follow Mike Cohen