<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Seesaw Style on Kind of Idea</title>
    <link>https://kindofidea.com/tags/seesaw-style/</link>
    <description>Recent content in Seesaw Style on Kind of Idea</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Mon, 08 Jul 2013 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://kindofidea.com/tags/seesaw-style/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Follow the Seesaw Style</title>
      <link>https://kindofidea.com/follow-the-seesaw-style/</link>
      <pubDate>Mon, 08 Jul 2013 00:00:00 +0000</pubDate>
      <guid>https://kindofidea.com/follow-the-seesaw-style/</guid>
      <description>&lt;p&gt;With the &lt;a href=&#34;http://valeriofarias.com/siga-o-metodo-ddd&#34;&gt;DDD method&lt;/a&gt;, I developed a strategic vision focused on decentralization through automation. But I needed to give the team a simple way to handle day-to-day tasks—in other words, a tactical approach. That’s how I came up with the seesaw style.&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;Seesaw style&lt;/strong&gt; means continuous effort distributed proportionally among everyone involved in a project.&lt;/p&gt;&#xA;&lt;img src=&#34;https://kindofidea.com/images/gangorra.jpg&#34; style=&#34;float:right;&#34; alt=&#34;Seesaw style&#34; /&gt;&#xA;&lt;p&gt;This way, tasks simply flow and no one gets overloaded.&lt;/p&gt;&#xA;&lt;p&gt;I use this term because this way of handling a project resembles playing on a seesaw.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
