Comments on: 2004 essay: Lean Team Software Process http://leansoftwareengineering.com/2009/05/20/2004-essay-lean-team-software-process/ Essays on the Continuous Delivery of High Quality Information Systems Mon, 22 Feb 2010 09:08:24 +0000 http://wordpress.org/?v=2.9.1 hourly 1 By: Curious Cat Management Improvement Blog » Management Improvement Carnival #65 http://leansoftwareengineering.com/2009/05/20/2004-essay-lean-team-software-process/comment-page-1/#comment-5428 Curious Cat Management Improvement Blog » Management Improvement Carnival #65 Mon, 01 Jun 2009 14:45:05 +0000 http://leansoftwareengineering.com/?p=1366#comment-5428 [...] Lean Team Software Process by Corey Ladas - “The customer’s terms likely do not include any notion of defects-per-KLOC. The producer’s end is profit and reputation, which comes from managing cost and consistency. If TSP, or something related to it, helps us realize our ends, then (and only then) it is meaningful.” [...] [...] Lean Team Software Process by Corey Ladas – “The customer’s terms likely do not include any notion of defects-per-KLOC. The producer’s end is profit and reputation, which comes from managing cost and consistency. If TSP, or something related to it, helps us realize our ends, then (and only then) it is meaningful.” [...]

]]> By: Lean nello sviluppo di software | Encob Blog http://leansoftwareengineering.com/2009/05/20/2004-essay-lean-team-software-process/comment-page-1/#comment-5349 Lean nello sviluppo di software | Encob Blog Thu, 21 May 2009 06:59:06 +0000 http://leansoftwareengineering.com/?p=1366#comment-5349 [...] trovato questi due articoli che parlano dello sviluppo software in maniera lean: uno è di Corey Ladas, ex sviluppatore Microsoft, l’altro è un articolo di Eric Ries (autore del blog Lessons [...] [...] trovato questi due articoli che parlano dello sviluppo software in maniera lean: uno è di Corey Ladas, ex sviluppatore Microsoft, l’altro è un articolo di Eric Ries (autore del blog Lessons [...]

]]> By: Corey Ladas http://leansoftwareengineering.com/2009/05/20/2004-essay-lean-team-software-process/comment-page-1/#comment-5347 Corey Ladas Thu, 21 May 2009 03:02:23 +0000 http://leansoftwareengineering.com/?p=1366#comment-5347 What's interesting to me about this is how many ideas are already baked into such a short essay: * one-piece flow * customer pull * value-denominated work items * gemba / genchi genbutsu (go and see for yourself) * rolling wave planning * service-level agreements * inventory limits * value stream maps * workflow management * integrated security and reliability engineering * continuous integration * continuous deployment ...and that is on top of a process definition that is already based on Statistical Process Control, standard work, and continuous improvement. I started this essay in Spring 04, around the time of the first "Scrumban" process definition. This draft is from Autumn 04, according to the timestamped revision control logs. What’s interesting to me about this is how many ideas are already baked into such a short essay:

* one-piece flow
* customer pull
* value-denominated work items
* gemba / genchi genbutsu (go and see for yourself)
* rolling wave planning
* service-level agreements
* inventory limits
* value stream maps
* workflow management
* integrated security and reliability engineering
* continuous integration
* continuous deployment

…and that is on top of a process definition that is already based on Statistical Process Control, standard work, and continuous improvement.

I started this essay in Spring 04, around the time of the first “Scrumban” process definition. This draft is from Autumn 04, according to the timestamped revision control logs.

]]>