<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="http://www.startupcto.com/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="http://www.startupcto.com/feed.php">
        <title>StartupCTO processes</title>
        <description></description>
        <link>http://www.startupcto.com/</link>
        <image rdf:resource="http://www.startupcto.com/lib/images/favicon.ico" />
       <dc:date>2010-09-08T09:04:29-04:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/business-vs-technical-requirements?rev=1265496889"/>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/code-documentation-standards?rev=1241910137"/>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/documentation-practical-practices-and-ideas?rev=1245219110"/>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/home?rev=1234671749"/>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/project-management-when-you-dont-know-what-you-are-building?rev=1213844660"/>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/web-qa-testing?rev=1242863539"/>
                <rdf:li rdf:resource="http://www.startupcto.com/processes/writing_good_functional_requirements?rev=1213897751"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="http://www.startupcto.com/lib/images/favicon.ico">
        <title>StartupCTO</title>
        <link>http://www.startupcto.com/</link>
        <url>http://www.startupcto.com/lib/images/favicon.ico</url>
    </image>
    <item rdf:about="http://www.startupcto.com/processes/business-vs-technical-requirements?rev=1265496889">
        <dc:format>text/html</dc:format>
        <dc:date>2010-02-06T17:54:49-04:00</dc:date>
        <title>Building Widgets: Business Requirements vs. Technical Requirements</title>
        <link>http://www.startupcto.com/processes/business-vs-technical-requirements?rev=1265496889</link>
        <description>Have you ever built a widget? No, I’m not talking about one of those Mac OS X Dashboard Widgets, as cool as they are. Nor a Confabulator Widget, or a Yahoo! Widget. I’m talking about a good old-fashioned widget.

What’s that, you ask? Surely you don’t need me to explain a widget to you.</description>
    </item>
    <item rdf:about="http://www.startupcto.com/processes/code-documentation-standards?rev=1241910137">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-09T19:02:17-04:00</dc:date>
        <title>Code Documentation Standards</title>
        <link>http://www.startupcto.com/processes/code-documentation-standards?rev=1241910137</link>
        <description>Documenting your code well is almost as important as making sure it is bug free. In fact, many people would argue that it is more important, because if you document it well, at least somebody else can come in and fix your bugs later on.

I like using the *doc format for code documentation (phpdoc, javadoc, etc.) because it is fairly standard and easily machine+human readable. It uses @ identifiers for various peices of documentation (e.g. @param, @return, @see, etc.)</description>
    </item>
    <item rdf:about="http://www.startupcto.com/processes/documentation-practical-practices-and-ideas?rev=1245219110">
        <dc:format>text/html</dc:format>
        <dc:date>2009-06-17T02:11:50-04:00</dc:date>
        <title>Documentation - Practical Practices &amp; Ideas</title>
        <link>http://www.startupcto.com/processes/documentation-practical-practices-and-ideas?rev=1245219110</link>
        <description>This document aims to give some practical ideas and advice for Internet startups and Internet development shops as to what they should consider documenting when they're writing 'documentation'. There's probably a lot of things on here that you don't need to document in your particular case, and there's probably a lot of things that aren't on here that you do need to document.</description>
    </item>
    <item rdf:about="http://www.startupcto.com/processes/home?rev=1234671749">
        <dc:format>text/html</dc:format>
        <dc:date>2009-02-14T23:22:29-04:00</dc:date>
        <title>Processes</title>
        <link>http://www.startupcto.com/processes/home?rev=1234671749</link>
        <description>processes index</description>
    </item>
    <item rdf:about="http://www.startupcto.com/processes/project-management-when-you-dont-know-what-you-are-building?rev=1213844660">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-18T23:04:20-04:00</dc:date>
        <title>Project Management When You Don't Know What You're Building</title>
        <link>http://www.startupcto.com/processes/project-management-when-you-dont-know-what-you-are-building?rev=1213844660</link>
        <description>Next time you’re flying somewhere in the US, consider this: the air traffic controllers that are guiding your plane are using technology originally developed in the 1960’s and 1970’s called ARTS to make sure you don’t crash into another plane. They started working on a new system called AAS in 1983, canned it in 1994, and resurrected part of it in 1996. Now we’re already in 2006, and they’re saying Phase I deployment won’t be done for another year.</description>
    </item>
    <item rdf:about="http://www.startupcto.com/processes/web-qa-testing?rev=1242863539">
        <dc:format>text/html</dc:format>
        <dc:date>2009-05-20T19:52:19-04:00</dc:date>
        <title>Website + WebApp QA &amp; Testing Procedures</title>
        <link>http://www.startupcto.com/processes/web-qa-testing?rev=1242863539</link>
        <description>This is intended to be a brief overview of some of the things you need to do think about when doing QA/testing a website or web application. It is aimed more at the front-end than the back-end, and is not comprehensive (but should still serve as an excellent guide).</description>
    </item>
    <item rdf:about="http://www.startupcto.com/processes/writing_good_functional_requirements?rev=1213897751">
        <dc:format>text/html</dc:format>
        <dc:date>2008-06-19T13:49:11-04:00</dc:date>
        <title>The Story of the Paperclip: Writing Good Functional Requirements</title>
        <link>http://www.startupcto.com/processes/writing_good_functional_requirements?rev=1213897751</link>
        <description>The Humble Paperclip

The paperclip was invented in the 1890s, and has been around, more or less unchanged, for the last hundred years. It isn’t likely that anyone created a requirements document for the paperclip, but I sometimes like to think of what it would have looked like if someone had.</description>
    </item>
</rdf:RDF>
