About: Lean software development is a research topic. Over the lifetime, 4977 publications have been published within this topic receiving 135273 citations.
TL;DR: You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Abstract: Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control.Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned.Fundamentals of XP include: Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders. Writing unit tests before programming and keeping all of the tests running at all times. Integrating and testing the whole system--several times a day. Producing all software in pairs, two programmers at one screen. Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity. Putting a minimal system into production quickly and growing it in whatever directions prove most valuable.Why is XP so controversial? Some sacred cows don't make the cut in XP: Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators--every XP programmer participates in all of these critical activities every day. Don't conduct complete up-front analysis and design--an XP project starts with a quick analysis of the entire system, and XP programmers continue to make analysis and design decisions throughout development. Develop infrastructure and frameworks as you develop your application, not up-front--delivering business value is the heartbeat that drives XP projects. Don't write and maintain implementation documentation--communication in XP projects occurs face-to-face, or through efficient tests and carefully written code.You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software. 0201616416B04062001
TL;DR: This book describes building systems using the deceptively simple process, Scrum, a new approach to systems development projects that cuts through the ocmplexity and ambiguity of complex, emergent requiremetns and unstable technology to iteratively and quickly produce quality software.
Abstract: From the Publisher:
Agile development methods are key to the future of flexible software systems. Scrum is one of the vangards of the new way to buy and manage software development when business conditions are changing. This book distills both the theory and practive and is essential reading for anyone who needs to cope with software in a volatile world.
Martin Fowler, industry consultant and CTO, ThoughtWorks
Most executives today are not happy with their organization's ability to deliver systems at reasonable cost and timeframes. Yet, if pressed, they will admit that they don't think their software developers are not competent. If it's not the engineers, then what is it that prevents fast development at reasonable cost? Scrum gives the answer to the question and the solution to the problem.
Alan Buffington, industry consultant, former Present, Fidelity Systems Company
Arguably the most important book about managing technology and systems development efforts, this book describes building systems using the deceptively simple process, Scrum. Readers will come to understand a new approach to systems development projects that cuts through the ocmplexity and ambiguity of complex, emergent requiremetns and unstable technology to iteratively and quickly produce quality software.
BENEFITS Learn how to immediately start producing software incrementally regardless of existing engineering practices or methodologies
Learn how to simplify the implementation of Agile processes
Learn how to simplify XP implementation through a Scrum wrapper
Learn why Agile processes work and how to manage them
Understand the theoretical underpinnings of Agile processes
TL;DR: In this article, the authors provide a framework for understanding the evolution of lean not only as a concept, but also its implementation within an organization, and point out areas for future research.
Abstract: The application of lean thinking has made a significant impact both in academic and industrial circles over the last decade. Fostered by a rapid spread into many other industry sectors beyond the automotive industry, there has been a significant development and “localisation” of the lean concept. Despite successful “lean” applications in a range of settings however, the lean approach has been criticised on many accounts, such as the lack of human integration or its limited applicability outside high‐volume repetitive manufacturing environments. The resulting lack of definition has led to confusion and fuzzy boundaries with other management concepts. Summarising the lean evolution, this paper comments on approaches that have sought to address some of the earlier gaps in lean thinking. Linking the evolution of lean thinking to the contingency and learning organisation schools of thought, the objective of this paper is to provide a framework for understanding the evolution of lean not only as a concept, but also its implementation within an organisation, and point out areas for future research.
TL;DR: The use of either lean thinking or agile manufacturing has to be combined with a total supply chain strategy particularly considering market knowledge and positioning of the decoupling point as agile manufacturing is best suited to satisfying a fluctuating demand and lean manufacturing requires a level schedule.