Manufacturing Methodologies

Manufacturing methodologies include:
Lean manufacturing

A lean organization understands customer value and focuses its key processes to continuously increase it. The ultimate goal is to provide perfect value to the customer through a perfect value creation process that has zero waste.

To accomplish this, lean thinking changes the focus of management from optimizing separate technologies, assets, and vertical departments to optimizing the flow of products and services through entire value streams that flow horizontally across technologies, assets, and departments to customers.

Eliminating waste along entire value streams, instead of at isolated points, creates processes that need less human effort, less space, less capital, and less time to make products and services at far less costs and with much fewer defects, compared with traditional business systems. Companies are able to respond to changing customer desires with high variety, high quality, low cost, and with very fast throughput times. Also, information management becomes much simpler and more accurate.

Software Development Methodologies

Methodologies include:
Lean Development (LD)
Agile Software Development
Crystal Methods
Dynamic Systems Development Model (DSDM)
Extreme Programming (XP)
Feature Driven Development (FDD)
Joint Application Development (JAD)
Rapid Application Development (RAD)
Rational Unified Process (RUP)
Scrum
Spiral
Systems Development Life Cycle (SDLC)
Waterfall (a.k.a. Traditional)

DevOps

DevOps promotes a set of processes and methods for thinking about communication and collaboration – between departments of development, QA (quality assurance), and IT operations. In some organizations, this collaboration involves embedding IT operations specialists within software development teams, thus forming a cross-functional team – this may also be combined with matrix management.

Working: do it multi-thread but beware the wait flags. Do not wait approval to do great things. Patch even if not perfect, do not wait for approval, failure is good. Work as a reactive intelligent unit, not on automation pilot. Automation pilot is also when you are too organized!

“In response to a message that it receives, an actor can: make local decisions, create more actors, send more messages, and determine how to respond to the next message received. Actors may modify private state, but can only affect each other through messages (avoiding the need for any locks).”

On software development there are laws on design and productivity, one of it is Conway’s law, and others applicable from the natural world, others really counterintuitive.

Organizations which design systems … are constrained to produce designs which are copies of the communication structures of these organizations.

— M. Conway

Corollary: organize your work, your teams, your organisation to work decoupled, decentralised in an unserialized way and feeling happy.