<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Module 3 Discussion by Sheppard Sternthal</title>
      <link>https://padlet.com/sstern04/s11gz5kr3rqz</link>
      <description>Please click on the + sign at the bottom right hand side of the screen to post your discussion questions, comment on posts, or post some of your own research.</description>
      <language>en-us</language>
      <pubDate>2017-11-06 17:41:45 UTC</pubDate>
      <lastBuildDate>2017-11-12 10:36:21 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Considering the scope of risk management for an organization, what are the measures you would take to avoid scope creep?</title>
         <author>sstern04</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204017148</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-11-06 17:44:11 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204017148</guid>
      </item>
      <item>
         <title>Is Scope Creep really a thing with this sort of project? If your answer is Yes, comment below:</title>
         <author>sstern04</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204017491</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-11-06 17:44:45 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204017491</guid>
      </item>
      <item>
         <title>Interesting take - what do you think?</title>
         <author>sstern04</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204173700</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://www.youtube.com/watch?v=o2PXF-Q_3MQ&amp;t=283s" />
         <pubDate>2017-11-07 01:09:37 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204173700</guid>
      </item>
      <item>
         <title>Mitigating Risk</title>
         <author>sstern04</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204177546</link>
         <description><![CDATA[]]></description>
         <enclosure url="https://www.scmagazineuk.com/mitigating-security-risks-in-the-extended-enterprise/article/699000/" />
         <pubDate>2017-11-07 01:31:35 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204177546</guid>
      </item>
      <item>
         <title>Is Scope Creep really a thing with this sort of project? If your answer is No, comment below:</title>
         <author>sstern04</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204665772</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-11-08 03:53:32 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204665772</guid>
      </item>
      <item>
         <title>Todd DeBruyne: Considering the scope of risk management for an organization, what are the measures you would take to avoid scope creep? First and foremost, there should a project plan or project agreement this way there is an understanding of the beginning and ending result of your project and make sure all involved have a good understanding also. Next, make a list of things such as budget, deadline, delivery, and satisfaction of customer. Use this list as a reference to choose decisions on scheduling when your project begins. Break your project into minor and major milestones doing this will help pace your project and help you determine how the project is coming along. This way if you know you are beginning to run behind schedule you will be able to adjust accordingly. Once the schedule is developed assign duties and resources and determine which parts of the project should be set for completion first and always add additional time for any upgrades and changes that may need to be made in the event you project is lengthy. And always anticipate the arise of scope creep and keep communication with customer open so they are always fully aware of problems or changes that may need to be approved.</title>
         <author></author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204958006</link>
         <description><![CDATA[]]></description>
         <enclosure url="" />
         <pubDate>2017-11-08 17:55:30 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/204958006</guid>
      </item>
      <item>
         <title></title>
         <author></author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/205121023</link>
         <description><![CDATA[<div>Scott Baigrie: Scope creep refers to a project that has seen its original goals expand while it's in progress. As the term suggests, scope creep is a subtle process that starts with small adjustments and ends up resulting in projects that take far longer to complete or even fail before they are finished. Even if the project is completed, scope creep can result in final deliverables that look nothing like what was originally envisioned.<br><br></div><div> </div><div>Scope creep can occur for a number of reasons, including:<br><br></div><div>A poor understanding of the original project<br><br></div><div>Changing market conditions<br><br></div><div> </div><div>A few things that can be done to help eliminate creep are:<br><br></div><div>Have a detailed understanding of the project requirements<br><br></div><div>Break the project down into major and minor milestones and create a schedule<br><br></div><div>Once the schedule has been created, assign resources and determine the critical path.<br><br></div><div>Expect that there will be scope creep from unforeseen circumstances and Include a process for changing the scope<br><br>on a side note I don't like this new discussion board format.</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-11-09 03:05:51 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/205121023</guid>
      </item>
      <item>
         <title>Managing Scope</title>
         <author>mraird01</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/205122402</link>
         <description><![CDATA[<div>Micah Rairdon: Managing scope is important for anyone who really wants to get work done. I personally struggle quite a bit with scope creep at my work place right now. There are too many people who would like me to take on tasks and not enough time to say yes to all of them. I need to learn how to say no to some of them.<br><br>When you are considering the scope of risk management, I think mitigation of scope creep should be similar to managing scope creep in any other situation. The best thing that you can do is correctly gather requirements from your customer and then come to an agreement with that customer on the fact that those are going to be the requirements from your position. If they need you to do something else for them they are going to have to revisit their initial requirements that you agreed on and either hire more staff (internal position) or raise the amount of money they are paying you (if this is a contracted position)</div>]]></description>
         <enclosure url="" />
         <pubDate>2017-11-09 03:16:37 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/205122402</guid>
      </item>
      <item>
         <title>New DQ Format</title>
         <author>sstern04</author>
         <link>https://padlet.com/sstern04/s11gz5kr3rqz/wish/205319495</link>
         <description><![CDATA[<div>Scott has given his feedback on this DQ format - What does everyone else think?<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2017-11-09 15:27:21 UTC</pubDate>
         <guid>https://padlet.com/sstern04/s11gz5kr3rqz/wish/205319495</guid>
      </item>
   </channel>
</rss>
