Following a request from a Discussion Forum member about information on the application of Lean in software development, several members provided advice and insight about the best tools to use. Responses varied from the use of Lean to control the flow of IT projects, to tying in business process execution language to BPM software, to the adoption of Agile development methods. Here’s what our readers had to say:
Posted by: Emma Chen-Banas
Posted on: Jan. 15, 2010
Hi. I’m doing research about Lean software development to explore any opportunity for my IT organization. Any information, idea or past experience on this topic is highly appreciated. Thanks.
Posted by: Jonathon Andell
Posted on: Jan. 27, 2010
I’m not sure this contribution will serve for “research” purposes, but here it is. My perception is that Lean itself is unlikely to improve the writing of code, unless the code itself is going to contribute to some form of Lean implementation.
However, the methods of Lean can be used to manage the flow of projects. Many organizations use “push” processing to start a ton of projects, all of which spend most of their time in queue at various process junctures. Lean can help organizations develop objective ways to sequence and assign projects. Ultimately, a Lean software shop should be able to deliver more projects at higher quality than a shop using “push” methods.
Posted by: MBBinWA
Posted on: Feb. 10, 2010
Lean applies to development as it would to any business process – identify the waste (non-development activities) and find ways to eliminate or minimize it. I also recommend looking into Agile development. In my experience, the iterative approach and voice of the customer emphasis bring the feel of a Kaizen to development teams.
Posted by: Charles Spence
Posted on: Feb. 10, 2010
If you’re interested in Lean software development, then you need to explore poppendieck.com. This site is [from] Mary and Tom Poppendieck, who are, by most accounts, the leading source for Agile/Lean development.
Posted by: Warren Hodgett
Posted on: Feb. 22, 2010
Hi Emma. I’m not sure if I can be of help, but maybe. I’m currently working for a company called T-Impact, and we specialize in automation of business processes. We have three tools to do this: Lean Six Sigma (DMAIC), [business process management] BPM software and [business process execution language] BPEL. The latter may be something you’re familiar with.
Essentially, we have been able to prove that BPEL, when tied with BPM and Lean Six Sigma, can very quickly automate a process without the need to alter the underlying systems (BPEL being used as a process orchestration layer which sits above and can interact with the underlying systems). This means that changes to IT can be done very quickly by creating a clever front end. BPEL links directly to BPM, which is used to map, model and simulate the business process.
Posted by: Don Strayer
Posted on: Feb. 24, 2010
I agree. Also consider Scrum. The impetus for the Agile manifesto and Agile software development methods arose from Lean thinking. I’ve worked with organizations that put a lot of effort into value stream mapping and other Lean techniques to reduce waste in their waterfall [systems development life cycle] SDLC and management oversight focused process management processes. They just didn’t get it. Agile is Lean.