Many times I come across job descriptions where the ScrumMaster role is just another hat worn by a lead developer, a development manager, a project manager, or someone else in a similar position of power over the development team. Of course, everyone has a budget, but skimping on this role is not the place to try to save money. Worse yet, sometimes companies hired for agile coaching will explicitly, or tacitly, endorse that conflation in responsibilities. To them, securing the engagement is more important than doing the job well. By definition the ScrumMaster is a servant leader; they should have the traits of both a […]