<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/175/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>project management</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/175/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/175/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Improving your business operations with a CRM</title>
    <link>https://swsblog.stanford.edu/blog/improving-your-business-operations-crm</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 class=&quot;summary&quot;&gt;&lt;span&gt;&lt;span&gt;Stanford Web Services serves a diverse set of clients throughout Stanford University, ranging as large as schools to as small as individual labs. With over 200 active or completed website projects, and an average of 18 new project inquiries per month, we needed to implement a Customer Relationship Management system to track all of our operational data and communications. &lt;/span&gt;&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 12 Feb 2016 20:25:18 +0000</pubDate>
 <dc:creator>Jamie C. Tsui</dc:creator>
 <guid isPermaLink="false">629 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Saying Yes, Saying No: A Designer’s Balancing Act</title>
    <link>https://swsblog.stanford.edu/blog/saying-yes-saying-no-designers-balancing-act</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 class=&quot;summary&quot;&gt;As designers, in order to come up with innovative solutions, we must embrace a “yes, and” mindset. But to really get the job done, our most important weapon is the ability to say “no.” To be successful, we have to constantly find a balance between a mindset of “yes” and a mindset of “no.”&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 23 Apr 2015 16:00:00 +0000</pubDate>
 <dc:creator>Megan Erin Miller</dc:creator>
 <guid isPermaLink="false">565 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Choosing your project&#039;s internal web team</title>
    <link>https://swsblog.stanford.edu/blog/choosing-your-projects-internal-web-team</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 class=&quot;summary&quot;&gt;Imagine you&#039;re an academic department or program and you&#039;re starting on a project to revamp your web presence. The first thing you&#039;ll need to do is figure out who should be on your internal web team that will see the project from inception to launch. This might be some combination of your staff, faculty, and students. But who exactly?&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Mon, 31 Mar 2014 17:02:11 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">375 at https://swsblog.stanford.edu</guid>
  </item>
  <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>
