<?xml version="1.0"?>
<rss version="2.0">
   <channel>
      <title>Ruan Discovery &amp; Solutioning Retro by Rachael Dacey</title>
      <link>https://padlet.com/rachdacey/x01oo3can9j809vq</link>
      <description>Share honest, respectful &amp; productive feedback to help us improve process &amp; practices as a team</description>
      <language>en-us</language>
      <pubDate>2021-08-26 14:34:07 UTC</pubDate>
      <lastBuildDate>2026-02-16 19:23:24 UTC</lastBuildDate>
      <webMaster>hello@padlet.com</webMaster>
      <image>
         <url></url>
      </image>
      <item>
         <title>Organized</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705359079</link>
         <description><![CDATA[<div>I think for Ruan we explored, vetted and proved SmartSheets and the shared discipline it provides kept all in sync. </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 20:56:19 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705359079</guid>
      </item>
      <item>
         <title>Never lose site of Customer</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705361725</link>
         <description><![CDATA[<div>Ruan gave us the true Legacy Waterfall/IT PMO efforts and drove so the waterfalls. At one point I felt like they spoke over the real customer - Brokerage for phase one - the user of MM. Getting that user the opportunity to ask for the Moon and delivering it is what we need to aim for each new Tenant.&nbsp;<br><br></div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 20:58:31 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705361725</guid>
      </item>
      <item>
         <title>Team approach</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705414256</link>
         <description><![CDATA[<div>We have had duties and roles which helps ownership </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 21:49:50 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705414256</guid>
      </item>
      <item>
         <title>Discovery Discussion Seq &amp; Priority</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705420730</link>
         <description><![CDATA[<div>With so much to cover during discovery I think there might be an opportunity to tackle certain discovery conversations &amp; topics ahead of others.<br><br>Some discovery asks, questions and needs seem to be required earlier than expected also, but this may be a by product of having an evolving product that requires a lot of engineering team work / support for build tasks that should / could have a UI to manage. </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 21:57:19 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705420730</guid>
      </item>
      <item>
         <title>Meeting Product Needs - Informational?</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705422577</link>
         <description><![CDATA[<div>Navigating first time around discovery &amp; solutioning it was not super clear if there was information Product was missing from team.&nbsp;<br><br>Would like to review existing templates &amp; modify / add if these templates are not structured to support hand-offs between teams </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 21:59:23 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705422577</guid>
      </item>
      <item>
         <title>Discovery INP + Product Planning </title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705426155</link>
         <description><![CDATA[<div>For Ruan we made the decision (despite knowing there would be open discovery in progress) to try and submit as many knowns as we could to hit August Product planning.&nbsp;<br><br>Is this approach ideal? Or is it preference of Product to wait until we have completed discovery before moving into product planning phase.<br><br>It was not clear to us when the next round of planning would be and we did not want to 'miss the boat' we are also trying to support a more iterative approach, but can stay waterfall if that is what we are positioned to support </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 22:03:26 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705426155</guid>
      </item>
      <item>
         <title>Implementation How To</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705428095</link>
         <description><![CDATA[<div>Not super clear or centralized docs for how to execute system - system integrations or what needs to be gathered up front from customer. An implementation guide is in progress which will be helpful for future but current gap in understanding makes planning for activities challenging</div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-30 22:05:49 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1705428095</guid>
      </item>
      <item>
         <title>Defined Roles/ Open Communication/Team Support</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1707076133</link>
         <description><![CDATA[<div>For most of us, this is our first time going through a full project lifecycle and in our roles. Our team has worked exceptionally well together. We make sure we support one another, ask for help when needed and communicate daily. There is also a clear direction on our roles. </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-31 13:24:47 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1707076133</guid>
      </item>
      <item>
         <title>Internal Processes &amp; Feedback</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1707152671</link>
         <description><![CDATA[<div>Lack of documentation:<br>-Unclear of the requirements that were needed from discovery calls<br>-Customer facing templates such as a systems diagram and an Orderful overview would have been helpful&nbsp;<br><br>Product feedback:<br>-Would have liked to get more feedback from Product on our solutions efforts. The thought was also that we would have more defined dates after roadmap planning. Still feel uneasy about our RM dates and how to message those dates to the customer. </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-31 13:54:10 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1707152671</guid>
      </item>
      <item>
         <title>Internal Timelines</title>
         <author></author>
         <link>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1707388658</link>
         <description><![CDATA[<div>Key takeaway from this project is to have awareness of our internal timelines not just customer timelines. For example, roadmap planning, timeline for test environment setup, timeline for Orderful connectivity, timeline for dev resources, etc. If this is clear to the project team then expectations can be set with our customers from the beginning. </div>]]></description>
         <enclosure url="" />
         <pubDate>2021-08-31 15:24:14 UTC</pubDate>
         <guid>https://padlet.com/rachdacey/x01oo3can9j809vq/wish/1707388658</guid>
      </item>
   </channel>
</rss>
