<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:creativeCommons="http://backend.userland.com/creativeCommonsRssModule" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0" xml:base="http://www.netobjectives.com">
<channel>
 <title>NetObjectives blogs</title>
 <link>http://www.netobjectives.com/blog</link>
 <description />
 <language>en</language>
<media:thumbnail url="http://www.netobjectives.com/files/images/logoNetO_35pct.jpg" /><media:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</media:keywords><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology/Tech News</media:category><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology/Tech News</media:category><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Technology/Tech News</media:category><media:category scheme="http://www.itunes.com/dtds/podcast-1.0.dtd">Business</media:category><itunes:owner><itunes:email>jim.trott@netobjectives.com</itunes:email></itunes:owner><itunes:explicit>no</itunes:explicit><itunes:image href="http://www.netobjectives.com/files/images/logoNetO_35pct.jpg" /><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><itunes:subtitle>Lean-Agile Straight Talk and Net Objectives Thoughts concentrates on helping business and developers together become more effective in software development through the use of lean and agile methods, Scrum, design patterns, and TDD</itunes:subtitle><itunes:summary>Lean-Agile Straight Talk and Net Objectives Thoughts concentrates on helping business and developers together become more effective in software development through the use of lean and agile methods, Scrum, design patterns, and TDD</itunes:summary><itunes:category text="Technology"><itunes:category text="Tech News" /></itunes:category><itunes:category text="Technology"><itunes:category text="Tech News" /></itunes:category><itunes:category text="Technology"><itunes:category text="Tech News" /></itunes:category><itunes:category text="Business" /><geo:lat>47.611021</geo:lat><geo:long>-122.168582</geo:long><image><link>http://www.netobjectives.com/blog</link><url>http://www.netobjectives.com/files/images/logoNetO_50pct.jpg</url><title>Net Objectives Thoughts</title></image><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/NetObjectivesThoughts" type="application/rss+xml" /><feedburner:emailServiceId>NetObjectivesThoughts</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
 <title>Chapter 1: A Developer's Guide to Lean Software Development</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/u0gVvHMLsto/lean-agile-software-development-chapter1</link>
 
 <comments>http://www.netobjectives.com/blogs/lean-agile-software-development-chapter1#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/39">Lean-Agile Straight Talk</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/38">Podcast</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Wed, 28 Oct 2009 14:39:22 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16536 at http://www.netobjectives.com</guid>
<enclosure url="http://www.netobjectives.com/podcasts/last20091028_LASD03_podcasts.mp3" length="17150103" type="audio/mpeg" /><media:content url="http://www.netobjectives.com/podcasts/last20091028_LASD03_podcasts.mp3" fileSize="17150103" type="audio/mpeg" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>  Chapter 1: A Developer&amp;#39;s Guide to Lean Software Development This show continues a chapter by chapter discussion about the new book, Lean-Agile Software Development: Achieving Enterprise Agility, by Alan Shalloway, Guy Beaver, and Jim Trott.  This sh</itunes:subtitle><itunes:summary>  Chapter 1: A Developer&amp;#39;s Guide to Lean Software Development This show continues a chapter by chapter discussion about the new book, Lean-Agile Software Development: Achieving Enterprise Agility, by Alan Shalloway, Guy Beaver, and Jim Trott.  This show focuses on Chapter 1, An Agile Developer&amp;#39;s Guide to Lean Software Development. The key question is, if Lean&amp;#39;s goal is to focus on speed, quality, and low cost, how do you do it? In the past, the approach has been to try to make every step and every person as efficient as possible. That doesn&amp;#39;t work. Instead, you have to look at optimizing the whole process. It is different than efficiency and cost; in fact, lowering cost can increase speed to market and lower quality. Lean says the better approach is to focus on removing delays. Focus on the time between the idea is conceived until the customer can consume it. This involves realizing that product development is a conversation between developers and customers to discover what is required. Cusotmers don&amp;#39;t always know what they need. As much as possible, you want your process to improve the learning and feedback that is taking place so that customers can focus on what they really need. For example, Lean approaches include:Get feedback from the customer quickly.Write tests first. Then you immediately discover when bugs appear. Detect integration issues quickly. The bottomline is that We want to make value flow through the organization quickly and remove anything that causes delay. Finally, practices change depending on the context. How do you know the practices you are doing are good? By comparing them with the foundation lean principles. Teams have both responsibility and guidance for their work. That is the perspective they need.About Lean-Agile Software Development: Achieving Enterprise Agility The motivation of this book is to create a bigger picture what teams transitioning to agile need to do. Yes, teams need to understand the mechanics of the approach to get working, but there is more. Management needs to understand how to help teams work together. Business leadership prioritizing the right things to be working on. And there is a need to ensure technical quality so that development can be done in a sustainable way. We also want to introduce Lean and how it applies to the transition. We don&amp;#39;t believe &amp;quot;scaling up&amp;quot; is a very effective approach. Rather, taking a more holistic view is needed to get success. That is how Lean thinking helps. This is not a book for experienced practitioners but for those who are picking Agile, Scrum, or Lean for software development. We expect you do understand a bit about Agile but not anything about Lean. For more information see the resource page for the book.RecommendationsLean-Agile Software Development: Achieving Enterprise Agility by Alan Shalloway, Guy Beaver, and James R TrottThe Lean-Agile Pocket Guide for Scrum Teams by Alan Shalloway and James R TrottEmergent Design: The Evolutionary Nature of Professional Software Development by Scott BainDesign Patterns Explained by Alan Shalloway and James R Trott For more information, visit us at http://www.netobjectives.com/ Music used in this podcast is by Bill Cushman at http://ghostnotes.blogspot.com and Kevin McLeod: http://www.incompetech.com/. If you need music, I’d encourage you to subscribe to their feeds.</itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description> Chapter 1: A Developer&amp;#39;s Guide to Lean Software Development
This show continues a chapter by chapter discussion about the new book, Lean-Agile Software Development: Achieving Enterprise Agility, by Alan Shalloway, Guy Beaver, and Jim Trott. 
This show focuses on Chapter 1, An Agile Developer&amp;#39;s Guide to Lean Software Development. The key question is, if Lean&amp;#39;s goal is to focus on...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=u0gVvHMLsto:3ClvEEE8YWk:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=u0gVvHMLsto:3ClvEEE8YWk:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=u0gVvHMLsto:3ClvEEE8YWk:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=u0gVvHMLsto:3ClvEEE8YWk:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=u0gVvHMLsto:3ClvEEE8YWk:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=u0gVvHMLsto:3ClvEEE8YWk:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=u0gVvHMLsto:3ClvEEE8YWk:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/u0gVvHMLsto" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/lean-agile-software-development-chapter1</feedburner:origLink></item>
<item>
 <title>The 5 whys of Lean as an answer to the But of Scrum</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/83Mtcw7Vtnk/5-whys-as-the-answer-to-the+but-of-scrum</link>
 
 <comments>http://www.netobjectives.com/blog/5-whys-as-the-answer-to-the+but-of-scrum#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/46">Scrum</category>
 <pubDate>Sun, 25 Oct 2009 11:36:59 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16487 at http://www.netobjectives.com</guid>
<description>In this blog I discuss the need to get to the root cause of why so many teams are not having success with Scrum.  Merely saying management is not removing impediments or labeling it &amp;quot;Scrum but&amp;quot; does not give much indications as to what or where the problems are. The question is &amp;quot;why does this happen and what can we do about it?&amp;quot; I will suggest one of Lean&amp;#39;s problem solving...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=83Mtcw7Vtnk:5NVubSoFnvY:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=83Mtcw7Vtnk:5NVubSoFnvY:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=83Mtcw7Vtnk:5NVubSoFnvY:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=83Mtcw7Vtnk:5NVubSoFnvY:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=83Mtcw7Vtnk:5NVubSoFnvY:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=83Mtcw7Vtnk:5NVubSoFnvY:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=83Mtcw7Vtnk:5NVubSoFnvY:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/83Mtcw7Vtnk" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blog/5-whys-as-the-answer-to-the+but-of-scrum</feedburner:origLink></item>
<item>
 <title>Complex Adaptive Systems Redux</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/ZjYfIUGVoBA/Complex-Adaptive-Systems-Redux</link>
 
 <comments>http://www.netobjectives.com/Complex-Adaptive-Systems-Redux#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/45">Managing</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/46">Scrum</category>
 <pubDate>Sun, 18 Oct 2009 09:00:00 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16353 at http://www.netobjectives.com</guid>
<description>This is a variant of a post I recently made to the Lean-Agile user group.   On the group there has been a lot of talk about the apparent disconnect or conflict between Complex Adaptive Systems  (CAS) and Lean-thinking. Complex adaptive systms are diverse and made up of multiple interconnected elements (and so are a part of network science) and adaptive in that they have the capacity to change and...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ZjYfIUGVoBA:vVfh8TlmTic:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ZjYfIUGVoBA:vVfh8TlmTic:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ZjYfIUGVoBA:vVfh8TlmTic:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ZjYfIUGVoBA:vVfh8TlmTic:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ZjYfIUGVoBA:vVfh8TlmTic:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ZjYfIUGVoBA:vVfh8TlmTic:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=ZjYfIUGVoBA:vVfh8TlmTic:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/ZjYfIUGVoBA" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/Complex-Adaptive-Systems-Redux</feedburner:origLink></item>
<item>
 <title>An Overview of Two New Books</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/03ioavHjNIo/overview-books-pocket-guide-lean-agile-software-development</link>
 
 <comments>http://www.netobjectives.com/blogs/overview-books-pocket-guide-lean-agile-software-development#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/39">Lean-Agile Straight Talk</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/38">Podcast</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/46">Scrum</category>
 <pubDate>Mon, 12 Oct 2009 13:40:06 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">15639 at http://www.netobjectives.com</guid>
<enclosure url="http://www.netobjectives.com/podcasts/last20091013_LASD02_podcasts.mp3" length="24601890" type="audio/mpeg" /><media:content url="http://www.netobjectives.com/podcasts/last20091013_LASD02_podcasts.mp3" fileSize="24601890" type="audio/mpeg" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>  An Overview of Two New Books In this show, we give overviews of two new books by Net Objectives which we think you will find helpful: The Lean-Agile Pocket Guide for Scrum Teams and another is Lean-Agile Software Development: Achieving Enterprise Agilit</itunes:subtitle><itunes:summary>  An Overview of Two New Books In this show, we give overviews of two new books by Net Objectives which we think you will find helpful: The Lean-Agile Pocket Guide for Scrum Teams and another is Lean-Agile Software Development: Achieving Enterprise Agility. We talk through both of these books: their motivation, their contents, why they are useful. In the next podcast, we will talk about the key ideas in each chapter by chapter of Lean-Agile Software Development, the ideas we have found is truly needed in order to be able to achieve enterprise agility. The Lean-Agile Pocket Guide for Scrum Teams The Pocket Guide fills the gap between one of those 10 page (&amp;quot;marketing&amp;quot;) overviews of Scrum and the thousands of pages that have been written on various good Scrum practices. In our work, we found there was a need for a concise statement of what scrum is and a convenient distillation of the best practices. It also includes some techniques not traditionally taught in Scrum but which are very helpful. In 200 pages, it is a great tool to remind you what needs to happen from beginning to end of product development. Lots of checklists and templates to help you think. Some of our clients have found this tool so helpful that they have created a &amp;quot;private label&amp;quot; version of the pocket guide for their own use. It served as a baseline for their own process. And we are willing to do that with others. If you are interested in this for yourself, drop us a note. For more information see the resource page for the pocket guide.Lean-Agile Software Development The motivation of this book is to create a bigger picture what teams transitioning to agile need to do. Yes, teams need to understand the mechanics of the approach to get working, but there is more. Management needs to understand how to help teams work together. Business leadership prioritizing the right things to be working on. And there is a need to ensure technical quality so that development can be done in a sustainable way. We also want to introduce Lean and how it applies to the transition. We don&amp;#39;t believe &amp;quot;scaling up&amp;quot; is a very effective approach. Rather, taking a more holistic view is needed to get success. That is how Lean thinking helps. This is not a book for experienced practitioners but for those who are picking Agile, Scrum, or Lean for software development. We expect you do understand a bit about Agile but not anything about Lean. For more information see the resource page for the book.RecommendationsLean-Agile Software Development: Achieving Enterprise Agility by Alan Shalloway, Guy Beaver, and James R TrottThe Lean-Agile Pocket Guide for Scrum Teams by Alan Shalloway and James R TrottEmergent Design: The Evolutionary Nature of Professional Software Development by Scott BainDesign Patterns Explained by Alan Shalloway and James R Trott For more information, visit us at http://www.netobjectives.com/ </itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description> An Overview of Two New Books
In this show, we give overviews of two new books by Net Objectives which we think you will find helpful: The Lean-Agile Pocket Guide for Scrum Teams and another is Lean-Agile Software Development: Achieving Enterprise Agility. We talk through both of these books: their motivation, their contents, why they are useful. In the next podcast, we will talk about the key...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=03ioavHjNIo:WsnqfcSzGY0:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=03ioavHjNIo:WsnqfcSzGY0:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=03ioavHjNIo:WsnqfcSzGY0:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=03ioavHjNIo:WsnqfcSzGY0:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=03ioavHjNIo:WsnqfcSzGY0:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=03ioavHjNIo:WsnqfcSzGY0:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=03ioavHjNIo:WsnqfcSzGY0:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/03ioavHjNIo" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/overview-books-pocket-guide-lean-agile-software-development</feedburner:origLink></item>
<item>
 <title>Learning to Manage What Matters – Not Always Intuitive</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/pZzprW6n2pI/Learning-to-Manage-What-Matters</link>
 
 <comments>http://www.netobjectives.com/blogs/Learning-to-Manage-What-Matters#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/45">Managing</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Sun, 11 Oct 2009 17:55:53 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16279 at http://www.netobjectives.com</guid>
<description>The Intuitive Solution – Not Necessarily Correct 
If there is one established measure of business success it is return on investment (ROI). ROI is the mantra of business. If you are a business executive and establish a high ROI for a sustained period of time – you are golden. ROI is easy to calculate – it is a measure of your profits (revenue-less expenses) divided by your expenses. ROI can...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=pZzprW6n2pI:I8Rac2cLD1Q:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=pZzprW6n2pI:I8Rac2cLD1Q:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=pZzprW6n2pI:I8Rac2cLD1Q:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=pZzprW6n2pI:I8Rac2cLD1Q:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=pZzprW6n2pI:I8Rac2cLD1Q:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=pZzprW6n2pI:I8Rac2cLD1Q:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=pZzprW6n2pI:I8Rac2cLD1Q:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/pZzprW6n2pI" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/Learning-to-Manage-What-Matters</feedburner:origLink></item>
<item>
 <title>The Difference Between "Inspect and Adapt" and Plan-Do-Check-Act (PDCA)</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/eM-6LLrjrA4/difference-btween-inspect-and-adapt-and-pdcs</link>
 
 <comments>http://www.netobjectives.com/blogs/difference-btween-inspect-and-adapt-and-pdcs#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/46">Scrum</category>
 <pubDate>Sat, 10 Oct 2009 08:42:14 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16251 at http://www.netobjectives.com</guid>
<enclosure url="http://scrumtraininginstitute.com/home/stream_download/scrumpapers" length="2840981" type="application/pdf" /><media:content url="http://scrumtraininginstitute.com/home/stream_download/scrumpapers" fileSize="2840981" type="application/pdf" /><itunes:explicit>no</itunes:explicit><itunes:subtitle> In our book, Lean-Agile Software Development: Achieving Enterprise and Team Agility, we mention that the &amp;quot;inspect and adapt&amp;quot; is not the same thing as Plan-Do-Check-Act. Yes, they sound the same, but they are manifestations of different causalit</itunes:subtitle><itunes:summary> In our book, Lean-Agile Software Development: Achieving Enterprise and Team Agility, we mention that the &amp;quot;inspect and adapt&amp;quot; is not the same thing as Plan-Do-Check-Act. Yes, they sound the same, but they are manifestations of different causality models. To fully understand the differences in inspect and adapt and PDCA, we must look at these causality models (which we will do shortly). Scrum portends that because we are working on non-deterministic systems, our own process should be a controlled black box. See The Scrum Papers, pg 58. We disagree. A simple example of this is driving a car. I think we&amp;#39;d all agree that driving is a non-deterministic system. When you leave your home for work you do not know exactly what will happen – who will cut you off and how you&amp;#39;ll have to drive defensively, or perhaps who you will cut off in an attempt to make up some time. Yet, most of the time, you get to where you wanted to get to in about the time you expected to get there. The &amp;quot;process&amp;quot; you use – keeping a certain distance between the car in front of you and your car (except, of course, when you are really trying to speed up the idiot), driving on the right side of the road when in the US on two-way streets, pressing the gas to accelerate, pressing the brake to slow down, threatening the kids if they don&amp;#39;t shut up, … While simply knowing the rules doesn&amp;#39;t mean you know how to drive, knowing the rules helps you drive better. In an earlier blog (Types of Processes by Don Reinertsen), I discussed how the degree of visibility of your process is a separate issue from the level of randomness of its output. A third, separate, issue is how much feedback you need to control things. While we agree that software development is a non-deterministic process, we do not believe that there is no causality of the actions involved. We also believe that it is important to create visibility into the process (what we call transparency) and not just visibility into the results (I&amp;#39;ve stated this several times on user groups but will write an upcoming blog to focus on this shortly). This is a significant difference in flow based systems (e.g., Kanban) and Scrum. At a cursory level, the project boards for both flow based systems and Scrum look the same. One can see work entering the system, different stages in which the work is in and when the work is done. We call this visibility – that is, we have visibility into the results of the team. Incredibly important, but insufficient in our minds. As important is the answer to the question- how does the work flow from one end of the board to the other? Is it just up to individual member&amp;#39;s decisions on when to work on things or is there a visible set of decisions at work? While no complete definition of Scrum exists, the aforementioned Scrum papers as well as many blogs and user-group comments from CSTs (certified scrum trainers, presumably the highest authorities on what the Scrum Alliance&amp;#39;s stance on Scrum is) continuously state the supposition that a defined process is not a good idea (if it were even possible). In other words, most Scrum boards will show you stories waiting to be worked on, those in process (including varying states) and those completed but having a defined set of rules for how things go from one column to the other is not a part of Scrum. It is just left to the team members&amp;#39; judgment. Teams are supposed to pay attention to the effectiveness of their actions and adapt accordingly. You can, of course, add your own rules. Good thing to do in our mind if you are doing Scrum – but then you have a variant of it (we call ours Scrum#). PDCA is a bit different from &amp;quot;inspect and adapt&amp;quot; in that it requires the team to consider how things are actually working. In other words, we don&amp;#39;t want to just inspect and adapt, we want to understand, at least a little, about the causality of things. For example, agile teams often experience a backlog of te</itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description>In our book, Lean-Agile Software Development: Achieving Enterprise and Team Agility, we mention that the &amp;quot;inspect and adapt&amp;quot; is not the same thing as Plan-Do-Check-Act.  Yes, they sound the same, but they are manifestations of different causality models.  To fully understand the differences in inspect and adapt and PDCA, we must look at these causality models (which we will do shortly)....&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=eM-6LLrjrA4:w7YZ9lkcs2g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=eM-6LLrjrA4:w7YZ9lkcs2g:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=eM-6LLrjrA4:w7YZ9lkcs2g:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=eM-6LLrjrA4:w7YZ9lkcs2g:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=eM-6LLrjrA4:w7YZ9lkcs2g:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=eM-6LLrjrA4:w7YZ9lkcs2g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=eM-6LLrjrA4:w7YZ9lkcs2g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/eM-6LLrjrA4" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/difference-btween-inspect-and-adapt-and-pdcs</feedburner:origLink></item>
<item>
 <title>Types of Processes - by Don Reinertsen</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/FL-ZSCGL4OM/Types-of-Processes</link>
 
 <comments>http://www.netobjectives.com/blogs/Types-of-Processes#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <pubDate>Tue, 06 Oct 2009 05:49:53 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16168 at http://www.netobjectives.com</guid>
<enclosure url="http://www.netobjectives.com/files/Lean-AgileReleasePlanning.pdf" length="1285443" type="application/pdf" /><media:content url="http://www.netobjectives.com/files/Lean-AgileReleasePlanning.pdf" fileSize="1285443" type="application/pdf" /><itunes:explicit>no</itunes:explicit><itunes:subtitle> In May 2009, there were some discussions on the Kanban Dev group about types of processes.  The dialog that resulted is an important part of the Lean thought process and I thought it&amp;#39;d be useful to reproduce that here.  The discussion on the quality </itunes:subtitle><itunes:summary> In May 2009, there were some discussions on the Kanban Dev group about types of processes.  The dialog that resulted is an important part of the Lean thought process and I thought it&amp;#39;d be useful to reproduce that here.  The discussion on the quality and pressure thread pressed me into thinking deeper on what I consider an important issue - can effective software development be defined. I had troubles formulating answers to people&amp;#39;s questions - but knew there was more there. I decided to ask Don Reinertsen about this. Don is the author of Managing the Design Factory (an absolute must read for any software developer in my mind) and The Principles of Product Development Flow: Second Generation Lean Product Development (an astounding book that contains 175 principles of product development). Note, even though this book is amazing, I really recommend reading &amp;quot;Design Factory&amp;quot; first if you haven&amp;#39;t read it yet. Anyway, here&amp;#39;s how Don responded (used by permission) (note - this is a long post - but I assure you it is well worth the time to read it):   Question: In &amp;quot;The Scrum Papers&amp;quot;, Jeff Sutherland and Ken Schwaber say &amp;quot;In this paper we introduce a development process, Scrum, that treats major portions of systems development as a controlled black box.&amp;quot; The basis for this is &amp;quot;Concepts from industrial process control are applied to the field of systems development in this paper. Industrial process control defines processes as either `theoretical&amp;#39; (fully defined) or `empirical&amp;#39; (black box). When a black box process is treated as a fully defined process, unpredictable results occur.&amp;quot; I had always interpreted this to mean that you need feedback in order to control a software development process. I agree with this. However, it actually says the process is a black box process – meaning one learns about it through observation.   We believe there are two different orthogonal issues. The first is the one Jeff and Ken mention – defined or empirical. The second, distinct issue is whether a process is predictable or requires feedback to control. These are not the same thing. Defined or empirical relates to whether there is a model underneath the system that one can learn. Predictable Vs Requiring Feedback means can you predict the outcome of the system. …..   Answer:   Hi Alan, By coincidence I have some experience with very advanced industrial process control systems, having spent many years operating nuclear reactors in the Navy. In my experience, such systems do not tidily divide into the categories of fully-determined and empirical. Nevertheless, it is not surprising that software gurus, who have &amp;quot;either/or&amp;quot; hard-coded into heir DNA, would perceive them in a binary way.   Let&amp;#39;s start by cleaning up the terminology. We can view the output of a process as deterministic or stochastic. In a deterministic process the outputs are 100 percent determined by the inputs. In a stochastic process the output is a random variable—it has different values that occur with different probabilities.   Fully-determined systems do not exist, except in academia and thought experiments. All industrial process control systems have stochastic outputs. They are partially determined. We use imperfect models to determine how to vary process inputs to control certain important measures of output within a useful control range. We embed these models in control strategies; for example, we might use a PID controller to weight the current level of parameters, their time derivatives, and their integrals to generate a control signal. We optimize our control strategy to balance the cost of control with the benefits of control. The tightness of the control band is simply an economic choice. We do not control for the sake of control. We do not believe that the lowest possible variance is the most desirable operating point.   It is useful to make a distinction between whether a process is fully-determined </itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description>In May 2009, there were some discussions on the Kanban Dev group about types of processes.  The dialog that resulted is an important part of the Lean thought process and I thought it&amp;#39;d be useful to reproduce that here.  The discussion on the quality and pressure thread pressed me into thinking deeper on what I consider an important issue - can effective software development be defined. I had...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=FL-ZSCGL4OM:IPcBmlNdHE8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=FL-ZSCGL4OM:IPcBmlNdHE8:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=FL-ZSCGL4OM:IPcBmlNdHE8:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=FL-ZSCGL4OM:IPcBmlNdHE8:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=FL-ZSCGL4OM:IPcBmlNdHE8:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=FL-ZSCGL4OM:IPcBmlNdHE8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=FL-ZSCGL4OM:IPcBmlNdHE8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/FL-ZSCGL4OM" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/Types-of-Processes</feedburner:origLink></item>
<item>
 <title>Pragmatic Lean</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/qDecVcW8bgY/Pragmatic-Lean</link>
 
 <comments>http://www.netobjectives.com/blogs/Pragmatic-Lean#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Tue, 06 Oct 2009 04:19:50 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16167 at http://www.netobjectives.com</guid>
<description>I am writing this blog to create a better context for my current blog series on Lean. As CEO of a company that helps other companies transition to becoming more effective in their software development efforts I am mostly interested in helping  companies achieve enterprise agility. Enterprise agility is the ability to be agile at the enterprise level.  That is, when a quick response is needed, the...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qDecVcW8bgY:ifQhTWFMXC4:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qDecVcW8bgY:ifQhTWFMXC4:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qDecVcW8bgY:ifQhTWFMXC4:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qDecVcW8bgY:ifQhTWFMXC4:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qDecVcW8bgY:ifQhTWFMXC4:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qDecVcW8bgY:ifQhTWFMXC4:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=qDecVcW8bgY:ifQhTWFMXC4:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/qDecVcW8bgY" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/Pragmatic-Lean</feedburner:origLink></item>
<item>
 <title>An Overview of Lean Software Development</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/RiLBcX-NxXw/an-overview-of-lean-software-development</link>
 
 <comments>http://www.netobjectives.com/blogs/an-overview-of-lean-software-development#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Sun, 04 Oct 2009 04:36:16 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16137 at http://www.netobjectives.com</guid>
<description>In starting out this series of blogs on Lean I intended to go through the sequence I feel is best for people to understand what Lean Software Development is.  However, after having started this I realized a quick overview - to create a road map would be best.  Some of this re-thinking is also because I believe I can turn this series into a short book I believe I&amp;#39;ll call Lean Software...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=RiLBcX-NxXw:CMtxcyHJDmc:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=RiLBcX-NxXw:CMtxcyHJDmc:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=RiLBcX-NxXw:CMtxcyHJDmc:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=RiLBcX-NxXw:CMtxcyHJDmc:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=RiLBcX-NxXw:CMtxcyHJDmc:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=RiLBcX-NxXw:CMtxcyHJDmc:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=RiLBcX-NxXw:CMtxcyHJDmc:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/RiLBcX-NxXw" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/an-overview-of-lean-software-development</feedburner:origLink></item>
<item>
 <title>The Dangers of Complex Adaptive Systems</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/J9KuU-KGfUg/the-dangers-of-complex-adaptive-systems</link>
 
 <comments>http://www.netobjectives.com/blogs/the-dangers-of-complex-adaptive-systems#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Sat, 03 Oct 2009 09:10:48 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16125 at http://www.netobjectives.com</guid>
<description>There has been some talk about CAS systems in software.  My own experience (albeit limited and I am wanting to learn more) is that CAS is mostly useful at the team level.  I believe there are some dangers at higher levels in most organizations.  Furthermore, I tend to view CAS as a good explanation of things - but not necessarily a good predictive model. In other words, can you use CAS as a model...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=J9KuU-KGfUg:60S5Ld7ArSI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=J9KuU-KGfUg:60S5Ld7ArSI:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=J9KuU-KGfUg:60S5Ld7ArSI:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=J9KuU-KGfUg:60S5Ld7ArSI:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=J9KuU-KGfUg:60S5Ld7ArSI:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=J9KuU-KGfUg:60S5Ld7ArSI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=J9KuU-KGfUg:60S5Ld7ArSI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/J9KuU-KGfUg" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/the-dangers-of-complex-adaptive-systems</feedburner:origLink></item>
<item>
 <title>The Foundations of Lean (and Kanban)</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/JadZvXJzEP0/foundation-of-lean</link>
 
 <comments>http://www.netobjectives.com/blogs/foundation-of-lean#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Fri, 02 Oct 2009 13:54:03 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16114 at http://www.netobjectives.com</guid>
<description>I hadn&amp;#39;t meant to imply that the page or two on the essence of Lean of my earlier post covered the scope of Lean.  In this blog, I&amp;#39;ll talk about two foundations of Lean - systems thinking and respecting people.  This will open the door for follow up blogs on Lean-Management and Lean-Learning (continuous process improvement).Systemic Thinking and Respecting People.
I like George Box&amp;#39;s...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=JadZvXJzEP0:MKe3QIczbkM:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=JadZvXJzEP0:MKe3QIczbkM:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=JadZvXJzEP0:MKe3QIczbkM:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=JadZvXJzEP0:MKe3QIczbkM:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=JadZvXJzEP0:MKe3QIczbkM:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=JadZvXJzEP0:MKe3QIczbkM:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=JadZvXJzEP0:MKe3QIczbkM:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/JadZvXJzEP0" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/foundation-of-lean</feedburner:origLink></item>
<item>
 <title>The Essence of Lean (and Kanban)</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/jIs2keC82oY/Essence-of-lean</link>
 
 <comments>http://www.netobjectives.com/blogs/Essence-of-lean#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Wed, 30 Sep 2009 14:21:06 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">16031 at http://www.netobjectives.com</guid>
<description>There is a lot of buzz about Kanban these days.  There seems to be an equal confusion about what it is. Since Kanban for Software Engineering is really Lean applied to software, I am going to make the two synonymous for the purposes of this blog.  I am going to refer to Lean throughout this article. I provide the alternative title because I think the essence of Kanban is the same as the essence...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=jIs2keC82oY:BLzOu9sEGqw:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=jIs2keC82oY:BLzOu9sEGqw:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=jIs2keC82oY:BLzOu9sEGqw:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=jIs2keC82oY:BLzOu9sEGqw:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=jIs2keC82oY:BLzOu9sEGqw:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=jIs2keC82oY:BLzOu9sEGqw:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=jIs2keC82oY:BLzOu9sEGqw:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/jIs2keC82oY" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/Essence-of-lean</feedburner:origLink></item>
<item>
 <title>Comparing Scrum to Lean - Not Quite Apples to Oranges</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/ddQt6TPrzjc/comparing-scrum-to-lean-not-quite-apples-to-oranges</link>
 
 <comments>http://www.netobjectives.com/blogs/comparing-scrum-to-lean-not-quite-apples-to-oranges#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/46">Scrum</category>
 <pubDate>Tue, 29 Sep 2009 00:58:58 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">15981 at http://www.netobjectives.com</guid>
<description>There have been several posts from those in the Scrum community (Ron Jeffries, Tobias Meyer, to name two) that say it is folly to compare Scrum and Lean/Kanban.  The supposition is that they are different tools and therefore you can’t say one is better than another. Apples to oranges they say.  I don’t agree.   
The odd theory is that they are different tools in your tool box. I say “odd theory”...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ddQt6TPrzjc:CxgDzGaWimQ:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ddQt6TPrzjc:CxgDzGaWimQ:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ddQt6TPrzjc:CxgDzGaWimQ:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ddQt6TPrzjc:CxgDzGaWimQ:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ddQt6TPrzjc:CxgDzGaWimQ:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=ddQt6TPrzjc:CxgDzGaWimQ:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=ddQt6TPrzjc:CxgDzGaWimQ:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/ddQt6TPrzjc" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/comparing-scrum-to-lean-not-quite-apples-to-oranges</feedburner:origLink></item>
<item>
 <title>A New Series</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/LErNE_FS96g/new-series</link>
 
 <comments>http://www.netobjectives.com/blogs/new-series#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/39">Lean-Agile Straight Talk</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/38">Podcast</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/45">Managing</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/46">Scrum</category>
 <pubDate>Mon, 28 Sep 2009 16:04:39 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">15616 at http://www.netobjectives.com</guid>
<enclosure url="http://www.netobjectives.com/podcasts/last20090929_LASD01_podcasts.mp3" length="22580611" type="audio/mpeg" /><media:content url="http://www.netobjectives.com/podcasts/last20090929_LASD01_podcasts.mp3" fileSize="22580611" type="audio/mpeg" /><itunes:explicit>no</itunes:explicit><itunes:subtitle> A New Series This podcast kicks off a new series for Lean Agile Straight Talk. We have been busy finishing several books focused on Lean-Agile. One is called the Lean-Agile Pocket Guide for Scrum Teams and another is Lean-Agile Software Development: Achi</itunes:subtitle><itunes:summary> A New Series This podcast kicks off a new series for Lean Agile Straight Talk. We have been busy finishing several books focused on Lean-Agile. One is called the Lean-Agile Pocket Guide for Scrum Teams and another is Lean-Agile Software Development: Achieving Enterprise Agility. We are proud of both of these books and wanted to introduce them to you. In this show, Alan Shalloway and I talk about the motivations behind these books, what is going in in the world of Lean and Agile software development and why they are needed. The next show will give a rundown of the pocket guide. After that, we will talk through each of the chapters in Lean-Agile Software Development. Each of these chapters has good, core concepts that we want you to know and this approach gives us a game plan for covering all of them. Each of the books Net Objectives offers aims to address the question, &amp;quot;What do people need to know to succed in their role to do product development?&amp;quot; In a nutshell, we describe Lean-Agile with the phrase, Make-Value-Flow-Sustainably. Make. How do developers create software at the team-level. In the past, &amp;quot;making&amp;quot; was where the challenges were. Value. What does the business need? How do we get them to drive what really needs to get done? Flow. How do you get what multiple teams create to flow through the organization. Learning to work together, coordinating work. Sustainably. How do keep writing code so that it is always of sufficient quality? So that we do not keep incurring technical debt. And ow do keep the organization growing in a healty way so that it can continue to do the work. Even if you find a technique, such as Scrum, that works well at a team-level, it does not always work in every context. And, we have learned that trying to &amp;quot;scale&amp;quot; Scrum to the enterprise is not the correct approach to achieve enterprise agility. Understanding the principles helps you know what to do when confronting situations you have not yet encountered. And that leads to proficiency in this field. Recommendations Lean-Agile Software Development: Achieving Enterprise Agility by Alan Shalloway, Guy Beaver, and James R Trott The Lean-Agile Pocket Guide for Scrum Teams by Alan Shalloway and James R Trott Emergent Design: The Evolutionary Nature of Professional Software Development by Scott Bain Design Patterns Explained by Alan Shalloway and James R Trott For more information, contact info@netobjectives.com or visit us at http://www.netobjectives.com/ &amp;nbsp; &amp;nbsp; </itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description>A New Series 

This podcast kicks off a new series for Lean Agile Straight Talk. We have been busy finishing several books focused on Lean-Agile. One is called the Lean-Agile Pocket Guide for Scrum Teams and another is Lean-Agile Software Development: Achieving Enterprise Agility. We are proud of both of these books and wanted to introduce them to you. In this show, Alan Shalloway and I talk...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=LErNE_FS96g:fJkqzBiUhys:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=LErNE_FS96g:fJkqzBiUhys:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=LErNE_FS96g:fJkqzBiUhys:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=LErNE_FS96g:fJkqzBiUhys:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=LErNE_FS96g:fJkqzBiUhys:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=LErNE_FS96g:fJkqzBiUhys:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=LErNE_FS96g:fJkqzBiUhys:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/LErNE_FS96g" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/new-series</feedburner:origLink></item>
<item>
 <title>Mid-Management in the Lean-Agile Enterprise: Competencies Required</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/cIbCt1PdU9M/mid-management-lean-agile-enterprise</link>
 
 <comments>http://www.netobjectives.com/blogs/mid-management-lean-agile-enterprise#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/45">Managing</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Fri, 18 Sep 2009 15:54:04 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">15820 at http://www.netobjectives.com</guid>
<enclosure url="http://www.netobjectives.com/files/VisualControlsEnterpriseTeams.pdf" length="1706537" type="application/pdf" /><media:content url="http://www.netobjectives.com/files/VisualControlsEnterpriseTeams.pdf" fileSize="1706537" type="application/pdf" /><itunes:explicit>no</itunes:explicit><itunes:subtitle> There are many catch-phrases and metaphors used in the Agile space to try to define the role of management [1]. Examples include &amp;quot;servant-leader&amp;quot;, &amp;quot;Chickens not Pigs&amp;quot;, facilitator, motivator, etc. After all, the notion of &amp;quot;self-o</itunes:subtitle><itunes:summary> There are many catch-phrases and metaphors used in the Agile space to try to define the role of management [1]. Examples include &amp;quot;servant-leader&amp;quot;, &amp;quot;Chickens not Pigs&amp;quot;, facilitator, motivator, etc. After all, the notion of &amp;quot;self-organization&amp;quot; can easily be construed to mean no management required. Many Agile practitioners handle this dilemma by focusing on traits of good leadership, and implying that instead of focusing on competencies based on principles and practices, the successful Agile manager only needs to focus on aggregating the traits of a good leader, such as coaching and motivating teams, supporting (not directing) teams, leading (not assigning). While these traits are all valuable, they are not drivers for the successful Lean-Agile manager. Instead these traits are observable outcomes of management properly applying principles and practices to a complex organization. Instead of seeing management as the problem, I&amp;#39;ve found that certain competencies must be mastered and practiced by managers in order for Agility to take hold and grow in a Lean-Agile enterprise. This blog helps define competencies that must be mastered before the traits of good Agile management begin to emerge. By mid-management, I am referring to the layer of managers from Project Manager to Senior Manager to Director. So what are the competencies that managers should learn in order to transition to an effective Lean-Agile project manager? I think the foundation was laid in David Anderson&amp;#39;s excellent book &amp;quot;Agile Management for Software Engineering: Applying the Theory of Constraints for Business Results [2].&amp;quot; This book makes the case for competencies based on understanding established fields of knowledge including Theory of Constraints and Lean Principles and Practices such as (Lead Time, Focus on Quality, Just-in-Time, Identifying Flow, and more). By studying and understanding these competencies, a clearer view of the drivers and focus areas begins to emerge that can allow management to avoid confusion and mistakes, and actually drive the successful transition of a software engineering enterprise. Here is a short list of the key focus areas that Lean-Agile Managers should embrace and master, but if I had to condense this into a sound bite, it would be this:   The Lean-Agile Management competencies are about understanding the relationships between queues and workflows, and learning how to manage them.Competencies for Lean-Agile Managers Value Stream Transparency Limit work to capacity Minimize WIP Eliminate Waste Focus on Quality I&amp;#39;ll take them one at a time and break down some specific areas of responsibility that managers must embrace and be accountable for in order to lead a Lean-Agile enterprise. Value Stream Transparency This competency is critical for any of the other competencies to be understood. By value stream, I mean highest level flow of identified business and operational needs (pulled by business value and client value). This &amp;quot;flow&amp;quot; is really the end-to-end transformation of discovered business need to solution delivered. The Poppendieck&amp;#39;s refer to this as &amp;quot;concept to cash [3].&amp;quot; Management is accountable for identifying this value stream, and making it transparent to the entire organization. This is best accomplished by Visual Controls that bring transparency to flow, pull, work-in-process, bottlenecks, and waste. For more details, see the chapter on Visual Controls [4] in our upcoming book, Lean-Agile Software Development: Achieving Enterprise Agility [5]. Limit Work to Capacity Lean&amp;#39;s view is that the most important resource is the creativity and problem solving capacity in our people. To create an environment that effectively utilizes this resource, we need to respect the fundamental laws of capacity utilization, which reveal that our ability to move through a discovery process is optimized if we don&amp;#39;t overload our resources with work. In terms of the</itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description>There are many catch-phrases and metaphors used in the Agile space to try to define the role of management [1]. Examples include &amp;quot;servant-leader&amp;quot;, &amp;quot;Chickens not Pigs&amp;quot;, facilitator, motivator, etc. After all, the notion of &amp;quot;self-organization&amp;quot; can easily be construed to mean no management required. Many Agile practitioners handle this dilemma by focusing on traits of...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=cIbCt1PdU9M:1hNJTdIeU2g:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=cIbCt1PdU9M:1hNJTdIeU2g:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=cIbCt1PdU9M:1hNJTdIeU2g:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=cIbCt1PdU9M:1hNJTdIeU2g:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=cIbCt1PdU9M:1hNJTdIeU2g:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=cIbCt1PdU9M:1hNJTdIeU2g:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=cIbCt1PdU9M:1hNJTdIeU2g:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/cIbCt1PdU9M" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/mid-management-lean-agile-enterprise</feedburner:origLink></item>
<item>
 <title>Creativity, Art, Software and Process</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/9NJfc3sQ3do/creativity-art-software-and-process</link>
 
 <comments>http://www.netobjectives.com/blogs/creativity-art-software-and-process#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/37">Design Patterns</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Mon, 07 Sep 2009 08:37:17 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">15559 at http://www.netobjectives.com</guid>
<description>I was recently surprised when someone said I had said software is not creative.  I was surprised because I can’t imagine myself ever saying that.  On reflection, I realized I had said software is not like art.  But I meant that it is not like art because art does not have a particular customer nor does it need to follow particular rules.  Art speaks to whoever it speaks to.  It comes from the...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=9NJfc3sQ3do:OaeZYvidG2s:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=9NJfc3sQ3do:OaeZYvidG2s:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=9NJfc3sQ3do:OaeZYvidG2s:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=9NJfc3sQ3do:OaeZYvidG2s:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=9NJfc3sQ3do:OaeZYvidG2s:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=9NJfc3sQ3do:OaeZYvidG2s:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=9NJfc3sQ3do:OaeZYvidG2s:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/9NJfc3sQ3do" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/creativity-art-software-and-process</feedburner:origLink></item>
<item>
 <title>Lean is more than a set of tools</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/nMgk6UVdGD0/Lean-Is-Not-Just-A-Set-Of-Tools</link>
 
 <comments>http://www.netobjectives.com/blogs/Lean-Is-Not-Just-A-Set-Of-Tools#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Mon, 31 Aug 2009 18:11:19 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">15451 at http://www.netobjectives.com</guid>
<description>I hear a lot of people talking about Lean as if it were just a set of tools.  I also hear a lot of people saying it doesn&amp;#39;t make any sense to try to contrast Scrum and Lean.   If you believe the first, you will likely believe the second. This blog is an attempt to show how Lean has a set of tools, but isn&amp;#39;t just a set of tools.  By tools, in our case, I mean the practices with which to...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=nMgk6UVdGD0:c6g0n-BtM8M:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=nMgk6UVdGD0:c6g0n-BtM8M:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=nMgk6UVdGD0:c6g0n-BtM8M:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=nMgk6UVdGD0:c6g0n-BtM8M:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=nMgk6UVdGD0:c6g0n-BtM8M:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=nMgk6UVdGD0:c6g0n-BtM8M:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=nMgk6UVdGD0:c6g0n-BtM8M:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/nMgk6UVdGD0" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/Lean-Is-Not-Just-A-Set-Of-Tools</feedburner:origLink></item>
<item>
 <title>Software Quality and Daily Life</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/qEOL-P3COsI/software-quality-daily-life</link>
 
 <comments>http://www.netobjectives.com/blogs/software-quality-daily-life#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/199">Coaching</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/37">Design Patterns</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/40">Testing</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Tue, 18 Aug 2009 10:58:29 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">14987 at http://www.netobjectives.com</guid>
<description>I recently had to install a driver for a network printer in my home. This is, I would say, a pretty commonplace thing to do in modern life. 
I don&amp;#39;t want to suggest that what happened was limited to a particular vendor, so we&amp;#39;ll leave the company name out… however, it is one of the most prominent and successful printer companies in the world. Not some little podunk knock-off, in other...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qEOL-P3COsI:jqP_-8xQep8:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qEOL-P3COsI:jqP_-8xQep8:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qEOL-P3COsI:jqP_-8xQep8:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qEOL-P3COsI:jqP_-8xQep8:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qEOL-P3COsI:jqP_-8xQep8:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=qEOL-P3COsI:jqP_-8xQep8:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=qEOL-P3COsI:jqP_-8xQep8:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/qEOL-P3COsI" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/software-quality-daily-life</feedburner:origLink></item>
<item>
 <title>The Case for One-Piece Flow (Part 3/3)</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/uoVFcvq3c80/case-one-piece-flow-part-3</link>
 
 <comments>http://www.netobjectives.com/blogs/case-one-piece-flow-part-3#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/44">Lean</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/45">Managing</category>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Wed, 29 Jul 2009 14:58:15 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">14647 at http://www.netobjectives.com</guid>
<enclosure url="http://www.netobjectives.com/files/SeeingLean.pdf" length="565026" type="application/pdf" /><media:content url="http://www.netobjectives.com/files/SeeingLean.pdf" fileSize="565026" type="application/pdf" /><itunes:explicit>no</itunes:explicit><itunes:subtitle>Part 3: Managing Enterprise Agility In parts 1 and 2 of this series, we discussed how the principles of queuing theory and capacity utilization suggest that keeping people busy actually works against minimizing cycle time. When applied to software develop</itunes:subtitle><itunes:summary>Part 3: Managing Enterprise Agility In parts 1 and 2 of this series, we discussed how the principles of queuing theory and capacity utilization suggest that keeping people busy actually works against minimizing cycle time. When applied to software development organizations, we begin to see how having too many projects underway unintentionally hides wasteful activity. In part 3, we pull together the concepts and discuss why organizations that focus on completing smaller, high value capabilities can realize much greater returns on technology investments. During dinner at a recent multi-family vacation, I was asked what I did as a consultant. My reply was that I teach large organizations new ways to think about getting work done. I could see that the audience wasn&amp;#39;t going to get much out of the lingo that I deal with everyday, so I boiled it down to something that everyone at the table could grasp. Here&amp;#39;s how I pitched it: Say you start your day with a &amp;quot;To Do&amp;quot; list that contains 10 tasks. Each task happens to take about an hour to complete. If you work in multi-task mode, and open each task, the average time to complete each task will be 10 hours. If you work an 8 hour day, you&amp;#39;ll go home with no tasks completed. Now suppose each task was a request by 10 different customers/clients. If instead of juggling all 10 tasks at once you decide instead to prioritize the tasks, and focus on completing them in sequence, you have a chance of pleasing 8 customers/clients. If your sequence matched the importance of the customer (based on whatever business priority you decide), then you &amp;quot;please&amp;quot; customers based on value. Now when we look at average wait time (cycle time) it comes down to 5 hours in this case, as customer 1 saw 1 hour, customer 2 saw 2 hours, etc., which averages to 5 hours. By simply working in priority and sequencing the work, our average cycle time has been cut in half. (Technically, the average cycle time in case 2 converges to 1 hour, but in this special case I assumed they all hit the start queue at the same time.) If we extend this model to business stakeholders making project requests, we can see how minimizing work-in-process (WIP) actually allows for a more Agile business model, as higher value work can get completed on its own instead of bundling up lots of requests into large projects, which hides prioritization and slows down the delivery stream of completed work. For a deeper discussion, see Chapter 14 &amp;quot;Seeing Lean&amp;quot; in our latest book &amp;quot;Lean-Agile Software Development: Achieving Enterprise Agility.&amp;quot; I was once invited to sit in on a mid-project review for a large conversion project referred to here as &amp;quot;Big Conversion Release.&amp;quot; It had been underway for 6 months (along with 3 other large release projects that were underway and being worked on by the same team). This conversion project appeared in a Release Plan Timeline that looked something like this: The team of 30 developers, testers, and analysts were spread across 3 smaller quarterly releases as well as the &amp;quot;Big Conversion Release&amp;quot;. The review session was for the team to show the Big Conversion Release to the business team. The meeting started with the dev team proudly describing a new UI as a technological breakthrough that allows them to store and retrieve screen information in a database. The meeting went downhill from there… The team reviewed a parity conversion of an existing app over to the new technology. It was clear that this was the first time that the business team and the testers had seen the screens. Over 100 &amp;quot;feedback items&amp;quot; were created, and most were challenged by the team as &amp;quot;new requirements&amp;quot; and &amp;quot;complex&amp;quot;. Finally the IT manager piped up with &amp;quot;We&amp;#39;ll capture these, estimate how big they are, and decide if we can do them &amp;quot;. By the end of the session, the business reviewers and delivery team members were visibly in conflict, and a p</itunes:summary><itunes:keywords>lean,agile,scrum,design,patterns,patterns,tdd,test,driven,development,shalloway,trott,netobjectives,net,objectives,poppendieck</itunes:keywords><description>Part 3: Managing Enterprise Agility
In parts 1 and 2 of this series, we discussed how the principles of queuing theory and capacity utilization suggest that keeping people busy actually works against minimizing cycle time. When applied to software development organizations, we begin to see how having too many projects underway unintentionally hides wasteful activity. In part 3, we pull together...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=uoVFcvq3c80:FEumz5dGGRI:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=uoVFcvq3c80:FEumz5dGGRI:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=uoVFcvq3c80:FEumz5dGGRI:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=uoVFcvq3c80:FEumz5dGGRI:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=uoVFcvq3c80:FEumz5dGGRI:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=uoVFcvq3c80:FEumz5dGGRI:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=uoVFcvq3c80:FEumz5dGGRI:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/uoVFcvq3c80" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/case-one-piece-flow-part-3</feedburner:origLink></item>
<item>
 <title>Is Part of the Agile Community Acting Like the Waterfall Community of Old?</title>
 <link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/hBaJcBIPfa4/Is-Part-of-the-Agile-Community-Acting-Like-Waterfall-Community-of-Old</link>
 
 <comments>http://www.netobjectives.com/blogs/Is-Part-of-the-Agile-Community-Acting-Like-Waterfall-Community-of-Old#comments</comments>
 <category domain="http://www.netobjectives.com/taxonomy/term/43">Lean-Agile</category>
 <pubDate>Wed, 15 Jul 2009 09:04:24 -0600</pubDate>
 <dc:creator>jim.trott@netobjectives.com</dc:creator>
 <guid isPermaLink="false">14313 at http://www.netobjectives.com</guid>
<description>When I started writing this blog I had one answer to the question it presents, but after having  written it, I have another.  I will say that my initial answer was &amp;quot;yes, it feels similar.&amp;quot;  You&amp;#39;ll have to wait until the end to get my current answer.
I have spent the last few months trying to explain why Kanban works to people who have mostly done Scrum. I&amp;#39;ll admit that I have...&lt;br/&gt;
&lt;br/&gt;
[[ This is a content summary only. Visit my website for full links, other content, and more! ]]&lt;div class="feedflare"&gt;
&lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=hBaJcBIPfa4:YYVHztR-8TU:yIl2AUoC8zA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=yIl2AUoC8zA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=hBaJcBIPfa4:YYVHztR-8TU:63t7Ie-LG7Y"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=63t7Ie-LG7Y" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=hBaJcBIPfa4:YYVHztR-8TU:dnMXMwOfBR0"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=dnMXMwOfBR0" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=hBaJcBIPfa4:YYVHztR-8TU:7Q72WNTAKBA"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=7Q72WNTAKBA" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=hBaJcBIPfa4:YYVHztR-8TU:YwkR-u9nhCs"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?d=YwkR-u9nhCs" border="0"&gt;&lt;/img&gt;&lt;/a&gt; &lt;a href="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?a=hBaJcBIPfa4:YYVHztR-8TU:JEwB19i1-c4"&gt;&lt;img src="http://feeds.feedburner.com/~ff/NetObjectivesThoughts?i=hBaJcBIPfa4:YYVHztR-8TU:JEwB19i1-c4" border="0"&gt;&lt;/img&gt;&lt;/a&gt;
&lt;/div&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/hBaJcBIPfa4" height="1" width="1"/&gt;</description><creativeCommons:license>http://creativecommons.org/licenses/by-nc-nd/2.0/</creativeCommons:license><feedburner:origLink>http://www.netobjectives.com/blogs/Is-Part-of-the-Agile-Community-Acting-Like-Waterfall-Community-of-Old</feedburner:origLink></item>
<media:rating>nonadult</media:rating><item><title>Links for 2006-08-08 [del.icio.us]</title><link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/L4sb_gtWQXw/jjtrott</link><pubDate>Wed, 09 Aug 2006 00:00:00 PDT</pubDate><guid isPermaLink="false">http://del.icio.us/jjtrott#2006-08-08</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://trailridgeconsulting.typepad.com/pete_behrens_blog/"&gt;Carnival of Agilists&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/L4sb_gtWQXw" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/jjtrott#2006-08-08</feedburner:origLink></item><item><title>Links for 2006-07-17 [del.icio.us]</title><link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/Hgiyc-Lg0TQ/jjtrott</link><pubDate>Tue, 18 Jul 2006 00:00:00 PDT</pubDate><guid isPermaLink="false">http://del.icio.us/jjtrott#2006-07-17</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://blogs.conchango.com/howardvanrooijen/"&gt;Howard van Rooijen's Blog&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/Hgiyc-Lg0TQ" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/jjtrott#2006-07-17</feedburner:origLink></item><item><title>Links for 2006-06-09 [del.icio.us]</title><link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/rvI1iCY3l1Y/jjtrott</link><pubDate>Sat, 10 Jun 2006 00:00:00 PDT</pubDate><guid isPermaLink="false">http://del.icio.us/jjtrott#2006-06-09</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.gembapantarei.com/2006/06/some_thoughts_on_future_state_value_stream_mapping.html"&gt;Kaizen and Lean Manufacturing thoughts | Gemba Panta Rei&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/rvI1iCY3l1Y" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/jjtrott#2006-06-09</feedburner:origLink></item><item><title>Links for 2006-06-08 [del.icio.us]</title><link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/X4hJacAo2zg/jjtrott</link><pubDate>Fri, 09 Jun 2006 00:00:00 PDT</pubDate><guid isPermaLink="false">http://del.icio.us/jjtrott#2006-06-08</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.versionone.com/"&gt;VersionOne - Agile Software Development - DSDM, Scrum &amp;amp; XP Project Management Software&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/X4hJacAo2zg" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/jjtrott#2006-06-08</feedburner:origLink></item><item><title>Links for 2006-06-05 [del.icio.us]</title><link>http://feedproxy.google.com/~r/NetObjectivesThoughts/~3/eV9lyGQa2uI/jjtrott</link><pubDate>Tue, 06 Jun 2006 00:00:00 PDT</pubDate><guid isPermaLink="false">http://del.icio.us/jjtrott#2006-06-05</guid><description>&lt;ul&gt;
&lt;li&gt;&lt;a href="http://www.netobjectives.com/"&gt;Net Objectives: Main Page&lt;/a&gt;&lt;br/&gt;
Home page of Net Objectives, the leader in training, coaching, and consulting services for lean-agile software development, design patterns, agile analysis, scrum, and test-driven development&lt;/li&gt;
&lt;li&gt;&lt;a href="http://controlchaos.com/"&gt;Control Chaos&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://poppendieck.com/"&gt;Poppendieck.LLC&lt;/a&gt;&lt;br/&gt;
Mary and Tom Poppendieck are primary thought leaders in lean software development&lt;/li&gt;
&lt;li&gt;&lt;a href="http://wordpress.com/"&gt;WordPress.com &amp;raquo; Your Blogging Home&lt;/a&gt;&lt;br/&gt;
we are using wordpress, hosted by bluehost&lt;/li&gt;
&lt;li&gt;&lt;a href="http://bluehost.com/"&gt;Web hosting provider - Bluehost.com - domain hosting - PHP Hosting - cheap web hosting - Frontpage Hosting E-Commerce Web Hosting Bluehost&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="http://wordpress.org/"&gt;WordPress &amp;rsaquo; Free Blog Tool and Weblog Platform&lt;/a&gt;&lt;br/&gt;
we are using wordpress for our blogging&lt;/li&gt;
&lt;/ul&gt;&lt;img src="http://feeds.feedburner.com/~r/NetObjectivesThoughts/~4/eV9lyGQa2uI" height="1" width="1"/&gt;</description><feedburner:origLink>http://del.icio.us/jjtrott#2006-06-05</feedburner:origLink></item></channel>
</rss>
