Beyond | IT : lean

Poppendieck: Ten Simple Rules of Lean Programming

john.mullinax — Wed, 06 Feb 2008 06:31:00 GMT

After my last post referring to a webinar by Durward Sobek, he got me thinking again about the fantastic work of Mary and Tom Poppendieck. They are such a great force for evangelizing lean software development. I highly recommend their two books on the subject.

One of the things I especially like is that they boil down how you can apply lean to software development in a way that's clear and practical, and also does justice to the core philosophical principles of Lean Thinking. Not always easy, that. Even so, it's crucial to do -- an understanding of the core principles will allow you to apply the lean software concepts when situations and context change (as they will).

In that vein, I especially like this powerpoint slide deck that the Poppendiecks have posted on their website, called Lean Thinking: the theory behind agile development (2002). Here's a nugget of insight from slide 9:

Ten Simple Rules of Lean Programming:

Eliminate waste
Minimize artifacts
Satisfy all stakeholders
Deliver as fast as possible
Decide as late as possible
Decide as low as possible
Deploy comprehensive testing
Learn by experimentation
Measure business impact
Optimize across organizations

See the deck for great examples and explanations about the list above, and more.

And BTW, be sure to check out the last slide -- it's a bibliography slide. The reading list could be an intense graduate seminar on lean thinking / lean management!

Technorati Tags: Lean thinking,software development methods,Lean software

Applying Lean Thinking in software development... model Lean product development

john.mullinax — Mon, 04 Feb 2008 21:07:00 GMT

I like what Mark Ramm says here.... There's much that software development can gain from Lean manufacturing. It's not that software development operations should adopt manufacturing processes, per se -- but many of the principles of lean thinking can be extracted from lean manufacturing and applied to improve software development.

That said, If you're looking for a model to help you apply lean thinking to software, you may find lean product development to be an even better fit than lean manufacturing.

I saw a webinar on Lean Product and Process Development a while back that was put on by Durward Sobek through the Lean Enterprise Institute. I captured a few notes from the webinar on what Durward called "the basics":

The object of the game is to make a profit consistently
The operational value stream generates the profit
The rate and quality of output from development depend critically on knowledge.
Generate knowledge through set-based concurrent engineering.
Grow teams of experts who can use, generate useful knowledge
Establish and support entrepreneurial system designers
Eliminate overburden, instability, and waste through cadence, pull, and flow.

For much more, check out this book by Allan C. Ward called Lean Product and Process Development.

Update: I heard from Durward Sobek, and you can see an archived version of the webinar here for yourself!

Technorati Tags: Lean,software development methods

Enterprise Agility | NetObjectives: SIPOC helps you figure out where to start

john.mullinax — Wed, 30 Jan 2008 22:33:02 GMT

Some very good basic advice here from Jim Trott at NetObjectives about applying lean principles and systems thinking to improve software development. An excerpt:

"When it comes to analyzing where to start in helping a development organization, it often makes sense to talk to the Business, which is the customer of the dev group, as well as upstream to the Operations, which supplies the dev group. A standard lean technique is to do a simple SIPOC (Supplier-Input-Process-Output-Customer) to be explicit about who and how the organization interacts with the system. All too often, this simple step is forgotten as we are focused on building product.
"For example, a local team might already be reasonably productive, even without Scrum. But they are thrashing because their Business customer is not ready to work with them when they need answers. Or the change management system takes weeks to schedule a user acceptance test. These are structural issues dealing with upstream inputs and downstream outputs over which the local team has no control. Attack these root causes of thrashing and you improve the flow. Only then will it make a difference to improve the team."

A quick read and worth a look!

Technorati tags: Lean, Systems thinking, Agility

Optimizing the consumer value stream

john.mullinax — Wed, 04 Jul 2007 01:33:45 GMT

Technorati Tags: systems thinking , lean , consumer experience , web 2.0 , next web , loyalty Are you thinking about your consumers' personal value stream? The businesses I generally work with are familiar with the notion of a value chain or a value...(read more)

A GREAT collection of Lean Software Development Info

john.mullinax — Thu, 14 Jun 2007 16:26:00 GMT

Technorati Tags: systems thinking , lean manufacturing , lean , six sigma , learning , software development methods I just stumbled across Brad Appleton's fantastic collection of resources on Lean and Agile software development . Books, presentations,...(read more)

Why bother with lean? Because it Rocks!!

john.mullinax — Thu, 18 Jan 2007 03:13:00 GMT

My last post left off with the following set of questions:

Why bother with lean? Really, why would we want to imitate an old and slow industry like manufacturing? Especially given it's long and steady decline in the United States. With the acceleating pace of change in the world, we need new ideas that can help us be agile and adaptive, don't we?

While it's not always an easy journey, I find it does have it's rewards. In the manufacturing industry, few if any seriously debate the value of being lean. Basically, everyone wants to be lean and the debates today are around how to best do it. Lean thinking has literally transformed manufacturing around the world. Moreover, other industries support lean as well. For example, retail establishments like Walmart support manufacturers in continuously improving their lean-ness by providing them demand chain visibility. REI uses the principles of "flow" and "evenness" to make optimize their checkout lines, as have most retail financial service operations (i.e., bank branches) -- though lean adopters are not always consciously thinking about lean when they take these actions. In many cases, people are simply copying what has worked elsewhere.

Copying others is definately a low-effort way to make changes. It can work well in the short run, and can be genuinely helpful to long-term learning and oganizational growth. That said, I suspect the consciously early-adopters of lean in a new industry do so because they want to lead their industry. As their successes are copied, competitors may gain as well. But in the long-run, an understanding of the lean principles and a commitment to continuous improvement in a rapidly changing world allow lean thinking companies to generally increase their performance leads over time versus those who blindly copy yesterday’s (or this morning’s) actions without understanding why. I suspect that near the end of the lean adoption cycle in an industry -- for example, where we are now in the Manufacturing industry -- lean adoption and lean thinking get taken up by the last of the "hold outs" as a matter of survival more than a matter of leadership.

The funny thing is that people often view the manufacturing industry as old and slow. In today's vernacular, people want their organizations to be adaptive so they can cope with the ever accelerating pace of change. Fortunately for all of us, a framework for being adaptive already exists -- in fact, it's fundamentally built into lean thinking: understand your environment, experiment, apply improvements, and repeat.

It's worth noting that this core nugget of lean is also the fundamental idea behind the Deming Cycle (Plan-Do-Check-Act), as well as Six Sigma (Define-Measure-Analyze-Improve-Control). Thanks to John Boyd, US Army teaches it's soldiers the OODA Loop (Observe-Orient-Decide-Act) -- essentially the same idea, which Boyd built from Godel's Incompleteness Theorem, Heisenberg's Uncertainty Principle, and the Second Law of Thermodynamics- the entropy of a closed system increases. Not the first to do so, Boyd extended the idea to social evolution, and believed that the decision cycle is the central mechanism of adaptation. Jack Welch said (paraphrasing) that if change on the outside of your organization is faster than change on the inside, you're in trouble.

Though I certainly don't put myself in the same category as the giants above, I've also written about this in a different forum as Respond-Sense-Learn, based onthe ideas of Philosopher Karl Popper, as well as Peter Senge (minimizing Deming's "plan" component as a step toward greater agility).

Finally, what does any of this have to do with Microsoft? Well, quite a bit, actually. Taken together, Microsoft technologies provide an outstanding platform to help you build an adaptive organization. For example:

Bringing business intelligence to all parts of the enterprise so that workers up, down, and throughout the organization can make faster, more insightful decisions with higher success rates at each of the multiple decision events they face during a typical day.
Sharing that information with people in the flow and context of their business processes, be they structured or semi-structured/unstructured -- as so many business processes actually are.
Sharing information with visualizations that actually inspire insights, and within tools people already know and that enable immediate actions to be taken.
Rapid and easy business process composition, prototyping, experimentation, and implementation, including tools to monitor and assess the performance and "fitness" of specific business process variations against measures that matter to you.
The capability to use that same data about business process "trials" -- and potentially every prototype and production implementation is also a trial -- to build and execute simulation models that create even greater insight about your business so you can understand what truly drives the results you care about.
Ironically, the deep understanding of what drives your results that can come from enabling business intelligence throughout your organization, business process experimentation, and business simulation is actually the key to reducing information overload and controlling the flood of data that threatens to drown people's ability to do productive work. By understanding the things that really drive results, we can target our activities and only report, share, and analyze the things that actually matter.
And if you find yourself in an environment of ontological uncertainty, the collaboration and communication platform provides a wide variety of communication channels to ensure folks understand the organizational principles that will enable them, as individuals and team members, to drive in a common direction toward an uncertain future.

I believe in Boyd's idea that decision making is the primary mechanism for adaptation. The reality is that, whether we realize it or not, we all live in a world where the ability to make better decisions faster about the things that truly matter will ultimately determine our success. Many folks will make speedy, apparently "effective" decisions about things that appear to matter -- but really don't drive desired results because they are themselves driven by other "confounding" variables. Perhaps even more people will make slow, ponderous decisions on topics that may or may not drive results -- but cause opportunity and value to slip through their fingers. And a comparatively small group of people will make rapid, insightful decisions about things that truly do drive results. Over time, these people will work for the leading companies in their respective fields, because they will have created that success.

Whatever the labels you decide to use, I invite you to join me on the journey!

Lean Everywhere

john.mullinax — Thu, 18 Jan 2007 02:29:00 GMT

Lean manufacturing has been around for a long time. Many of the principles of lean were identified in Henry Ford's work before the US Great Depression of the 1930s, and significantly extrended by Kiichiro Toyoda and Taiichi Ohno during the middle of the last century. Today, Toyota is regarded as the pre-eminent practioner of Lean Manufacturing, and "Lean Thinking", and the company is unique in many ways. A few diverse (but non-random) examples:

Toyota is the only automotive company to grow from a looming/weaving company.
Toyota is the only automotive company that has invested in research to create a "car operating system" (yes, I'm talking software OS; not an operating methodology)
Toyota is poised to overtake GM as the world's largest automotive company, perhaps as early as 2008. Despite a dramatic increase in competition in the key US automotive market, Toyota has consistently increased it's sales in the neighborhood of 10% per year over the last 10 years.
Toyota has been extraordinarily open about its manufacturing processes -- guiding thousands of visitors, many competitors, on tours of its operating facilities -- and yet no other company seems able to duplicate its successes.

Each of these unique Toyota attributes raises questions, but I'd like to dwell today on the last point. How come no one has been able to duplicate Toyota's success, despite much concerted effort and an extraordinary openess by Toyota itself to competitors?

In a nutshell, the "secret sauce" is not the operating method or visible artifacts -- it's the thinking process. The relentless focus on experimentation, continuous learning, and the application of that learning to make improvements as a way of life. This thinking process does not make Toyota a lean paragon by itself -- it is applied together with the idea that we should seek to provide the right goods and services, at the right price, at the right time, and at the right place with as little waste as possible.

The idea is striking in its simplicity. Basically, Toyota applies a scientific approach to meet consumer needs with minimum waste. Of course, being simple does not equal being easy. Also, the scientific approach does not replace the need for sound strategy, good people, and strong execution in all of their functional organizations -- in fact, this is one of the key insights: these traditional fundamentals of management are not separate things from the experimentation, learning, and the application of learning for improvement. The scientific thought processes infuse *how* these functions work.

Equally striking, because this is not actually a manufacturing method, but is instead a thought process applied to meeting consumer needs without waste, we can all benefit from lean thinking -- even if we don't work in a plant or in a manufacturing group. Just as marketing, finance, product development, and customer service organizations within manufacturering companies can benefit form lean thinking, so too can financial, consumer, communications, and service industries benefit from lean.

This is not just my idea (if only I were smart enough to figure this one out by mysef!). James Womack, lean guru and founder of the Lean Enterprise Institute advocates applying lean principles widely -- far beyond traditional manufacturing industries. In particular, healthcare stands out as a beautiful target. It's an industry that is actually a composite of the service, financial, manufacturing, and retail industries. If ever there was an industry that consumers wanted to improve it's ability to provide the right goods and services, at the right price, at the right time, at the right place, with minimum waste, it is the US healthcare industry. I don't say this lightly, or smugly, but clearly there is a lot of discontent with healthcare in the United States.

Naturally, there's a lot more to applying Lean thinking than what I've described in a few paragraphs. People spend their lives working to improve their ability to think lean, and apply lean principles. Understanding the various types of waste all around us, developing the ability to see the waste for what it is, and learing to effectively use tools to reduce the waste in our environment is a continuous journey. And I should note that while I'm a fan of lean thinking, I'm certainly not a "Lean Expert". Work, and growth, is required -- for me as much as anyone else.

Well, That's for my next post!

Update: That "next post" is here.