LFC Le kanban est un terme japonais signifiant « étiquette », c'est une simple fiche que l'on fixe sur les bacs ou les conteneurs de pièces sur une ligne de production, d'assemblage ou dans une zone de stockage. Mais avant tout, le kanban est une méthode de travail qui a pour but de définir les modalités de mise en route d'une production en flux tirés. C'est un système d'information qui fonctionne entre deux postes de travail et limite la production du poste amont aux besoins exacts du poste aval. Ce sont donc les commandes clients qui déclenchent automatiquement la fabrication par remontée des ordres depuis la sortie des produits. Ce type de fonctionnement permet d'améliorer la productivité grâce à: Une précision de production Une flexibilité Une consommation réelle Une production par petits lots Des petits stocks Un management visuel Une meilleure communication Programme de formation
Why Continuous Deployment? Of all the tactics I have advocated as part of the lean startup, none has provoked as many extreme reactions as continuous deployment, a process that allows companies to release software in minutes instead of days, weeks, or months. My previous startup, IMVU, has used this process to deploy new code as often as an average of fifty times a day. This has stirred up some controversy, with some claiming that this rapid release process contributes to low-quality software or prevents the company from innovating. If we accept the verdict of customers instead of pundits, I think these claims are easy to dismiss. Far more common, and far more difficult, is the range of questions from people who simply wonder if it's possible to apply continuous deployment to their business, industry, or team. The particulars of IMVU’s history give rise to a lot of these concerns. One large source of waste in development is “double-checking.” Why does it work? Continuous deployment also acts as a speed regulator.
L'Extreme Programming Depuis les débuts de l'informatique commerciale dans les années '60, plusieurs méthodologies de développement de logiciel ont vu le jour. Le modèle en cascade et ses dérivés ont connu un grand succès, mais leur lourdeur et rigidité sont de sérieux handicaps. Extreme Programming propose de remplacer certaines notions acquises par des idées révolutionnaires, et de rendre le développement de logiciel efficace et agile. I-A. La petite histoire d'une grande industrie▲ L'histoire du développement de logiciels est intimement liée à l'histoire de l'industrie informatique. I-B. Le transistor a été inventé en 1948, et l'ordinateur sous sa forme actuelle existe depuis les années '50. Les années '70 ont vu l'apparition des langages C, Pascal et Basic, de Unix, du circuit intégré, de Apple, Intel et Microsoft, et des premiers micro-ordinateurs. I-C. Des méthodologies de développement sont apparues à différents moments durant la révolution informatique. I-D. II-A. II-B. III-A. III-B. III-C. III-D.
Why minimalist software wins at workflow Recently I’ve been evaluating software to help support agile/scrum development on our team, and ideally to roll into our NASA Code product for others to use. We’re already married to Trac, so we’ve been playing with Agilo and are looking at some of the other agile plugins for Trac. Unfortunately they’re all so heavyweight, despite some that claim not to be. I came back to a realization I’m sure a lot of us have had: most software sucks. This is part of the reason most enterprise software sucks so terribly. A lot of us have learned that less software is more effective. The other thing about minimalism is that, like abstraction (another form of compression), everything you leave in the design makes such a huge difference. Luckily, minimalism buys you a sort of abstraction that can enable projection. Coming back to Timothy’s “a board and post-its” remark, why do you even need software? Software does have a couple strengths. However, I’m seeing a lot of this in agile/scrum software.
Agile software development Agile software development is a set of principles for software development in which requirements and solutions evolve through collaboration between self-organizing,[1] cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, and continuous improvement, and it encourages rapid and flexible response to change.[2] Agile itself has never defined any specific methods to achieve this, but many have grown up as a result and have been recognized as being 'Agile'. The Manifesto for Agile Software Development,[3] also known as the Agile Manifesto, was first proclaimed in 2001, after "agile methodology" was originally introduced in the late 1980s and early 1990s. The manifesto came out of the DSDM Consortium in 1994, although its roots go back to the mid 1980s at DuPont and texts by James Martin[4] and James Kerr et al.[5] History[edit] Incremental software development methods trace back to 1957.[6] In 1974, E. The Agile Manifesto[edit] Agile principles[edit]
Why Pair Programming Works Pair programming is like magic in more ways than one. It dramatically improves programmer productivity and reduces bug count, and yet it does so through a technique that’s completely counter-intuitive. You can’t help but think that there’s some trick yet to be exposed; that pair programming is just slight of hand. In this article, I will endeavor to pull back the curtain and reveal the secrets of the pair programming magicians. Specifically, I identify six reasons pair programming succeeds: Continuous Code ReviewFewer blockagesMasking distractionsGuaranteed focusMultiple points of viewReduced training cost and time Continuous Code Review One of the maxims of extreme programming (XP) is to turn all the dials to 11. Furthermore the feedback is more likely to be useful that that from classic code reviews. Finally, feedback can be incorporated more quickly and easily when it’s given earlier in the process. And if you’re not already doing code reviews? Fewer blockages Why wait? Guaranteed Focus
Kanban et Scrum - tirer le meilleur des deux Ce livre fait partie de la collection de livres InfoQ "Enterprise Software Development". Avec ce livre, vous apprendrez ce qu'est Kanban, ses forces et ses limites, et quand l'utiliser. Vous apprendrez également comment Kanban peut améliorer Scrum, ou tout autre outil que vous utilisez, et à quel moment c'est possible. Henrik montre clairement que le plus important n'est pas l'outil avec lequel on commence, mais la façon dont on améliore constamment son utilisation et comment on développe progressivement son ensemble d'outils. Mary Poppendieck, auteur de plusieurs livres de référence sur le Lean Software Development. Je suis très heureux qu'Henrik Kniberg et Mattias Skarin aient émergé comme des leaders dans ce domaine. David Anderson, fondateur de l'Agile Project Leadership Network, membre fondateur de Feature Driven Development (FDD), et auteur de livres sur l'agilité. 7 commentaires Henrik Kniberg, Mattias Skarin Lire l'article. Article lu 7368 fois.
An Agile Bibliography Relevance Agile Bibliography Tags: agile and bibliography You can't learn agile development by reading a book. Our customers and students frequently ask us how they can learn more about how we work. Three Essentials Almost all technical books are about particulars: particular processes, platforms, techniques, or tools. The Pragmatic Programmer: From Journeyman to Master, by Andrew Hunt and David Thomas. Agile Software Development: The Cooperative Game (Second Edition) by Alistair Cockburn. Peopleware: Productive Projects and Teams (Second Edition) by Tom DeMarco and Timothy Lister. Software Development The Mythical Man-Month: Essays on Software Engineering (Anniversary Edition), by Fred Brooks. Patterns of Enterprise Application Architecture by Martin Fowler. Waltzing with Bears: Managing Risk on Software Projects by Tom DeMarco and Timothy Lister. Domain-Driven Design: Tackling Complexity in the Heart of Software by Eric Evans. I.M. Agile Methods Reflection and Responsiveness