eXtreme Manufacturing (XM) is an iterative and incremental framework for manufacturing improvement and new product development that was inspired by the software development methodology Scrum and the systematic waste-elimination (lean) production scheduling system Kanban(かんばん(看板)).^{[not verified in body]}

It is often presented as the intersection between three contributing, component circles: that of Scrum (with its standard roles and responsibilities, its principles of iterative design and sprints, and of making work visible), of object-oriented architecture (emphasizing modularity of components, the interface/contract-first rather than contract-last approach to design, as borrowed from web programming, etc.), and of concepts from extreme programming (XP), a software development methodology, extended to engineering (including use of user stories, "pairing and swarming" work patterns, and ideas from test driven development).^{[not verified in body]} The framework also generally applies principles of behavior-driven development.^{[not verified in body]}

The name was coined in 2012 by Joe Justice, founder of Wikispeed, and Marcin Jakubowski, founder of Open Source Ecology, as a take-off of the name extreme programming (XP), a software development methodology. The XM framework, popularized by Justice and J.J. Sutherland,^{[not verified in body]} has a rich history,^{[not verified in body]} with origins that relate to the Japanese concept of a Kaizen (改善) or "improvement" business culture,^{[not verified in body]} and which predate the early implementations of agile software development.^{[not verified in body]}

XM has its origins in the intersection between several fields of study, namely Agile Project Management, Engineering (e.g. Mechanical, Materials, etc.), and Knowledge Management.^{[citation needed]} The name was coined in 2012 after Extreme Programming (XP) software development by Joe Justice, founder of Wikispeed, and Marcin Jakubowski, founder of Open Source Ecology.^[1]

In 1986, Hirotaka Takeuchi and Ikujiro Nonaka wrote an HBR article on Scrum, entitled "New New Product Development Game,"^{[2][subscription]} a treatment considered seminal.^[3] This work challenged the business community to adopt a more holistic approach toward achieving goals; now Scrum is considered a best practice in project management.^{[according to whom?][citation needed]}

As Nonaka and Takeuchi progressed in their careers, they continued to collaborate and wrote The Knowledge Creating Company.^[4] XM leverages a Takeuchi and Nonaka tenet, that the "most powerful learning comes from direct experience" and that "managers in Japan emphasize the importance of learning from direct experience."^[4]

XM uses a prioritized product backlog as the primary work input queue,^[jargon] where work is visualized in an open area generally on a single team Kanban Board.^{[jargon][citation needed]} Every XM team has a Scrum Master and also a Product Owner,^{[clarification needed]} who together with the team help to ensure that Agile/Lean principles are followed.^[5] In XM the Scrum Master has some critical responsibilities, including to:^{[citation needed]}

• communicate with the product owner,
• identify and remove impediments,^{[clarification needed]}
• ensure test driven development (TDD) principles are followed,^[jargon] and
• manage team WIP limits, which may vary with team size.^{[clarification needed][jargon]}

The product owner represents the customer, and provides the overall vision and must serve as the product expert.^{[citation needed]}

The Agile Software Development Actors found in Agile and Scrum are present in XM.^{[citation needed]} XM does not require, but does encourage TDD.^{[clarification needed][citation needed]} Ideally, XM should adhere to the 10 Principles of XM outlined by Peter Stevens:^{[6][citation needed]}

1. Optimize for change,^{[clarification needed]}
2. Object-oriented, Modular Architecture,
3. Test Driven Development.
4. Contract-First Design,^{[clarification needed]}
5. Iterate the Design,
6. Agile Hardware Design Patterns,^{[clarification needed]}
7. Continuous integration Development,
8. Continuous Deployment Development,^{[clarification needed]}
9. Scaling Patterns,^{[clarification needed]} and
10. Partner Patterns.^{[clarification needed]}

According to Stevens, these "principles and patterns do not represent the final wisdom on Agile manufacturing, but rather a work-in-progress… [toward] the discovery of better ways to manufacture things."^{[6][self-published source?][better source needed]}

A number of prototype cars have been developed by separate companies using the XM process.

In 2008, in response to the Automotive X Prize sponsored by Progressive Insurance—a $10 million prize aimed rewarding the design and construction of a car capable of fuel efficiency at the 100 miles per gallon (m.p.g.) mark, while achieving "road-legal safety specifications"^{[7][subscription]}—Joe Justice and team Wikispeed, composed of 44 members from 4 countries, used XM to achieve what Fortune magazine called the "seemingly impossible:" application of tools formerly largely devoted to software manufacturing, to the development of a functional automotive prototype in three months time.^[7][8] Even more remarkable than the 100 m.p.g. car was an impressive rate of acceleration: from 0 to 60 m.p.h. in less than 5 seconds.^[9][10] The success—finishing 10th in the mainstream class, and "outrunning more than one hundred other cars from well-funded companies and universities around the world"— led to an invitation to team Wikispeed to showcase their prototype at the Detroit auto show.^[7]

Companies use XM as a way to challenge their employees to develop new skills and learn the power of teamwork to solve complex problems. For example, in 2013, Lockheed Martin (Sunnyvale, CA) challenged 200 of its engineers to build a 100 m.p.g. car in a single day; the challenge was met and the team's car was sold for $25,000.^[11] Another such example is opensourceecology.org,^[12][13] whose Global Village Construction Set is developing and building affordable industrial machines, and publishing the designs on-line for free.^[14]

• Axiomatic product development lifecycle
• Design–build
• Systems development life-cycle
• New product development
• Product lifecycle management
• Engineering design process
• Fluid production systems^[15]