<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Digital.gov</title>
    <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/kate-garklavs/</link>
    <description>Recent content on Digital.gov</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <atom:link href="/preview/gsa/digitalgov.gov/bc-archive-content-3/authors/kate-garklavs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Taking an Agile Approach to Content</title>
      <link>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/06/10/taking-an-agile-approach-to-content/</link>
      <pubDate>Fri, 10 Jun 2016 02:00:28 -0400</pubDate>
      <guid>/preview/gsa/digitalgov.gov/bc-archive-content-3/2016/06/10/taking-an-agile-approach-to-content/</guid>
      <description>So, you’ve recently joined an agile team — congratulations! Here at 18F, we work in an agile way — in other words, we base our designs on user needs, conduct usability testing, iterate quickly, and release MVPs (minimum viable products) rather than highly finalized releases. We take an agile approach to content too. While there’s</description>
    </item>
  </channel>
</rss>
