Software
  • Introduction
  • Code craft
    • Clean code
    • Reusable code
    • Refactoring
    • Code smells
  • Service craft
  • Software Principles
  • Big Data
    • Introduction
    • Data modelling
  • Patterns
    • Enterprise patterns
    • Software patterns
  • Agile & proj management
    • Scrum vs Kanban
    • Kanban
    • Scrum
  • Conflict management
  • Reading
  • Software Architecture
    • Architecture components
Powered by GitBook
On this page
  • Technical
  • Personal

Was this helpful?

Conflict management

Technical

  • Organise a tech session (1-2 hours max) with a clear agenda (what is to discuss, what should be the outcome, who presents)

  • proponents present their solution, with pros and cons on itself and vs other solutions

  • if the objective and available solutions are clear and doable, the outcome can be voted on (democratically)

  • if there are more questions (inconclusive objective), reorganise a new session, where someone will be delegated to prepare answers to those questions (and share them preferably before the session)

Personal

  • face to face in private

  • be transparent

  • listen

  • start what do you have in common with that person

  • ask and try to view their perspective and motivations

  • agree on what both could to work toward the common goal, or reduce tensions

PreviousScrumNextReading

Last updated 5 years ago

Was this helpful?