<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Growing the pool of speakers</title>
	<atom:link href="http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/</link>
	<description>SQL Server, PASS, and other data mishaps</description>
	<lastBuildDate>Sun, 21 Apr 2013 07:15:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Allen Kinsel</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-132</link>
		<dc:creator>Allen Kinsel</dc:creator>
		<pubDate>Fri, 26 Mar 2010 07:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-132</guid>
		<description>sounds like a great idea but, Im not sure how this would work logistically, especially since we cant expect all experienced speakers to be willing mentors to others they may or may not know.</description>
		<content:encoded><![CDATA[<p>sounds like a great idea but, Im not sure how this would work logistically, especially since we cant expect all experienced speakers to be willing mentors to others they may or may not know.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Todd McDermid</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-125</link>
		<dc:creator>Todd McDermid</dc:creator>
		<pubDate>Wed, 17 Mar 2010 22:44:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-125</guid>
		<description>How about this... if you have a repeat speaker whom you&#039;d like to present two or three of their submitted sessions, and there&#039;s a new speaker that has submitted a similar session that meets general quality criteria - how about asking the existing speaker to mentor the new one?</description>
		<content:encoded><![CDATA[<p>How about this&#8230; if you have a repeat speaker whom you&#8217;d like to present two or three of their submitted sessions, and there&#8217;s a new speaker that has submitted a similar session that meets general quality criteria &#8211; how about asking the existing speaker to mentor the new one?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Humphrey</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-121</link>
		<dc:creator>Eric Humphrey</dc:creator>
		<pubDate>Fri, 12 Mar 2010 16:28:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-121</guid>
		<description>How about encouraging new speakers? &lt;a href=&quot;http://lotsahelp.blogspot.com/2010/03/growing-pass-summit-speaker-pool.html&quot; rel=&quot;nofollow&quot;&gt;Encouragement vs. Discouragement.&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>How about encouraging new speakers? <a href="http://lotsahelp.blogspot.com/2010/03/growing-pass-summit-speaker-pool.html" rel="nofollow">Encouragement vs. Discouragement.</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How can we grow the pool of Summit speakers? &#124; Jeremiah Peschka, SQL Server Developer</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-120</link>
		<dc:creator>How can we grow the pool of Summit speakers? &#124; Jeremiah Peschka, SQL Server Developer</dc:creator>
		<pubDate>Fri, 12 Mar 2010 16:05:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-120</guid>
		<description>[...]  Allen Kinsel, my brother in arms for the Summit 2010 Program, posed a question about how to grow the pool of speakers for the PASS 2010 Summit. Allen has proposed that in order to bring in more speakers, we limit things to 1 session per [...]</description>
		<content:encoded><![CDATA[<p>[...]  Allen Kinsel, my brother in arms for the Summit 2010 Program, posed a question about how to grow the pool of speakers for the PASS 2010 Summit. Allen has proposed that in order to bring in more speakers, we limit things to 1 session per [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Corbett</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-119</link>
		<dc:creator>Jack Corbett</dc:creator>
		<pubDate>Fri, 12 Mar 2010 15:34:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-119</guid>
		<description>I like the fact that pre/post con speakers do a spotlight and think that should continue.

I don&#039;t know that I think it should be a hard and fast rule to limit a speaker to 1 session.  I think that it should be more of &quot;soft&quot; rule for the abstract selection teams to choose a new session by a &quot;new&quot; speaker over an existing speaker if they evaluate closely.  So if speaker A has a session already selected and their second session rates a 8 out of 10 while speaker B has no sessions selected and their session is a 7 out of 10 then you select speaker B.  If there are no sessions that measure up then I think you need to allow speaker A to speak twice.

Also to throw into the mix, there were over 90 MS sessions in 2009 and at least the ones I went to, could have been done just as well by a community speaker, so limiting MS sessions a bit would open up slots for community people.  That doesn&#039;t mean you eliminate the Buck Woody&#039;s and Bob Ward&#039;s as I know those were great sessions.

Perhaps also factoring in past performance (ratings) would help.  Allow top N from each track to have 2 sessions and everyone else limited to 1 (including MS folks).  

Those are my random thoughts on it.</description>
		<content:encoded><![CDATA[<p>I like the fact that pre/post con speakers do a spotlight and think that should continue.</p>
<p>I don&#8217;t know that I think it should be a hard and fast rule to limit a speaker to 1 session.  I think that it should be more of &#8220;soft&#8221; rule for the abstract selection teams to choose a new session by a &#8220;new&#8221; speaker over an existing speaker if they evaluate closely.  So if speaker A has a session already selected and their second session rates a 8 out of 10 while speaker B has no sessions selected and their session is a 7 out of 10 then you select speaker B.  If there are no sessions that measure up then I think you need to allow speaker A to speak twice.</p>
<p>Also to throw into the mix, there were over 90 MS sessions in 2009 and at least the ones I went to, could have been done just as well by a community speaker, so limiting MS sessions a bit would open up slots for community people.  That doesn&#8217;t mean you eliminate the Buck Woody&#8217;s and Bob Ward&#8217;s as I know those were great sessions.</p>
<p>Perhaps also factoring in past performance (ratings) would help.  Allow top N from each track to have 2 sessions and everyone else limited to 1 (including MS folks).  </p>
<p>Those are my random thoughts on it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allen Kinsel</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-118</link>
		<dc:creator>Allen Kinsel</dc:creator>
		<pubDate>Fri, 12 Mar 2010 15:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-118</guid>
		<description>You&#039;re correct the number could be different in many cases, I was looking for a maximum impact based on last years numbers as a way to quantify the potential expense.</description>
		<content:encoded><![CDATA[<p>You&#8217;re correct the number could be different in many cases, I was looking for a maximum impact based on last years numbers as a way to quantify the potential expense.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steve Jones</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-117</link>
		<dc:creator>Steve Jones</dc:creator>
		<pubDate>Fri, 12 Mar 2010 15:29:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-117</guid>
		<description>I&#039;d like to see new speakers, but not sure I want to limit it to 1. Maybe limit the number of consecutive years, set a percentage of new speakers, set some requirements for speakers as well (delivered the presentation twice already to UGs/SQLSaturday, etc).</description>
		<content:encoded><![CDATA[<p>I&#8217;d like to see new speakers, but not sure I want to limit it to 1. Maybe limit the number of consecutive years, set a percentage of new speakers, set some requirements for speakers as well (delivered the presentation twice already to UGs/SQLSaturday, etc).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Ford</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-116</link>
		<dc:creator>Tim Ford</dc:creator>
		<pubDate>Fri, 12 Mar 2010 15:06:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-116</guid>
		<description>Keep in mind that you may not end up with 20 additional comps as some of these will likely overlap with comps awarded to volunteers in other areas.  Perhaps you&#039;re only looking at 10-15 additional.  You also will need to make allowances for adding an additional session for a presenter if there is no coverage for a specific topic that requires it.

I will comment on Andy&#039;s suggestion in my blog since I&#039;m responsible for Spotlights, Pre-Cons, and that selection process.</description>
		<content:encoded><![CDATA[<p>Keep in mind that you may not end up with 20 additional comps as some of these will likely overlap with comps awarded to volunteers in other areas.  Perhaps you&#8217;re only looking at 10-15 additional.  You also will need to make allowances for adding an additional session for a presenter if there is no coverage for a specific topic that requires it.</p>
<p>I will comment on Andy&#8217;s suggestion in my blog since I&#8217;m responsible for Spotlights, Pre-Cons, and that selection process.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Warren</title>
		<link>http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/comment-page-1/#comment-115</link>
		<dc:creator>Andy Warren</dc:creator>
		<pubDate>Fri, 12 Mar 2010 14:47:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.allenkinsel.com/archive/2010/03/growing-the-pool-of-speakers/#comment-115</guid>
		<description>Allen, I think the additional cost is well worth the value to the event and to the community. I like that you&#039;re looking at the potential downside, and from the outside it seems like it shouldn&#039;t end up being a big concern, but still good to leave yourself some room to manuever the first time you implement this.

I wonder if you could write more about the spotlight sessions and the overall process of reviewing and selecting sessions?</description>
		<content:encoded><![CDATA[<p>Allen, I think the additional cost is well worth the value to the event and to the community. I like that you&#8217;re looking at the potential downside, and from the outside it seems like it shouldn&#8217;t end up being a big concern, but still good to leave yourself some room to manuever the first time you implement this.</p>
<p>I wonder if you could write more about the spotlight sessions and the overall process of reviewing and selecting sessions?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
