<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0">
    <channel>
        <title>Agile Storytelling - Tag - In a past life…</title>
        <link>https://archive.jtimothyking.com/tags/agile-storytelling/</link>
        <description>Agile Storytelling - Tag - In a past life…</description>
        <generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 08 Jan 2010 19:00:35 &#43;0000</lastBuildDate><atom:link href="https://archive.jtimothyking.com/tags/agile-storytelling/" rel="self" type="application/rss+xml" /><item>
    <title>Agile Storytelling</title>
    <link>https://archive.jtimothyking.com/2010/01/08/agile-storytelling/</link>
    <pubDate>Fri, 08 Jan 2010 19:00:35 &#43;0000</pubDate>
    <author>J. Timothy King</author>
    <guid>https://archive.jtimothyking.com/2010/01/08/agile-storytelling/</guid>
    <description><![CDATA[<p>I generally write a story using a process similar to <a href="http://www.advancedfictionwriting.com/art/snowflake.php">Randy Ingermanson’s “Snowflake” method</a>, but I don’t think of my process as resembling anything like a snowflake. Randy is a physicist, as I understand, so maybe that explains his choice of metaphor. I, on the other hand, come from the sordid world of software development. So from the world of software, I call my method “Agile Storytelling.”</p>
<p>When you’re designing a piece of custom software, in theory, your client tells you what he wants, and then you go and tell the computer how to give it to him. In reality, your client will never tell you what he actually wants, usually because he himself doesn’t actually know. But that’s okay, because he will most assuredly change his mind anyhow, as soon as you figure out how to do what you thought he asked for in the first place.</p>
<p>In other words, you’re trying to write something that you really don’t understand and that keeps changing from under your feet&hellip; kind of like writing a novel.</p>]]></description>
</item>
</channel>
</rss>
