Stuart Williams shares from experience how his company implemented Kanban, what worked for them in handling maintenance, support and a number of small projects.
Garrett Smith introduces Drunken Stumble, a development method in two stages: a lean, which represents the goal of the programmer or team, and a stumble, which is a series of automatic "next steps".
Alberto Brandolini discusses how the Theory of Constraints, Kanban, CQRS, Domain-Driven Design, EventStorming and UX blend together to solve the real problems in software development.
Francis Fish proposes a new agile manifesto that is influenced by Lean and the manufacturing movement.
Shaun Clowes discusses Growth Hacking, a way of minimizing waste in all aspects of product development and go to market.
Andy Carmichael shares the experiences of a team new to Scrum adopting a customized Kanban process that would allow changes that were kept only if they were confident they resulted in improvements.
Scott Ambler describes how to evolve from today’s vision of agile to a truly disciplined agile enterprise, exploring what it means to scale strategies at the project level and across an organization.
Ken Power looks at how to enable work to flow through an organization by designing an impediment removal process, and how to foster such a culture from teams to executives.
David Daly presents why his team chose Kanban, how it adopted it, the benefits of using Kanban, tips for implementing Kanban and pitfalls to avoid.
Jose Casal discusses using Kanban to introduce Agile principles and practices in non-Agile organizations, how Agility can help businesses improve their results and business performance metrics.
Thomas Lant presents how Lean Kanban was introduced into their organization, the challenges met, initial reactions and fears, the outcome.
Liz Keogh discusses breaking down requirements without going into too much detail combined with complexity estimation for easy planning, dependency management, and prioritization.