Jim Benson discusses why Kanban is helpful: enables clarity of purpose, promotes shared understanding, recognizes individual input, depersonalizes work, respects problem solving, and others.
Aurimas Adomavicius discusses metrics of great User Experience for the enterprise, the dual-track Scrum model, common pitfalls, lessons learned, and quantifying the success of a project.
Ian Kelsall and Keith Dodds discuss why complexity trumps determinism in the modern enterprise, explaining why it is essential to have a a fundamental change in leadership mindset.
Doug Talbot explains the importance of measuring to the Lean feedback cycle providing advice on what to measure and how often.
Big Design Upfront was considered so evil in the early days of Agile that it acquired its own acronym. It’s time we relearned that great products start with asking the right questions.
Ardita Karaj and Jason Little present their company’s journey to Agile using Lean Startup, contractor/internal coaches, culture hacking, ADKAR, Kanban, Innovation Games, and others.
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.