Deliver Early - There Is No Excuse!
Jesper Boeg discusses why it is important to deliver software early, why it is difficult to do so, along with tools/tips/practices: shared vision, story maps, coaching, and others.
Jesper Boeg discusses why it is important to deliver software early, why it is difficult to do so, along with tools/tips/practices: shared vision, story maps, coaching, and others.
The Lean Software & Systems Consortium (LeanSCC) whose mission is to improve the world by improving its systems and system-building capabilities (well known in the agile community for promoting the use of Kanban for software development) reorganized as the Lean System Society. The goal is to accelerate and deepen the Lean paradigm and bring together thinkers and doers from different perspectives.
Double-loop learning can be a great model for encouraging transformational improvements in teams by challenging key assumptions and strategies. Retrospectives and Lean Startup provide a framework to incorporate this learning model.
Forrester have recently released the results of their November 2011 Global Agile Software Application Development Online Survey in a report entitled "Survey Results: How Agile Is Your Organization?" It contains a number of interesting findings around how organisations that have adopted Agile are dealing with their implementation.

In the second of two articles Claudio Kerber talks about his experiences in team formation and collaboration and explains the process whereby he "became unnecessary" as the team he was working with built trust and cohesion through trust, shared knowledge and shared experiences. He examines the theoretical underpinnings and discusses ways in which servant leadership emerges.
![]()
Lean has the concept of a Sub-Optimal process. A Sub-Optimal process is where a part of the process is optimized to the detriment of the entire process’s efficiency. Are Agile practices creating projects that are in danger of being or becoming Sub-Optimal? What Agile practices are contributing to projects becoming Sub-Optimal? What can we do ensure our projects do not become Sub-optimal?

In today’s increasingly dynamic business environment, organizations must continuously adapt to survive. Change management has become a major bottleneck. Organizations’ need a practical mechanism for managing controlled variance and change in-flight to break the logjam. This paper provides a foundation for applying lean and agile principles to achieve Enterprise Agility through social collaboration
Joshua Kerievsky discusses Lean Startup -a disciplined, scientific and capital efficient method for discovering and building products and services that people love-, comparing it with Agile.
Rick Simmons presents a launch process meant to introduce a team to Kanban in two days, focusing on the core concepts and techniques, and by setting the team on an improvement path.

Alan Shalloway discusses the challenges associated with transitioning companies to Lean and Agile methods on an enterprise scale. The interview discusses how Lean and Kanban can be used to encourage encourage incremental change and ongoing improvement, the cultural factors that can hamper Agile adoption, and why practices that benefit teams can actually harm the organization as a whole.

Recorded at the 10th anniversary of the agile manifesto signing, Jim Highsmith discusses how he works with executive management teams to introduce and integrate agile techniques into enterprise organizations from both the business and IT sides. He defines adaptive leadership and discuses adaptive ALM, continuous delivery, lean and Kanban methods.

This mini-book offers an easy to follow 10 step guide to taking the initial plunge and start using Lean principles to optimizing value and flow in your system. Each step consists of a section explaining “why” followed by examples of specific tools, practices and rules that have helped other teams better understand and optimize their system.

Scrum and Kanban are two flavours of Agile software development. So how do they relate to each other? Part I illustrates the similarities and differences between Kanban and Scrum, comparing for understanding, not for judgement.Part II is a case study illustrating how a Scrum-based development organization implemented Kanban in their operations and support teams.