Diana talks about how to create the conditions for having the best job ever and describes a model for team collaboration and communication. She explains five simple rules for ongoing learning at the individual, team and organization level.
Amr Elssamadisy, founder of Agile Culture New York and author of the book Agile Adoption Patterns, shares his thoughts on why safety is essential to Agile success. We know that learning is essential for successful agility, and teams learn best through failure – but failure is inherently unsafe. The key to success is in making things safe. Without safety you cannot learn effectively from failure.
Dan Mezick, author of the book The Culture Game, shares his insights on engagement as the fuel of successful and lasting Agile adoptions. Pulling examples from Open Spaces and the computer gaming industry, Dan explains how they both implement four basic rules: have a clear goal, a clear set of rules, a good feedback system, and support an opt-in participation strategy.
Derek W. Wade and Susan Eller discuss double-loop learning, Chris Argyris, frames, simulations, hospitals, mental models and why double-loop learning is so much more bad-ass than single loop learning.
In this interview, Craig Larman discusses the many challenges you face when scaling scrum to large organizations. These challenges stem from decisions to use component teams over feature teams; adopting out sourcing without careful consideration for the impact of that decision; and over specialization of skills and limited learning which leads to waste, bottlenecks, and poor performance.
Roy Osherove talks about the challenges and opportunities of being a software team leader. He shares his hard won experiences in growing teams, their members and influencing behaviour. Being a software team lead is about getting out of your comfort zone, creating trust and commitment in your team but also about knowing about team maturity levels and the different approaches needed.
Venkat Subramaniam talks about the characteristics of JVM languages like Groovy, JRuby and Scala, and their applicability in enterprise applications. He also mentions several implementation details and finishes by addressing issues of lifelong learning for developers.
Brian and dave discuss what it might mean to be a true craftsman and why the idea of craft has become so popular of late. Other issues discussed include the question of why craft seems to be focused almost exclusively on programming and why everyone does not aspire to be a craftsman? Programming as performance art, programs as literary artifacts, and code "habitability" round out the discussion.