<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/xsl/rss.xsl" type="text/xsl"?>
<rss version="2.0" xmlns:podcast="https://podcastindex.org/namespace/1.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http://purl.org/dc/terms/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Different Kind of Agile's Podcast</title>
    <link>https://www.podomatic.com/podcasts/agile</link>
    <description>
      <![CDATA[]]>
    </description>
    <language>en-us</language>
    <generator>Podomatic RSS Generator</generator>
    <pubDate>Wed, 17 Jul 2019 16:57:41 +0000</pubDate>
    <itunes:keywords></itunes:keywords>
    <copyright>Copyright 2019 Different Kind of Agile</copyright>
    <itunes:subtitle>Give it a listen!</itunes:subtitle>
    <itunes:type>episodic</itunes:type>
    <itunes:explicit>false</itunes:explicit>
    <itunes:block>no</itunes:block>
    <itunes:image href="https://agile.podomatic.com/images/default/D-1400.png"/>
    <image>
      <url>https://agile.podomatic.com/images/default/D-1400.png</url>
      <title>Different Kind of Agile's Podcast</title>
      <link>https://www.podomatic.com/podcasts/agile</link>
    </image>
    <itunes:author>Different Kind of Agile</itunes:author>
    <itunes:summary></itunes:summary>
    <atom:link href="https://agile.podomatic.com/archive.xml" rel="self" title="Different Kind of Agile's Podcast" type="application/rss+xml"/>
    <item>
      <title>Customer Journey</title>
      <description>
        <![CDATA[So, how does your customer approach you? What is she thinking? What are her feelings towards her problem? What pressure does she have, and who is directly influencing her. How is she managing with her crisis today? This podcast covers this and much more. Check it out!]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-09T03_19_50-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-09T03_19_50-07_00</comments>
      <pubDate>Fri, 09 Jun 2017 10:19:50 +0000</pubDate>
      <dcterms:modified>2017-06-09</dcterms:modified>
      <dcterms:created>2017-06-09</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-09T03_19_50-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-09T03_19_50-07_00.mp3?_=1497003592.12192622" length="4834393" type="audio/mpeg"/>
      <itunes:duration>201</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>So, how does your customer approach you? What is she thinking? What are her feelings towards her problem? What pressure does she have, and who is directly influencing her. How is she managing with her crisis today? This podcast covers this and much more. Check it out!</itunes:summary>
      <itunes:subtitle>So, how does your customer approach you? What is she thinking? What are her feelings towards her ...</itunes:subtitle>
    </item>
    <item>
      <title>Epics and Themes</title>
      <description>
        <![CDATA[An epic is where we start to go into detail. We try to map out the scenario, a set of steps to be found within one process, or perhaps a use case where we might have standard and alternate flows. This will be content where some additional analysis might be required, looking at impact, dependencies and the costs and benefits of the value we are generating with our solution. A sound epic structure also helps us in establishing transparency, when you think about it. Let’s try to map this out.]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-04T02_35_13-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_35_13-07_00</comments>
      <pubDate>Sun, 04 Jun 2017 09:35:13 +0000</pubDate>
      <dcterms:modified>2017-06-04</dcterms:modified>
      <dcterms:created>2017-06-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_35_13-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-04T02_35_13-07_00.mp3?_=1496568958.12182281" length="5328601" type="audio/mpeg"/>
      <itunes:duration>222</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>An epic is where we start to go into detail. We try to map out the scenario, a set of steps to be found within one process, or perhaps a use case where we might have standard and alternate flows. This will be content where some additional analysis might be required, looking at impact, dependencies and the costs and benefits of the value we are generating with our solution. A sound epic structure also helps us in establishing transparency, when you think about it. Let&#8217;s try to map this out.</itunes:summary>
      <itunes:subtitle>An epic is where we start to go into detail. We try to map out the scenario, a set of steps to be...</itunes:subtitle>
    </item>
    <item>
      <title>Kano Model Postscript</title>
      <description>
        <![CDATA[What will very often also change once you start modifying processes willy nillly like we’re doing in this exercise? The business rules could very well change, and most likely will. Now what do the results look like? Now you have come up with a process that is unique for that particular actor, based upon some modified constraints you have put together with revised business rules. Now, can that possibly be a delighter for your customer? Possibly.]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-04T02_32_49-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_32_49-07_00</comments>
      <pubDate>Sun, 04 Jun 2017 09:32:49 +0000</pubDate>
      <dcterms:modified>2017-06-04</dcterms:modified>
      <dcterms:created>2017-06-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_32_49-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-04T02_32_49-07_00.mp3?_=1496568774.12182279" length="3144985" type="audio/mpeg"/>
      <itunes:duration>131</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>What will very often also change once you start modifying processes willy nillly like we&#8217;re doing in this exercise? The business rules could very well change, and most likely will. Now what do the results look like? Now you have come up with a process that is unique for that particular actor, based upon some modified constraints you have put together with revised business rules. Now, can that possibly be a delighter for your customer? Possibly.</itunes:summary>
      <itunes:subtitle>What will very often also change once you start modifying processes willy nillly like we&#8217;re doing...</itunes:subtitle>
    </item>
    <item>
      <title>Kano Model</title>
      <description>
        <![CDATA[Can standard requirements look different, depending on the market you’re trying to serve? You betcha. A great differentiator would be how requirements are seen in developing and developed countries. What. You’re saying there is no such thing as such a divide, and you can find both in different regions and even countries in the world. Guess things are more fragmented than we would like to admit.]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-04T02_31_47-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_31_47-07_00</comments>
      <pubDate>Sun, 04 Jun 2017 09:31:47 +0000</pubDate>
      <dcterms:modified>2017-06-04</dcterms:modified>
      <dcterms:created>2017-06-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_31_47-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-04T02_31_47-07_00.mp3?_=1496568709.12182278" length="4675993" type="audio/mpeg"/>
      <itunes:duration>194</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>Can standard requirements look different, depending on the market you&#8217;re trying to serve? You betcha. A great differentiator would be how requirements are seen in developing and developed countries. What. You&#8217;re saying there is no such thing as such a divide, and you can find both in different regions and even countries in the world. Guess things are more fragmented than we would like to admit.</itunes:summary>
      <itunes:subtitle>Can standard requirements look different, depending on the market you&#8217;re trying to serve? You bet...</itunes:subtitle>
    </item>
    <item>
      <title>Planning Poker</title>
      <description>
        <![CDATA[This technique is coming straight out of the agile and scrum world, and is a way to perform estimation. I believe it has a strong similarity to the Delphi method, but there are some philosophical differences. Let me go through them with you.]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-04T02_29_26-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_29_26-07_00</comments>
      <pubDate>Sun, 04 Jun 2017 09:29:26 +0000</pubDate>
      <dcterms:modified>2017-06-04</dcterms:modified>
      <dcterms:created>2017-06-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_29_26-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-04T02_29_26-07_00.mp3?_=1496568622.12182277" length="5371801" type="audio/mpeg"/>
      <itunes:duration>223</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>This technique is coming straight out of the agile and scrum world, and is a way to perform estimation. I believe it has a strong similarity to the Delphi method, but there are some philosophical differences. Let me go through them with you.</itunes:summary>
      <itunes:subtitle>This technique is coming straight out of the agile and scrum world, and is a way to perform estim...</itunes:subtitle>
    </item>
    <item>
      <title>User Stories</title>
      <description>
        <![CDATA[Don't ask the user for specifications, because you are asking them to do your job. This podcast describes user stories and how they concentrate on needs.]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-04T02_26_10-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_26_10-07_00</comments>
      <pubDate>Sun, 04 Jun 2017 09:26:10 +0000</pubDate>
      <dcterms:modified>2017-06-04</dcterms:modified>
      <dcterms:created>2017-06-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_26_10-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-04T02_26_10-07_00.mp3?_=1496568420.12182276" length="4959385" type="audio/mpeg"/>
      <itunes:duration>206</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>Don't ask the user for specifications, because you are asking them to do your job. This podcast describes user stories and how they concentrate on needs.</itunes:summary>
      <itunes:subtitle>Don't ask the user for specifications, because you are asking them to do your job. This podcast d...</itunes:subtitle>
    </item>
    <item>
      <title>Agile For the Rest of Us</title>
      <description>
        <![CDATA[This podcast will talk about how the business looks on IT development with envy as they are able to get something out the door....and they can't]]>
      </description>
      <guid isPermaLink="true">https://agile.podomatic.com/entry/2017-06-04T02_20_43-07_00</guid>
      <comments>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_20_43-07_00</comments>
      <pubDate>Sun, 04 Jun 2017 09:20:43 +0000</pubDate>
      <dcterms:modified>2017-06-04</dcterms:modified>
      <dcterms:created>2017-06-04</dcterms:created>
      <link>https://www.podomatic.com/podcasts/agile/episodes/2017-06-04T02_20_43-07_00</link>
      <dc:creator>Different Kind of Agile</dc:creator>
      <itunes:keywords></itunes:keywords>
      <enclosure url="https://agile.podomatic.com/enclosure/2017-06-04T02_20_43-07_00.mp3?_=1496568049.12182273" length="3571801" type="audio/mpeg"/>
      <itunes:duration>148</itunes:duration>
      <itunes:image href="https://assets.podomatic.net/ts/d5/d1/2d/mboyle99/1400x1400-363x363+64+7_12182274.jpg"/>
      <itunes:summary>This podcast will talk about how the business looks on IT development with envy as they are able to get something out the door....and they can't</itunes:summary>
      <itunes:subtitle>This podcast will talk about how the business looks on IT development with envy as they are able ...</itunes:subtitle>
    </item>
  </channel>
</rss>
