eXtreme Manufacturing

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(かんばん(看板)).

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). The framework also generally applies principles of behavior-driven development.

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, has a rich history, with origins that relate to the Japanese concept of a Kaizen (改善) or "improvement" business culture, and which predate the early implementations of agile software development.

Origins
Getting Started at Agile DC 2013.

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. 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.

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]

Concept

XM uses a prioritized product backlog as the primary work input queue, where work is visualized in an open area generally on a single team Kanban Board. Every XM team has a Scrum Master and also a Product Owner, 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:

  • communicate with the product owner,
  • identify and remove impediments,
  • ensure test driven development (TDD) principles are followed, and
  • manage team WIP limits, which may vary with team size.

The product owner represents the customer, and provides the overall vision and must serve as the product expert.

The Agile Software Development Actors found in Agile and Scrum are present in XM. XM does not require, but does encourage TDD. Ideally, XM should adhere to the 10 Principles of XM outlined by Peter Stevens:

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

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]

Contemporary interests
Team Wikispeed and Agile DC conference attendees celebrating success.

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]

gollark: ++data list
gollark: I had a network issue there, but the server does NOT run on my laptop so who knows.
gollark: Oh no, just Google beeing bees.
gollark: There appear to be beeapios incursing into my network, weird.
gollark: * bridge, not bot

See also

References
  1. Tincq, Benjamin (25 October 2012). "From Henry Ford to Joe Justice: WikiSpeed, Manufacturing in the Age of Open Collaboration". OuiShare Magazine. Archived from the original on 27 February 2014. Retrieved 21 October 2015. Alt URL
  2. Takeuchi, Hirotaka; Nonaka, Ikujiro (1 January 1986). "New New Product Development Game". Harvard Business Review: 137–146. Retrieved 21 October 2015. Product #: 86116-PDF-ENG[subscription]
  3. Sutherland, Jeff (2011-10-22). "Takeuchi and Nonaka: The Roots of Scrum". Scrum Inc. Retrieved 8 July 2018.
  4. Nonaka, Ikujirō; Takeuchi, Hirotaka (1995). The Knowledge-creating Company: How Japanese Companies Create the Dynamics of Innovation. Oxford University Press. p. 3. ISBN 9780199762330. Retrieved 21 October 2015.
  5. "Principles behind the Agile Manifesto". AgileManifesto.org. Retrieved 15 November 2013.
  6. Stevens, Peter (2013). "Extreme Manufacturing Explained". Retrieved 21 October 2013.
  7. Kupp, Martin; Dahlander, Linus; Morrow, Eric (8 November 2013). "Cases: Team Wikispeed: Developing Hardware the Software Way". Harvard Business Review. Retrieved 21 October 2015. ES1391-PDF-ENG[subscription]
  8. Hagel III, John; Brown, John Seely (18 June 2012). "Strategy: How Companies Ought to Train Their Staffers". Fortune. Retrieved 21 October 2015.
  9. Denning, Steve (10 May 2012). "Leadership: Wikispeed, How A 100 mpg Car Was Developed In 3 Months". Forbes. Retrieved 21 October 2015.
  10. "Home". Wikispeed. 2012-06-18. Retrieved 2015-10-21.
  11. Louie, David (3 December 2013). "Lockheed Martin Challenges Engineers to Build a Car in 1 Day". ABC7 News. Retrieved 21 October 2015.
  12. "Open Source Ecology". Open Source Ecology. Retrieved 2015-10-21.
  13. Jakubowski, Marcin (March 2011). "Open-Sourced Blueprints for Civilization". Ted2011. Retrieved 21 October 2015.
  14. "Civilization Starter Kit DVD v0.01". Open Source Ecology. 2015-01-14. Retrieved 2015-10-21.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.