<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Fred Brunel - Latest Comments in Evidence Based Scheduling</title><link>http://fredbrunel.disqus.com/</link><description></description><language>en</language><lastBuildDate>Thu, 10 Jul 2008 19:35:41 -0000</lastBuildDate><item><title>Re: Evidence Based Scheduling</title><link>http://fredbrunel.com/journal/2008/07/evidence-based-scheduling/#comment-1457148</link><description>&lt;p&gt;I have the exact same situation, multiple projects, dependencies, and people working remotely. It's really not easy to manage.&lt;/p&gt;&lt;br&gt;&lt;p&gt;I'd be glad to hear more about your experience with Scrum in such situation.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fbrunel</dc:creator><pubDate>Thu, 10 Jul 2008 19:35:41 -0000</pubDate></item><item><title>Re: Evidence Based Scheduling</title><link>http://fredbrunel.com/journal/2008/07/evidence-based-scheduling/#comment-1457150</link><description>&lt;p&gt;Just read up on the EBS process and it sounds pretty interesting. On the surface, the process shares many similarities with Scrum. Will look into it some more. &lt;/p&gt;&lt;br&gt;&lt;p&gt;Initially our company had a few issues with Scrum as well. We had a large dev team, some remotely, working on multiple projects which required multiple releases. However we were able to adapt the Scrum philosophy into the way we work, sometimes even breaking down the teams into smaller Scrum groups if necessary.&lt;/p&gt;&lt;br&gt;&lt;p&gt;Thanks for the post. Always an interesting read.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Trevor</dc:creator><pubDate>Thu, 10 Jul 2008 18:56:31 -0000</pubDate></item><item><title>Re: Evidence Based Scheduling</title><link>http://fredbrunel.com/journal/2008/07/evidence-based-scheduling/#comment-1457149</link><description>&lt;p&gt;Hi Trevor,&lt;/p&gt;&lt;br&gt;&lt;p&gt;I'm using Scrum right now in my company. Even if the process is interesting it is not without flaws. Especially when you have lots of people (and teams) to synchronize for releases.&lt;/p&gt;&lt;br&gt;&lt;p&gt;Joel don't use Scrum.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">fbrunel</dc:creator><pubDate>Thu, 10 Jul 2008 17:55:55 -0000</pubDate></item><item><title>Re: Evidence Based Scheduling</title><link>http://fredbrunel.com/journal/2008/07/evidence-based-scheduling/#comment-1457151</link><description>&lt;p&gt;I completely agree, which is why I'm a huge proponent of Scrum / Agile Development.&lt;/p&gt;&lt;br&gt;&lt;p&gt;More here:&lt;/p&gt;&lt;br&gt;&lt;p&gt;http://en.wikipedia.org/wiki/Scrum_(development)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Trevor</dc:creator><pubDate>Thu, 10 Jul 2008 17:51:17 -0000</pubDate></item></channel></rss>