<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.11.81 (http://www.squarespace.com/) on Sun, 27 May 2012 08:28:04 GMT--><?xml-stylesheet type="text/css" href="/universal/styles/feed.css"?><rss version="2.0"><channel><title>Elastic Team Leadership in Software - Comments</title><link>http://5whys.com/blog/</link><description></description><copyright></copyright><language>en-US</language><generator>Squarespace Site Server v5.11.81 (http://www.squarespace.com/)</generator><item><title>Robert Simmons comments on Three reasons not to have your own private office</title><author>Robert Simmons</author><pubDate>Mon, 03 Oct 2011 11:58:18 +0000</pubDate><link>http://5whys.com/blog/three-reasons-not-to-have-your-own-private-office.html#comments</link><guid isPermaLink="false">422423:4655536:comment/15221830</guid><description><![CDATA[<p>There is one negative to consider - the team may feel uncomfortable with their &quot;boss&quot; right next to them all the time. It can keep a team from feeling like they can relax and be themselves. Any suggestions on handling that aspect? Over time, you&#39;d hope the uneasiness would go away, but that doesn&#39;t mean it would.</p>]]></description></item><item><title>Ryan Cromwell comments on Video: Mistake #1 - Not Understanding Team Maturity</title><author>Ryan Cromwell</author><pubDate>Fri, 29 Jul 2011 03:17:22 +0000</pubDate><link>http://5whys.com/blog/video-mistake-1-not-understanding-team-maturity.html#comments</link><guid isPermaLink="false">422423:4655536:comment/14293702</guid><description><![CDATA[<p>What are your thoughts on Tuckman&#39;s stages of group development?  http://en.wikipedia.org/wiki/Forming-storming-norming-performing.</p>]]></description></item><item><title>Nikola Stjelja comments on Yelling at team members</title><author>Nikola Stjelja</author><pubDate>Thu, 14 Jul 2011 13:13:31 +0000</pubDate><link>http://5whys.com/blog/yelling-at-team-members.html#comments</link><guid isPermaLink="false">422423:4655536:comment/13794846</guid><description><![CDATA[<p>I really got frustrated and nervous by my team behavior some time. I took me some time to adjust my self to the situation. Two things helped:<br/>- my manager did some coaching with me<br/>- I started learning more about human psychology<br/>- I started practicing Jeet Kune Do and Eskrima</p><p>The result was I learned to accept that my team is who they are and that they are not doing the things they do from malice and that good and open communication and time can solve and fix most problems.<br/>If someone is deliberately malicious or just won&#39;t apply after several concrete feedback well that why we have project managers.<br/>Martial arts are a really good stress relief. For the last six months I&#39;ve been the calmest since ever. It really allowed me to change and grow in a better technical lead.<br/>Of course there is the added benefit of all those good looks I receive since I&#39;ve buffed up my physical exercise regime.</p>]]></description></item><item><title>Robert Schultz comments on Burst your team's bubble - stop protecting them from the surrounding organization</title><author>Robert Schultz</author><pubDate>Mon, 20 Jun 2011 18:21:51 +0000</pubDate><link>http://5whys.com/blog/burst-your-teams-bubble-stop-protecting-them-from-the-surrou.html#comments</link><guid isPermaLink="false">422423:4655536:comment/13353217</guid><description><![CDATA[<p>As a coder, the #1 thing I&#39;ve learned is that when sales folks, marketing or management bring &#39;demands&#39; to you, don&#39;t just say &quot;Ok&quot;.<br/>Instead, figure out WHY they want that and work with them at coming up with a much better, more elegant solution.<br/>Don&#39;t even think about how to code it, or how it&#39;s system architecture will be. Just think &#39;perfect world&#39;, in the end, how would this be. You can figure out how to make it a reality later, as that&#39;s just a technical challenge.</p><p>Roy, it seems like your advice is geared towards &#39;newbie&#39; developer teams. Those fresh out of college or those who don&#39;t have much experience. Experienced coders may view your advice as patronizing,  as coming from a superiority complex mindset.</p>]]></description></item><item><title>Agile Scout comments on A good leader won't need to ask</title><author>Agile Scout</author><pubDate>Tue, 07 Jun 2011 15:25:45 +0000</pubDate><link>http://5whys.com/blog/a-good-leader-wont-need-to-ask.html#comments</link><guid isPermaLink="false">422423:4655536:comment/13188368</guid><description><![CDATA[<p>Well said. I like this quick introspection</p>]]></description></item><item><title>Gaurav Arora comments on What to do if some people in the team just don't want to take a task?</title><author>Gaurav Arora</author><pubDate>Tue, 07 Jun 2011 09:37:23 +0000</pubDate><link>http://5whys.com/blog/what-to-do-if-some-people-in-the-team-just-dont-want-to-take.html#comments</link><guid isPermaLink="false">422423:4655536:comment/13187092</guid><description><![CDATA[<p>Roy - Its really a nice to see answers for my queries. Recently I faced the same problem. I already started to follow your said words and I hope for the best.</p>]]></description></item><item><title>Roy Osherove comments on Slides: Team Leadership In the Age of Agile</title><author>Roy Osherove</author><pubDate>Thu, 28 Apr 2011 22:10:18 +0000</pubDate><link>http://5whys.com/blog/slides-team-leadership-in-the-age-of-agile.html#comments</link><guid isPermaLink="false">422423:4655536:comment/12731089</guid><description><![CDATA[<p>I hope that QCon will release this talk&#39;s video soon. I&#39;ll post here when it is released.</p>]]></description></item><item><title>Nabeel comments on Slides: Team Leadership In the Age of Agile</title><author>Nabeel</author><pubDate>Wed, 20 Apr 2011 00:13:20 +0000</pubDate><link>http://5whys.com/blog/slides-team-leadership-in-the-age-of-agile.html#comments</link><guid isPermaLink="false">422423:4655536:comment/12662315</guid><description><![CDATA[<p>Hi Roy. Do you have this talk available as a video or podcast anywhere on the web ?</p>]]></description></item><item><title>Roy Osherove comments on 12 Behavior Anti Patterns You Will Face As a Software Team Leader</title><author>Roy Osherove</author><pubDate>Thu, 14 Apr 2011 08:41:56 +0000</pubDate><link>http://5whys.com/blog/12-behavior-anti-patterns-you-will-face-as-a-software-team-l.html#comments</link><guid isPermaLink="false">422423:4655536:comment/12611678</guid><description><![CDATA[<p>the team lead responses are a way to deal with those behaviors, during chaotic team phases.<br/>if the team is in a learning phase, than you could say that the dev lead&#39;s responses are indeed anti patterns, because they do not fit the current team phase-context.</p>]]></description></item><item><title>cthibaut@octo.com comments on 12 Behavior Anti Patterns You Will Face As a Software Team Leader</title><author>cthibaut@octo.com</author><pubDate>Wed, 13 Apr 2011 07:39:05 +0000</pubDate><link>http://5whys.com/blog/12-behavior-anti-patterns-you-will-face-as-a-software-team-l.html#comments</link><guid isPermaLink="false">422423:4655536:comment/12580660</guid><description><![CDATA[<p>I assume that the situations AND the responses are part of the antipatterns, am I right ?</p>]]></description></item></channel></rss>
