<rss version="2.0">
	<channel>
		<title><![CDATA[Agile]]></title>
		<description><![CDATA[Agile]]></description>
		<link>http://www.thetaboard.com?&amp;t=2728</link>
		<language>en-us</language>		
<item>
	<title><![CDATA[Need a bit more detail? Use ThetaBoard Checklists!]]></title>
	<description><![CDATA[<p class="abstract">We're rolling out several new features this week. First up...</p>
<h2 class="abstract">Card Checklists</h2>
<p class="abstract"><img style="float: right; margin: 10px; border: 0px none;" src="http://c645303.r3.cf2.rackcdn.com/3a6ee5c7fe6e052ed6f214021cb82ee8.png" alt="ThetaBoard Checklists" width="294" height="268" />Checklists are todo lists embedded in ThetaBoard Cards. You can create multiple Checklists for on each card and sort them in order of importance. Make sure you visit your "Account Preferences" page to enable this feature! Or you can enable them on a Board-by-Board basis.</p>
<p>To create a Checklist click the "+ New Checklist" link on your Card. To add multiple items to your Checklist, type "Control + Enter" after you have finished entering your item--you will save the current item and create a new one for you.</p>
<h2>Use Cases</h2>
<p>We think you'll find Checklists invaluable for when you can't logically split a card into two separate cards but want to provide a more granular level of detail.</p>
<h2>Coming Soon</h2>
<p>We are planning on updating the Checklist feature in the coming weeks to allow you to create a new Card from a single Checklist item. If you have any other ideas or suggestions, please <a href="mailto:support@thetaboard.com">let us know</a>!</p>]]></description>
	<link>http://www.thetaboard.com/blog/need-a-bit-more-detail-use-thetaboard-checklists?r=391</link>
</item>
<item>
	<title><![CDATA[Why I'm Making ThetaBoard]]></title>
	<description><![CDATA[<p class="abstract">Nobody really likes to be criticized or have their startup ideas questioned. Over the course of the day yesterday I got some feedback about my current project and it's prospects for success:</p>
<blockquote>
<p>"the only problem is we have project management web app fatigue."</p>
</blockquote>
<p>and</p>
<blockquote>
<p>"This is a service that I've seen before. Not yours of course, but others like it."</p>
</blockquote>
<p>Very similar comments telling me that web-based project management tools are a dime-a-dozen. These were not vitriolic comments mind you. They just wanted to know why they should consider--and I should bother writing--yet another project management tool.</p>
<h2>Your Project Management Tool Sucks to Everyone But You</h2>
<p>Everyone works differently so it makes sense that everyone's ideal project management software would be different.&nbsp;Invariably, if you get a team of 5 people to use a tool, at least one of them will not like the tool you've choosen. At best, you can get people to suck it up and use the tool in front of them. However, in time, the process will begin to break down and ultimately the tool will be abandoned.&nbsp;What is the longest you've stuck with the same project management tool?</p>
<h2>Your Software Shits on the Agile Manifesto</h2>
<p>The very first tenet of the Agile Manifesto is:</p>
<blockquote>
<p><strong>Individuals and interactions</strong> over processes and tools</p>
</blockquote>
<p>It would lead you to believe that tools developed to faciliate agile software development would practice what they preach. Unfortunately they don't. Project Management software nearly always tries to impart its <em>genius</em>&nbsp;new process designed to <em>supercharge</em> your development.</p>
<p>Unfortunately, the development process you have built into your software is <em>your process</em>. Your customers likely don't share your vision. You may actually convince them that it will improve their process so they sign up for your product. It's their job to convince their team members. It doesn't work.</p>
<p>By introducing your&nbsp;<em>genius</em>&nbsp;new workflow/project management tool you are putting the focus of your software development on the tool and forcing your individual team members to adjust. It's as&nbsp;<em>unagile&nbsp;</em>as it gets.</p>
<p>Don't get me wrong, a lot of <a href="http://www.podio.com">these</a> <a href="http://www.projectorpm.com">tools</a> are <a href="http://www.getflow.com">slick</a> as <a href="http://do.com">hell</a>. And I'm not saying they aren't great products. I'm sure they help a lot of people get a lot done. But they all put process and tool ahead of individuals and interaction.</p>
<h2>So What's So Special About ThetaBoard</h2>
<div>Right now--nothing. It's just a buggly MVP that I decided to launch before it was ready so I could start getting feedback. But my vision for it excites me:</div>
<ul style="margin-top: 10px; margin-bottom: 10px;">
<li><strong>Simplicity at it's core.</strong>&nbsp;ThetaBoard is going to be a barebones (yet effective) tool for keeping track of projects and tasks.</li>
<li><strong>Customizable.</strong>&nbsp;You will be able to customize your ThetaBoard to fit your company's development process. Furthermore, your <em>users</em>&nbsp;will be able to further customize their ThetaBoard experience so they like it more.</li>
<li><strong>Extensibl<em>e.</em></strong>&nbsp;Users will be able to add functionality to ThetaBoard's core functionality through APIs.</li>
</ul>
<p>I think that the #1 reason people stop using a tool is because it contains too many unused features. There is something psychological about that excess, waste and clutter. I think that if I can create a tool that removes all of this excess, people will use it and use it longer.</p>
<ul>
</ul>
<h2>ThetaBoard Sucks Too</h2>
<p>I know. In fact I constantly find myself violating the first tenet of the Agile Manifesto myself. I've let terms like "iterations" and "stories" creep into the design and code. I constantly find myself making decisions on behalf of my future users. When this happens, I stand back, and rip out the functionality and start over.</p>
<p>There are two camps that won't ever like ThetaBoard: people who feel like ThetaBoard imparts <em>its own</em>&nbsp;process on them and those who need much more functionality. I'm going strive to make the first group of users very, very small. I'm going to simply ignore the latter.</p>
<p>What you see now is an MVP that's taken a wrong turn. I've gone back to the drawing board and started a complete redesign to stick more closely to the vision described above. When ThetaBoard finally leaves beta and I start adding premium plans, I think it will be a tool that sits in the background and adapts to your process letting you <em>really</em>&nbsp;supercharge your development.</p>
<p><a href="http://news.ycombinator.com/item?id=3806628">Discussion on Hacker News</a></p>]]></description>
	<link>http://www.thetaboard.com/blog/why-im-making-thetaboard?r=376</link>
</item>
<item>
	<title><![CDATA[Welcome to ThetaBoard]]></title>
	<description><![CDATA[<p class="abstract">Welcome to ThetaBoard!</p>
<p class="abstract">ThetaBoard is a simple tool for helping you get things done. Use it as an agile project management tool. Use it to plan your Thanksgiving dinner. Use it to plan your fantasy football draft. We'll keep it simple and you do the rest.</p>
<p class="abstract">We hope you find our product useful and this blog informative. If you have any questions or comments, feel free to email us at <a href="mailto:support@thetaboard.com">support@thetaboard.com</a>. </p>
<p class="abstract">Thanks!</p>
<p class="abstract">The ThetaBoard Team</p>]]></description>
	<link>http://www.thetaboard.com/blog/welcome-to-thetaboard?r=366</link>
</item>
	</channel>
</rss>