anchor.diff:  
   * Average out fairness or load balancing
   
  -* Focus on 1 stakeholder
  +* Focus on only 1 stakeholder
   
   Let's take a look at each one in detail and how to do it right:
   
  
positive.code: 
  Especially when scheduling people (who planned their social life based on the tentative schedule you gave them),
  it's key to minimize disruption. Another way to make this easier is to also do backup planning.
  
  For example in employee rostering, we assign 3 reserve shifts as backups to 3 employees:
  if another employee calls in sick, one of the reserve employees takes over automatically,
  without replanning. Only when more than 3 employees call in sick, we actually need to do (non disruptive) replanning.
  
negative.code: Project success doesn't depend on solution quality alone. There are a lot of factors that can make or break a project.
  In this article I highlighted some of the more social ones.
  Luckily, you can handle these additional requirements with http://www.optaplanner.org/[OptaPlanner] too.
  Don't let them catch you off guard!
  