No True Lean Thinking or Agile Software Development. Posted on November 22, 2010 Comments (0) “There is no true value of any characteristic, state, or condition that is defined in terms of measurement or observation.” – Dr. W. Edwards Deming. The value depends on your operational definition. Once you operationalize management ideas in a real organization it necessarily should have differences from how it is operationalized elsewhere. As Deming said there are no effective simple recipes for management. It is one of the frustrations people have with Dr. There is value in being able to think and discuss ideas in a broader context than your organization. One of agile’s guiding principles is individuals and interactions over processes and tools.
There are principles that seem to me necessary to, for example, consider an effort as lean management. Thoughts on No True Agile, No True Lean, No True Latte Related: Dr. On a personal level agile software development is the perfect melding of my career. Implementing Lean Software Development. "This remarkable book combines practical advice, ready-to-use techniques, anda deep understanding of why this is the right way to develop software.
I haveseen software teams transformed by the ideas in this book. "--Mike Cohn, author of Agile Estimating and Planning"As a lean practitioner myself, I have loved and used their first book for years.When this second book came out, I was delighted that it was even better. If youare interested in how lean principles can be useful for software developmentorganizations, this is the book you are looking for. The Poppendiecks offer abeautiful blend of history, theory, and practice. "--Alan Shalloway, coauthor of Design Patterns Explained"I've enjoyed reading the book very much. I feel it might even be better than thefirst lean book by Tom and Mary, while that one was already exceptionallygood! Eliminer les sources de gaspillage : les 7 gaspillages Lean des projets informatiques. Boost productivity with lean software development.
Lean software development is one of the latest hot topics at strategy consultancies like McKinsey. A report conducted by McKinsey dubbed "Applying Lean To Application Development And Maintenance," says implementing the approach can lead to productivity gains of between 20% and 40%, and that quality and speed of execution can improve markedly within a matter of months. Both valuable benefits when the cost of developing and maintaining applications now accounts for about 50% of the average IT budget - a figure that is set to rise in the future. So, on the surface of it, lean software development sounds like a boon.
But what is it, where does it come from and how realistic is it for most organisations not only to go down this route, but also to achieve the promised improvements? The concept was originally developed by Henry Ford in the 1920s as a means of preventing overproduction, while at the same time improving response times to changing customer needs. Email Alerts. Du Lean Software Development au Lean IT. Un effort Lean généralisé à l’ensemble de la DSI permettra d’étendre les succès récents de certaines équipes de développement à toutes les activités IT de la société.Plus fort qu’une simple dose de LSD (Lean Software Development, le Lean appliqué au développement logiciel), je fais l’hypothèse que nos DSI préféreront bientôt les cures de LIT (Lean IT, le Lean appliqué à toute la DSI). Des équipes de développement performantes Nous constatons chez nos clients que les équipes de développement voient leur productivité et la qualité de leurs livrables augmenter considérablement en suivant les pratiques du Lean Software Development (et les pratiques cousines des méthodes agiles).Le Lean appliqué à ces équipes de développement conduit notamment à une réduction importante de leur temps de cycle (c’est-à-dire le temps entre l’expression d’un besoin par la MOA et la livraison d’un logiciel fonctionnel et déployable par cette équipe de développement).
De nouveaux goulots d’étranglement Conclusion. Lean Software Developemnt - discover and deliver value to end users - Selleo Blog. 0xing Page: 1 2→ The core principle of the lean approach is to focus on value for the customer and at the same time eliminate waste. “Value” is defined as any action or process that the customer would be willing to pay for. “Waste” in turn is any action or process that does not add value. The focus on value In software value is what users will value once they start using the software. Making improvements little-but-often creates a learning environment which allows to truly discover and deliver value to end users.
Eliminate waste Lean defines waste as anything you do that does not add customer value or delays the delivery of value to customers. Partially done work Some examples of partially done work include: specifications and requirement documents created too earlycode which is not covered with testscode which is not deployed to production xing Tomasz Bąk Tom is a Rails developer with a wide range of API integration, JavaScript and cross-platform mobile programming experience.
« lean software development » sur SlideShare.