The After Action Review is a simple and powerful tool to help a team learn from their experiences in order to gain immediate, concrete improvements in performance. It is a more general and widely useful approach than the retrospection.
this webinar is probably something you want to listen to if you are at all interested in Lean Software Development. This is the basic 60 minute seminar that Alan Shalloway gives all around the country on Lean Thinking. Definitely worth a listen.
This session provides an overview of BDSD. It presents the reasons an organization must become agile, not merely their teams, and why incremental delivery of products is an essential path towards this. Outline:
Many organizations start their agile transformation with a pilot project – that is, taking a single team agile. This fails to achieve enterprise success most of the time for several reasons. Amongst these are the team is often not the major impediment to business agility.
In this article, Kanban is described as a systems approach to software development that affects many different types of behaviors. Also mentioned are a few of the common misconceptions people have about Kanban in order to help clarify what Kanban is and is not.
Extended XP engineering practices is a set of practices building on XP, but extended for teams that are part of larger organizations. XP’s history was mostly with small teams. As such, it should not be surprising that many of its practices are oriented around the dynamics of small teams. Give
Most of the software quality improvement practices proposed over the years have focused on helping testers find defects in code rather than to prevent the defects in the first place. Product quality has suffered from this approach.
The common model of a product owner works well for small to medium scale Agile adoption. However, for large scale Agile adoption one must expand the role to include a product manager that works with the business stakeholders while the product owner focuses on driving the teams.
An anti-pattern is a commonly occurring activity that is counter-productive to the company doing it. A "Lean" anti-pattern is an anti-pattern that goes against Lean principles. That is, it violates the company’s attempts to be following Lean methods.
This session describes how Lean Software Development is based on Just-In-Time and utilization theory. It also covers the principles of Lean Software Development: “Optimize the Whole”, “Eliminate Waste”, and “Build Quality” in.
This session discusses the five reasons for agility: Business, clarity on customer needs, better project management, helping the team learn, and technical agility. It also discusses the need to limit the amount of work in process at any one time.
This session shows how agile methods are manifestations of Lean Principles. It also shows how having large projects that force people to work on multiple projects inherently lowers productivity and effectiveness. Some suggestions on how to improve this situation are given.
This session shows an alternative to Scrum-of-Scrums to get teams to work together. It also shows how to do product portfolio management to ensure working on those products/enhancements that will get the most value for the business.
Lean Software Development has deep roots. Lean jumped into the software world about a decade ago but has still mostly been considered an extension of the main body of Lean, which is rooted in manufacturing.