Zaana Howard joins InfoQ to discuss Design Thinking and how it differs from how we traditionally look at design.
Trevor Owens sits down with InfoQ to discuss his new book, The Lean Enterprise, as well as the challenges he's faced bringing startup and entrepreneurship culture into large enterprises.
Melissa Perri shares her story of learning Lean Startup at Lean Startup Machine and then taking those learnings and applying them to various types of organizations.
Michael Cheveldave joins InfoQ to discuss Complexity Theory, the Cynefin framework, and how that fits with Lean UX.
Lane Halley sits down with InfoQ to discuss the Balanced Team movement and what can happen when people with cross functional skills self organize.
Amber Case explains how Esri handles GIS data, how to integrate small teams and startups into established companies, handling competent jerks and other types of team members, and much more.
John Shook sits down with InfoQ to discuss how lean change is both personal and organizational as well as the A3 process.
Jabe Bloom sits down with InfoQ to discuss systems thinking, complexity theory and how you can apply systems thinking to your organization or Agile implementation.
Glen Ford talks about his experiences in different organizations' environments, from start-ups to the likes of BBC. Glen discusses how to build great teams and why in his view Kanban works better than Scrum. Finally, Glen explains how Lean, DevOps and systems architecture all influence each other.
Jeff Gothelf sits down with InfoQ to discuss the origins of Lean UX, how to get started using it in your organization, and where we go from here.
Portia Tung talks about nurturing teams and supporting agile adoption as an Enterprise Gardener. She is a fulltime agile coach working within an organisation helping them achieve agility at scale. She discusses how the fulltime coach role differs from that of consultant coach, how teams are nurtured and why a culture of giving and sharing allows for collaborative growth.
Ola Ellnestam discusses the Mikado Method, a systematic approach to restructuring software. While complementary to, but different than refactoring or developing 'clean code' this method looks at producing a dependency graph to guide developers through the most successful path when introducing change into an existing system.