<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/349/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</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/349/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/349/all/feed" rel="self" type="application/rss+xml" />
      <item>
    <title>Investing in the Future: How our team takes the time to innovate for campus</title>
    <link>https://swsblog.stanford.edu/blog/investing-future-how-our-team-takes-time-innovate-campus</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;One of the challenges we at Stanford Web Services face as both a software development group as well as a client-facing web design team is finding time to create new and innovative tools for campus amidst client projects. Most of the time we are heads down, working with clients to launch scores of websites each year. So how do we approach innovating for campus?&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Fri, 07 Oct 2016 18:45:16 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">684 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Transparency in Product Development</title>
    <link>https://swsblog.stanford.edu/blog/transparency-product-development</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;div&gt; &lt;/div&gt;
&lt;p class=&quot;summary&quot;&gt;&lt;span&gt;While Stanford Web Services can be seen as a service provider, often involved with custom projects and closely working with clients, one of our core offerings is also our Jumpstart product. With any product offering company, as adoption and usage of the products grow, more and more customers give feedback and express interest in the future direction of the product. Lately, our group has been contemplating increasing transparency in our product development roadmap, and to what extent.&lt;/span&gt;&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Thu, 29 Oct 2015 21:05:07 +0000</pubDate>
 <dc:creator>Jamie C. Tsui</dc:creator>
 <guid isPermaLink="false">579 at https://swsblog.stanford.edu</guid>
  </item>
  </channel>
</rss>
