<?xml version="1.0" encoding="utf-8" ?><rss version="2.0" xml:base="https://swsblog.stanford.edu/taxonomy/term/173/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>Scrum</title>
    <link>https://swsblog.stanford.edu/taxonomy/term/173/all</link>
    <description></description>
    <language>en</language>
     <atom:link href="https://swsblog.stanford.edu/taxonomy/term/173/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>Agile Project Management and its flavors: where does Scrum end and Kanban begin?</title>
    <link>https://swsblog.stanford.edu/blog/agile-project-management-and-its-flavors-where-does-scrum-end-and-kanban-begin</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;Agile has become a big buzz word recently in the project management world. In this post, I&#039;ll try to clarify where some of the lines are being blurred between terms like Agile and Scrum, and what some of these terms actually mean.&lt;/p&gt;
&lt;p&gt;Keep in mind while reading this that I am primarly trained in Scrum, so my descriptions of other Agile methodologies are only decently informed. :)&lt;/p&gt;
&lt;h2&gt;What is Agile Project Management?&lt;/h2&gt;
&lt;p&gt;From the ever-present wikipedia:&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Wed, 30 Jul 2014 20:18:09 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">419 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Scrum Resources: Learn about Agile Project Management</title>
    <link>https://swsblog.stanford.edu/blog/scrum-resources-learn-about-agile-project-management</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;Welcome back! We&#039;re kicking off the new year with a post on Agile Project Management. I&#039;ve been speaking a lot to folks recently about Scrum and how to think about incorporating it into your team structure.&lt;/p&gt;
&lt;p&gt;One form of Agile project management, Scrum is an iterative development process that focuses the development team on the highest priority work and increases the product/project manager&#039;s ability to forecast timelines and delivery. For Web Services, it has improved our project estimates and helped us to work in a more focused way on our larger projects.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 07 Jan 2014 16:00:22 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">263 at https://swsblog.stanford.edu</guid>
  </item>
  <item>
    <title>Holding Space: A Scrum Master Overview</title>
    <link>https://swsblog.stanford.edu/blog/holding-space-scrum-master-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 class=&quot;summary&quot;&gt;In June, I wrote &lt;a href=&quot;https://swsblog.stanford.edu/blog/getting-your-priorities-order-agile-product-owner-overview&quot; rel=&quot;nofollow&quot;&gt;a post about the role of the Scrum Product Owner&lt;/a&gt; in a website project. For this post, I&#039;ll outline the role of the Scrum Master and how it differs from the Product Owner role.&lt;/p&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
     <pubDate>Tue, 03 Sep 2013 16:23:20 +0000</pubDate>
 <dc:creator>Linnea Ann Williams</dc:creator>
 <guid isPermaLink="false">223 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>
