All Videos Tagged lssc12 (limitedwipsociety) - limitedwipsociety

LSSC12: High Performance Operations: Using Lean and Kanban to Achieve High Maturity - Hillel Glazer

2012-07-25T02:26:29.826Z

Don't let the bureaucracy of everyday compliance issues get in your way of being lean and achieving excellence.
Hear about a revealing systematic approach that puts compliance properly in its place -- behind your pursuit of excellence.
Discover the secrets of incorporating non-value-added necessities into the value-added work stream.
One characteristic of the approach distinct from many lean initiatives is that it does not rely solely on incremental kaizen and "low-hanging fruit".
High Performance Operations looks at several facets including common mistakes that hinder high performance, the role of leadership, culture, trust, empowerment, learning and communication -- as prerequisites.
See how lean and kanban can be used to easily, seamlessly, effectively, and transparently incorporate compliance requirements into the flow of an operation. This also provides the insight and metrics for an operation to pull itself towards predictable, high-confidence performance -- the realm of high maturity -- while remaining agile and responsive.

LSSC12: The Systems Thinking Approach to Introducing Kanban - David J. Anderson

2012-07-25T02:22:07.159Z

While the design of kanban systems and visualizations is becoming well understood in the community and the concept that the Kanban Method is a way of catalyzing evolutionary change to existing process, there is still little understanding of how get started with a Kanban initiative. This talk will present the systematic approach employed by David J. Anderson to enable organizations to bootstrap a Kanban initiative. David will explain the approach to understanding the current circumstances, soliciting sources of dissatisfaction from all stakeholders via interviews and anecdotal evidence. He will then show how to develop an understanding of demand and capability breaking demand down by work type and required class of service. Workflow can then be studied for each work type by identifying a sequence of dominant activities for knowledge discovery. All of this input is used to develop a kanban system design. The new system is then socialized with stakeholders and its design points negotiated. Finally a rollout plan is produced and a kick-off meeting is held.

LSSC12 : Decentralizing Control: How Aligned Initiative Conquers Uncertainty - Reinertsen

2012-07-20T01:22:29.519Z

This presentation was given at the Lean Software and Systems Conference 2012 (LSSC12).

The situations we must manage span the range from deterministic to stochastic. On the deterministic end we have wonderful methods from the highly repetitive world of manufacturing. On the extreme stochastic end, completely unpredictable situations with an infinite number of possible conditions, each of unknown likelihood, planning is useless. Product development lies between these extremes – we deal with limited rather than complete uncertainty. Such conditions also appear in other domains. In this session Don Reinertsen will discuss the strategies of decentralized control that are used in the military. Such approaches are interesting because they work at large scale and they have avoided the natural tendency of self-organization to turn into local optimization

LSSC12: The Penguin and the Leviathan: Cooperative Human Systems Design - Yochai Benkler

2012-06-28T15:06:10.405Z

This presentation was given at the Lean Software and Systems Conference 2012 (LSSC12).

A decade ago, Wikipedia burst into a world not ready to comprehend it. Thousands of people cooperating effectively, without price signals to offer “incentives” or managerial hierarchy to direct efforts was simply impossible. And yet, it moves. And as it moved it combined with a deep shift across many disciplines, from biology and neuroscience to organizational sociology, experimental economics, and social psychology to paint a very different view of who we are as human beings. Slowly pushing back against decades of ever-refined analyses based on self-interested rationality, we begin to see that we are diverse beings; that a majority of us responds cooperatively to cooperative settings—we tend to treat well those who have treated us well, rather than take advantage of them; we tend to do what we think is right and fair, when it is clear in the setting what that is; we experience empathy, and it makes us more generous and trustworthy; we experience solidarity with others, and that makes us contributed more willingly to the group's goals. Moreover, explicit payments, the touchstone of mechanism design under universal self-interested rationality, turns out to have a much more complex relationship with motivation than simple addition. All this work in basic behavioral sciences combines with observations from organizational sociology, political science, management studies, and social software design to provide a basis on which to build a field of cooperative human systems design.

LSSC12: Understanding the Actual Customer Need Through ConOps - Mack McKinney

2012-06-26T20:08:34.534Z

This presentation was given at the Lean Software and Systems Conference 2012 (LSSC12).

Working closely with end users can help ensure complex systems meet not just the contractual specification but also operators’ and other stakeholders’ evolving needs in realistic operational environments. Gaining users’ strong support is crucial to maintaining funding for projects and programs in austere budget environment. But working with users is often difficult to arrange and fraught with challenges: They often disagree among themselves and change their opinions frequently. And which users should we contact and whose inputs should we consider? Users don’t speak engineering and engineers seldom speak “ops” so how can we have a meaningful conversation with them anyway? DOD contracts seldom contain any provisions for contacting or visiting with end users, nor does the USG want to pay for such discussions, so how can we arrange discussions with end users? Since there is no substitute for detailed operational discussions with end users of complex systems, an effective, efficient, reliable method must be found by systems engineers and project managers for the regular, methodical engagement of hands-on users of the systems we design and build. This presentation describes the Technical Concept of Operations (TechCONOPS) as the primary document for tying together users, buyers and designers. Then the briefer discusses the four most common user groups, when to involve each and what kinds of information we can typically get from them. This is followed by a brief discussion of how a robust TechCONOPS can drive modeling and simulation. Lastly the other two key communities (technologists and threat/intel specialists) are discussed in the context of their crucial contributions during regular revisits/updates to the CONOPS. Finally, several real-world examples of failed developmental systems (division air defense artillery system, UAV, imagery analysis software, others) illustrate common pitfalls of not building CONOPS and not involving hands-on end users early enough or often enough in system design and test.