<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:iweb="http://www.apple.com/iweb" version="2.0">
  <channel>
    <title>Presentations</title>
    <link>http://www.theagileengineer.com/public/Presentations/Presentations.html</link>
    <description>Here are presentations I’ve developed related to agile engineering, the most recent ones first. To download a PDF version, navigate to the presentation summary and click the large image.</description>
    <generator>iWeb 3.0.1</generator>
    <item>
      <title>Evo + Scrum = Value Delivery</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2010/3/9_Evo_+_Scrum_%3D_Value_Delivery.html</link>
      <guid isPermaLink="false">b78afe76-cc1a-4984-87ce-35b4e5fa6e59</guid>
      <pubDate>Tue, 9 Mar 2010 17:31:29 -0500</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2010/3/9_Evo_+_Scrum_%3D_Value_Delivery_files/Evo+Scrum_v3_slide1.001.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object088_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:269px; height:201px;&quot;/&gt;&lt;/a&gt;&lt;a href=&quot;Entries/2010/3/9_Evo_+_Scrum_%3D_Value_Delivery_files/ValueDelivery_SG2010.pdf&quot;&gt;My Presentation&lt;/a&gt; from the 2010 Scrum Gathering in Orlando about transitioning from Feature Builders to Value Deliverers. This message is important for Product Owners and Agile Coaches trying to maximize the real business value of every Release. &lt;br/&gt;&lt;br/&gt;Highlights include:&lt;br/&gt;&lt;br/&gt;	1.	Why more features/stories does not equal more value&lt;br/&gt;	2.	Distinction of Ends vs. Means and why planning for the ends is more important (but not currently done in Scrum)&lt;br/&gt;	3.	How to define and measure stakeholder value&lt;br/&gt;	4.	7-step recipe for integrating Value Delivery concepts from Evo with Scrum&lt;br/&gt;&lt;br/&gt;&lt;a href=&quot;http://www.meetup.com/nlscrum/members/7524487/&quot;&gt;Marco Mulder&lt;/a&gt; sat in on my talk and over lunch we continued our discussion around these concepts. Marco is an experienced Agile Coach and practitioner with &lt;a href=&quot;http://www.xebia.com/&quot;&gt;Xebia&lt;/a&gt;. He agreed that the concepts around value, taught by &lt;a href=&quot;http://www.gilb.com/&quot;&gt;Tom and Kai Gilb&lt;/a&gt; and myself, are superior to what’s being taught to Product Owners currently. The challenge is getting the ideas spread to a broader audience. &lt;br/&gt;&lt;br/&gt;Marco agreed with me that the title of the presentation wasn’t the best description for the main point, which was a shift in focus from means to ends. The concepts borrowed from Evo are the main points, not the Evo method itself. I haven’t come up with a better title, but I have submitted this for Agile 2010, so perhaps if I get selected a better title is in order.</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2010/3/9_Evo_+_Scrum_%3D_Value_Delivery_files/Evo+Scrum_v3_slide1.001.jpg" length="140747" type="image/jpeg"/>
    </item>
    <item>
      <title>Changing Organizational Culture</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2009/6/28_Changing_Organizational_Culture.html</link>
      <guid isPermaLink="false">85115bfb-d96e-47a3-bc0a-1114ac146e8b</guid>
      <pubDate>Sun, 28 Jun 2009 07:28:46 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2009/6/28_Changing_Organizational_Culture_files/CultureChangeTitle.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object089_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:269px; height:201px;&quot;/&gt;&lt;/a&gt;Presentation from the 2009 &lt;a href=&quot;http://www.gilb.com/&quot;&gt;Tom Gilb&lt;/a&gt; conference on “Culture Change”. Discusses 7 proven techniques (or at least those that have worked for me) on changing software development culture. Also presents some emerging techniques that I’m starting to research, including how Babic, my &lt;a href=&quot;http://www.nabaztag.com/&quot;&gt;Nabaztag&lt;/a&gt; rabbit, can help keep software teams on track and bring some fun into development teams.&lt;br/&gt;</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2009/6/28_Changing_Organizational_Culture_files/CultureChangeTitle.jpg" length="67453" type="image/jpeg"/>
    </item>
    <item>
      <title>Agile Engineering for Architects</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2009/4/24_Agile_Engineering_for_Architects.html</link>
      <guid isPermaLink="false">3ee19a18-56f7-40ea-a642-8adb6b993e7f</guid>
      <pubDate>Fri, 24 Apr 2009 20:16:52 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2009/4/24_Agile_Engineering_for_Architects_files/AE_ADC_2008.001.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object028.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:269px; height:201px;&quot;/&gt;&lt;/a&gt;Presentation from the April Richmond Java User Group meeting. This is a slight update of a talk I gave at Agile Development Practices on November 13, 2008. Shows how to break down a business strategy into possible system qualities, how to quantify them and then how to use Impact Estimation to determine best one. Finally discusses how to integrate this into a Scrum process.&lt;br/&gt;&lt;br/&gt;Here’s the &lt;a href=&quot;perma://BLPageReference/F67DAC4D-6B0B-4AD3-99EF-94686E5B6835&quot;&gt;Impact Estimation &lt;/a&gt;worksheet used in the presentation.&lt;br/&gt;&lt;br/&gt;</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2009/4/24_Agile_Engineering_for_Architects_files/AE_ADC_2008.001.jpg" length="123865" type="image/jpeg"/>
    </item>
    <item>
      <title>Measuring Business Value with Agile</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2008/9/23_Measurable_Business_Value_with_Agile.html</link>
      <guid isPermaLink="false">7e388338-277f-4e65-9d47-c846c9bc059e</guid>
      <pubDate>Tue, 23 Sep 2008 23:03:24 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2008/9/23_Measurable_Business_Value_with_Agile_files/MBV_Cover.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object091_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:269px; height:201px;&quot;/&gt;&lt;/a&gt;Updated version of talk from &lt;a href=&quot;http://www.agile2008.org/&quot;&gt;Agile 2008&lt;/a&gt; for &lt;a href=&quot;http://www.agilerichmond.com/&quot;&gt;Agile Richmond&lt;/a&gt;. This talk discusses what I think is missing from Agile methods like Scrum and XP, namely that they only focus on 1/2 of the problem: building things right. What they lack is a way to know you’re working on building the right things. I present four practices that can help address this:&lt;br/&gt;&lt;br/&gt;	1.	Deliver the Right Thing&lt;br/&gt;	2.	Measure Business Value&lt;br/&gt;	3.	Align to Value&lt;br/&gt;	4.	Measure Progress to Goals&lt;br/&gt;&lt;br/&gt;These practices are strongly influenced by &lt;a href=&quot;http://www.gilb.com/&quot;&gt;Evo&lt;/a&gt; and cover areas that in my experience are lacking in mainstream Agile thinking. I’ll go through some exercises that help reinforce these concepts in practice.</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2008/9/23_Measurable_Business_Value_with_Agile_files/MBV_Cover.jpg" length="121413" type="image/jpeg"/>
    </item>
    <item>
      <title>Agile Engineering for Managers</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2008/6/24_Agile_Engineering_for_Managers.html</link>
      <guid isPermaLink="false">41ff82aa-042f-46cb-a05d-24ce87a51d76</guid>
      <pubDate>Mon, 23 Jun 2008 22:03:12 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2008/6/24_Agile_Engineering_for_Managers_files/AgileEngineeringForManagers.001.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object092_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:269px; height:183px;&quot;/&gt;&lt;/a&gt;Presentation that’s part of a series I’m doing on the subject, this one aimed at software managers. After some story telling, I introduce Principles of Agile Engineering and questions managers can ask to see if their team is doing agile engineering.</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2008/6/24_Agile_Engineering_for_Managers_files/AgileEngineeringForManagers.001.jpg" length="254015" type="image/jpeg"/>
    </item>
    <item>
      <title>Agile Engineering: Test Driven Development</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2008/4/28_Test_Driven_Development.html</link>
      <guid isPermaLink="false">8cf5c8fc-b8f4-4c2e-a0b3-c4dbd3363c00</guid>
      <pubDate>Mon, 28 Apr 2008 12:13:37 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2008/4/28_Test_Driven_Development_files/AE_TDD_CapOne.030.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object093_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:268px; height:192px;&quot;/&gt;&lt;/a&gt;Presentation I gave in March 2008 at local company doing agile development with 60+ Scrum teams. This is a simple introduction that covers the basic principles and provides an exercise in practicing TDD (without a computer). Overall feedback was good but not great. May dust-off at some point and give it again.</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2008/4/28_Test_Driven_Development_files/AE_TDD_CapOne.030.jpg" length="76438" type="image/jpeg"/>
    </item>
    <item>
      <title>Smart Decisions</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2008/4/23_Smart_Decisions.html</link>
      <guid isPermaLink="false">52473b6f-43a5-4e5b-9504-d46822e0c866</guid>
      <pubDate>Wed, 23 Apr 2008 23:40:04 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2008/4/23_Smart_Decisions_files/SmartDecisions_v4.011.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object094_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:268px; height:202px;&quot;/&gt;&lt;/a&gt;My latest update on a presentation I first gave in July 2007 at &lt;a href=&quot;http://www.gilb.com/&quot;&gt;Tom Gilb’s&lt;/a&gt; seminar and later at &lt;a href=&quot;http://www.nofluffjuststuff.com/&quot;&gt;No Fluff Just Stuff&lt;/a&gt;. First introduction of Evo + Scrum to work from Strategic to Tactical levels with mini-case study that goes from quantified business objectives to Scrum backlog. Quote I like the most: “Just because you’re doing Agile doesn’t mean you’re making smart decisions”. </description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2008/4/23_Smart_Decisions_files/SmartDecisions_v4.011.jpg" length="180754" type="image/jpeg"/>
    </item>
    <item>
      <title>Scaling Agility</title>
      <link>http://www.theagileengineer.com/public/Presentations/Entries/2008/4/20_Scaling_Agility.html</link>
      <guid isPermaLink="false">4df290f1-3532-40d5-8eb3-1c2197c319dd</guid>
      <pubDate>Sun, 20 Apr 2008 10:07:49 -0400</pubDate>
      <description>&lt;a href=&quot;http://www.theagileengineer.com/public/Presentations/Entries/2008/4/20_Scaling_Agility_files/ScalingAgility_May06.001.jpg&quot;&gt;&lt;img src=&quot;http://www.theagileengineer.com/public/Presentations/Media/object095_1.jpg&quot; style=&quot;float:left; padding-right:10px; padding-bottom:10px; width:268px; height:153px;&quot;/&gt;&lt;/a&gt;Presentation I first gave at the &lt;a href=&quot;http://agileconference.org/&quot;&gt;Agile Business Conference&lt;/a&gt; in London 2005. Discusses how the team I was leading doing XP with 40 developers and 100+ team members was shipping a commercial enterprise product using XP. Discusses what was working and not working with some thoughts of my own. I got very good responses to this presentation, mostly because it’s not theoretical but a very practical how-to for large agile teams. I later presented this at &lt;a href=&quot;http://www.nofluffjuststuff.com/&quot;&gt;No Fluff Just Stuff&lt;/a&gt;.</description>
      <enclosure url="http://www.theagileengineer.com/public/Presentations/Entries/2008/4/20_Scaling_Agility_files/ScalingAgility_May06.001.jpg" length="109178" type="image/jpeg"/>
    </item>
  </channel>
</rss>

