<?xml version="1.0"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:syn="http://purl.org/rss/1.0/modules/syndication/"
         xmlns="http://purl.org/rss/1.0/">




    



<channel rdf:about="http://www.pragmaticmarketing.com/resources/requirements/RSS">
  <title>Articles on Requirements</title>
  <link>http://www.pragmaticmarketing.com</link>
  
  <description>
    
       
       
  </description>
  
  
  
            <syn:updatePeriod>daily</syn:updatePeriod>
            <syn:updateFrequency>1</syn:updateFrequency>
            <syn:updateBase>2007-06-02T15:10:00Z</syn:updateBase>
        
  
  <image rdf:resource="http://www.pragmaticmarketing.com/logo.jpg"/>

  <items>
    <rdf:Seq>
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/05/0501sk1"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/magazine/5/5/add-201cquick-hits201d-and-finally-address-those-priority-3-enhancements"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/magazine/4/3/ask"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/magazine/4/3/0605sk"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/magazine/3/1/0501bh"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/07/0702jm"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/06/0604sj"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/02/0203sj"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/magazine/5/3/easy-to-use-for-whom-defining-the-customer-and-user-experience-for-enterprise-software"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/05/0511jm2"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/05/0501jm2"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/01/0109sj"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/04/0403jm_b"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/magazine/4/1/managing-product-requirements"/>
        
        
            <rdf:li rdf:resource="http://www.pragmaticmarketing.com/publications/topics/05/0506jm1"/>
        
    </rdf:Seq>
  </items>

</channel>

    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/05/0501sk1">        <title>A House With No Front Door</title>        <link>http://www.pragmaticmarketing.com/publications/topics/05/0501sk1</link>        <description>In my effort to build products with limited resources, I often spend time justifying the need for features. By Saeed Khan</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-10T17:40:15Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/magazine/5/5/add-201cquick-hits201d-and-finally-address-those-priority-3-enhancements">        <title>Add “Quick Hits” and (Finally) Address Those Priority 3 Enhancements</title>        <link>http://www.pragmaticmarketing.com/publications/magazine/5/5/add-201cquick-hits201d-and-finally-address-those-priority-3-enhancements</link>        <description>Woe to the minor enhancement request that gets tagged as a dreaded Priority 3 or nice-to-have feature during the prioritization phase of a project. All too often, it will get pushed into a future-release black hole—never to be seen again. By Chloe Morrow</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>gjoyce</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>product management</dc:subject>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-11-06T14:54:20Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/magazine/4/3/ask">        <title>Ask the Expert: Does a Formal Requirements Process Stifle Creativity and Innovation?</title>        <link>http://www.pragmaticmarketing.com/publications/magazine/4/3/ask</link>        <description>“Our company seems to spend more time writing requirements and specifications than we do actually writing code and developing products. Shouldn’t we value the result more than the process?”</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>pragmatic marketer</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-10-22T23:06:09Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/magazine/4/3/0605sk">        <title>Building a Better Beta</title>        <link>http://www.pragmaticmarketing.com/publications/magazine/4/3/0605sk</link>        <description>Delivering a successful beta program can be one of the hardest things to do as a product manager. By Saeed Khan.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>skhan</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>product management</dc:subject>                    <dc:subject>working with development</dc:subject>                    <dc:subject>pragmatic marketer</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-10T18:25:26Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/magazine/3/1/0501bh">        <title>Clean, Cutting-Edge UI Design Cuts McAfee's Support Calls by 90%</title>        <link>http://www.pragmaticmarketing.com/publications/magazine/3/1/0501bh</link>        <description>With 20,000 downloads of ProtectionPilot over a 10-week time span, McAfee received only 170 calls to support lines. Here are 23 detailed tips gleaned from McAfee and their external UI design team. By Bruce Hadley.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>bhadley</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>pragmatic marketer</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-06-17T18:45:04Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/07/0702jm">        <title>Creating the Right Product Roadmap</title>        <link>http://www.pragmaticmarketing.com/publications/topics/07/0702jm</link>        <description>In most companies, Product Management is responsible for building, maintaining, and presenting the product roadmap inside and outside of the company. However, one of the biggest problems is they build, and build, and build, and finally re-build their roadmaps! By John Milburn</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jmilburn</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>product management</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-14T04:08:10Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/06/0604sj">        <title>Data driven design</title>        <link>http://www.pragmaticmarketing.com/publications/topics/06/0604sj</link>        <description>“My mom should be able to use it” translates into making an easy interface while “I want absolute control over the placement of items in my document” requires a powerful interface. By Steve Johnson</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sjohnson</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-10T18:23:45Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/02/0203sj">        <title>Defects or Features Next</title>        <link>http://www.pragmaticmarketing.com/publications/topics/02/0203sj</link>        <description>Should we fix defects or add new features? Should we deliver on the promises we've already made to our customers, or should we make new promises to get new customers? By Steve Johnson</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-10T17:21:09Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/magazine/5/3/easy-to-use-for-whom-defining-the-customer-and-user-experience-for-enterprise-software">        <title>Easy to Use for Whom: Defining the Customer and User Experience for Enterprise Software</title>        <link>http://www.pragmaticmarketing.com/publications/magazine/5/3/easy-to-use-for-whom-defining-the-customer-and-user-experience-for-enterprise-software</link>        <description>Enterprise software is only easy to use if the customer and user think it is easy to use. By Sean Van Tyne.</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>svantyne</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>pragmatic marketer</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-07-02T16:32:07Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/05/0511jm2">        <title>Feature Police: Following Through On Requirements</title>        <link>http://www.pragmaticmarketing.com/publications/topics/05/0511jm2</link>        <description>how Product Managers can play a vital role as the Requirements Police, making sure that important requirements are not forgotten.
By Jacques Murphy</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-15T19:35:03Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/05/0501jm2">        <title>Getting Your Priorities Straight: A Twisted Path</title>        <link>http://www.pragmaticmarketing.com/publications/topics/05/0501jm2</link>        <description>A major challenge that faces every software product is determining the priority of the oh- so-many suggestions that come to Product Management as requirements for the next release. By Jacques Murphy </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-15T19:37:57Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/01/0109sj">        <title>He Who Owns The Compiler Wins</title>        <link>http://www.pragmaticmarketing.com/publications/topics/01/0109sj</link>        <description>In my seminars I often quote my rule that "he who owns the compiler wins." It's a reminder that product managers lack the political power to make developers do anything. Instead product management must persuade developers to build what the market will buy. By Steve Johnson</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>sjohnson</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-10T17:01:19Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/04/0403jm_b">        <title>How Product Managers Help Development?</title>        <link>http://www.pragmaticmarketing.com/publications/topics/04/0403jm_b</link>        <description>Product Managers are in the unique position of having dual citizenship, with passports for both Marketing land and Development land.  By Jacques Murphy </description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>product management</dc:subject>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-15T19:45:13Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/magazine/4/1/managing-product-requirements">        <title>Managing Product Requirements: Where Did All My Customer Insights Go?</title>        <link>http://www.pragmaticmarketing.com/publications/magazine/4/1/managing-product-requirements</link>        <description>How does Requirements Management not only help your company deliver more customer-driven products but how does it help you personally work more efficiently. By Ted Hartnell.
</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>thartnell</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>pragmatic marketer</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-10T18:09:36Z</dc:date>        <dc:type>Page</dc:type>    </item>
    <item rdf:about="http://www.pragmaticmarketing.com/publications/topics/05/0506jm1">        <title>Meeting Promised Development Dates</title>        <link>http://www.pragmaticmarketing.com/publications/topics/05/0506jm1</link>        <description>How to commit to specific product release dates and meet them. By Jacques Murphy</description>        <dc:publisher>No publisher</dc:publisher>        <dc:creator>jlouie</dc:creator>        <dc:rights></dc:rights>                    <dc:subject>working with development</dc:subject>                    <dc:subject>requirements</dc:subject>                <dc:date>2007-08-15T20:03:56Z</dc:date>        <dc:type>Page</dc:type>    </item>




</rdf:RDF>
