<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/171/all" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:og="http://ogp.me/ns#" xmlns:article="http://ogp.me/ns/article#" xmlns:book="http://ogp.me/ns/book#" xmlns:profile="http://ogp.me/ns/profile#" xmlns:video="http://ogp.me/ns/video#" xmlns:product="http://ogp.me/ns/product#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
  <channel>
    <title>Product Owner</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/171/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/171/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Getting Your Priorities in Order: An Agile Product Owner Overview</title>
    <link>https://swsblog.stanford.edu/blog/getting-your-priorities-order-agile-product-owner-overview</link>
    <description>&lt;div class=&quot;field field-name-body field-type-text-with-summary field-label-hidden&quot;&gt;&lt;div class=&quot;field-items&quot;&gt;&lt;div class=&quot;field-item even&quot; property=&quot;content:encoded&quot;&gt;&lt;p&gt;Last December, my coworker Zach Chandler wrote a great &lt;a href=&quot;/blog/agile-developer-waterfall-client&quot;&gt;blog post on the core principles of Agile Project Management&lt;/a&gt; and how to think about them in relation to web development at Stanford. In Zach&#039;s &quot;Be Careful What You Ask For&quot; section he briefly outlines the challenges for the Product Owner (primary decision maker) in Agile projects: balancing the power to change project direction with budget and time constraints. In this post, I&#039;d like to go into the role of the Product Owner in a bit more depth.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 17 Jun 2013 16:00:12 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">189 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
