<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Blog 3 Comments by Samantha Simpson</title>
      <link>https://padlet.com/samantha_simpson1/8pwwrnayvah6</link>
      <description>Made with no regrets, whatsoever</description>
      <language>en-us</language>
      <pubDate>2018-09-20 16:50:38 UTC</pubDate>
      <lastBuildDate>2018-10-29 01:47:26 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Mike Wood - Useful plans? </title>
         <author>mwood51</author>
         <link>https://padlet.com/samantha_simpson1/8pwwrnayvah6/wish/297844032</link>
         <description><![CDATA[<div>You make a good point regarding the timeliness of a technology plan. I think instead of trying to make something yearly to keep up with technology updates and changes, such a task should be incorporated into a master plan.  Consider the design process:  identify a need, create something to address the need, test it out, and revise as needed.  An effective technology plan should have this framework as well.  A living document, if you will, that  works as a plan for new technology implementation.  <br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2018-10-29 01:34:44 UTC</pubDate>
         <guid>https://padlet.com/samantha_simpson1/8pwwrnayvah6/wish/297844032</guid>
      </item>
   </channel>
</rss>
