Benjamin Mitchell shares experiences gained working with teams over the last five years, highlighting mistakes that were made following simplistic guidance and outlining key pragmatic examples that worked.
Benjamin Mitchell is a highly-rated international speaker on applying innovative approaches, such as Kanban, to software development. Based in London, he works with clients as a speaker, executive coach or team consultant. He has practical real-world experience delivering software projects with exceptional results based on practical, implementable advice. Twitter: @benjaminm
Software is changing the world; QCon aims to empower software development by facilitating the spread of knowledge and innovation in the enterprise software development community; to achieve this, QCon is organized as a practitioner-driven conference designed for people influencing innovation in their teams: team leads, architects, project managers, engineering directors.
Seems like cargo cult run amok for too long
However, I am surprised it took five years to discover that "following simplistic [Agile] guidance" would not result in much more than what he ended up with. His expectations are classic cargo cult.
Most things do not have to be re-learnt through the school of hard knocks. Plenty of literature (Lean-Agile and beyond) on humanistic & psychological issues regarding servant-leadership, motivation, biases, nurturing, feedback, retrospectives, empathy, theory of mind, etc., has been available for far longer than that.
No core description of a methodology nor basic advice from a few select gurus (who cannot even agree amongst themselves) will ever be the solution to unskilled, unpracticed, inexperienced, or otherwise poor leadership/management. And in particular, Scrum and Kanban Method explicitly do _not_ address such issues.