{"id":1557,"date":"2012-06-11T00:00:00","date_gmt":"2012-06-10T22:00:00","guid":{"rendered":"https:\/\/wwwneu.strehle.de\/tim\/weblog\/archives\/2012\/06\/11\/1502\/"},"modified":"2012-06-11T00:00:00","modified_gmt":"2012-06-10T22:00:00","slug":"1502","status":"publish","type":"post","link":"https:\/\/www.strehle.de\/tim\/weblog\/archives\/2012\/06\/11\/1502\/","title":{"rendered":"How to Advance Lean Software Development (Beyond the &#8218;Toyota Way&#8216;)"},"content":{"rendered":"<p>Matthew Heusser at CIO.com \u2013 <a href=\"http:\/\/www.cio.com\/article\/706793\/How_to_Advance_Lean_Software_Development_Beyond_the_Toyota_Way_\">How to Advance Lean Software Development (Beyond the &#8218;Toyota Way&#8216;)<\/a>:<\/p>\n<p>\u201cLean manufacturing focuses on delivering one part, end-to-end. This is sometimes called one-piece flow. [\u2026] To get to one-piece flow, we&#8217;ll eliminate multi-tasking.<\/p>\n<p>[\u2026] Instead of &#8222;pushing&#8220; work to the next step in the chain, we pull it. This means testers don&#8217;t take on work until they are ready for it. [\u2026] [The programmers] have to figure out how to help the testers\u2014 by testing themselves, perhaps, or by writing test tools or &#8222;drivers.&#8220;<\/p>\n<p>[\u2026] The lean software solution is to get the person who can answer the question in the room\u2014either by embedding the customer directly in the team room, or, for a technical question, pairing new programmers with more experienced staff so they dont get stuck.<\/p>\n<p>[\u2026] When I started at one recent client, the team was doing &#8222;book&#8220; Scrum, with two-week iterations and bi-weekly ritual meetings that included retrospective, planning and estimating meetings. These meetings often felt forced and artificial. [\u2026] We dropped iterations and moved the meetings to a just-in-time format. [\u2026] Since we made that switch, two other teams switched to this continuous flow approach; three other teams continue to use iterations. There was no mandate from management or standard to follow. Certain teams simply saw waste and wanted to eliminate it.\u201d<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Matthew Heusser at CIO.com \u2013 How to Advance Lean Software Development (Beyond the &#8218;Toyota Way&#8216;): \u201cLean manufacturing focuses on delivering one part, end-to-end. This is sometimes called one-piece flow. [\u2026] To get to one-piece flow, we&#8217;ll eliminate multi-tasking. [\u2026] Instead of &#8222;pushing&#8220; work to the next step in the chain, we pull it. This means [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[1],"tags":[],"class_list":["post-1557","post","type-post","status-publish","format-standard","hentry","category-weblog"],"share_on_mastodon":{"url":"","error":""},"_links":{"self":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1557","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/comments?post=1557"}],"version-history":[{"count":0,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/posts\/1557\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/media?parent=1557"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/categories?post=1557"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.strehle.de\/tim\/wp-json\/wp\/v2\/tags?post=1557"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}