Comments on: 11 Signs That Your Project Will Fail - Part I http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i Thu, 17 May 2012 02:30:00 +0000 http://wordpress.org/?v=abc hourly 1 By: 11 Signs That Your Project Will Fail - Part II - PM Hut http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i/comment-page-1#comment-1174 11 Signs That Your Project Will Fail - Part II - PM Hut Mon, 23 Mar 2009 04:47:25 +0000 http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i#comment-1174 [...] 11 Signs That Your Project Will Fail - Part II [...] [...] 11 Signs That Your Project Will Fail - Part II [...]

]]> By: Satya http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i/comment-page-1#comment-1173 Satya Fri, 20 Mar 2009 12:13:35 +0000 http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i#comment-1173 Thanks Eoin for your comments. As Larry Elision of Oracle recently put it - the "yo-yo" years of IT is coming to an end. The actual boom happened during the internet birth, when anyone who could spell Java or C++ or C, with some experiences from any industry got into management roles. May be the next phase will see techno managers with solid managerial as well as technical capability - after the recession. Thanks Eoin for your comments.

As Larry Elision of Oracle recently put it - the “yo-yo” years of IT is coming to an end. The actual boom happened during the internet birth, when anyone who could spell Java or C++ or C, with some experiences from any industry got into management roles.

May be the next phase will see techno managers with solid managerial as well as technical capability - after the recession.

]]> By: Eoin Redmond http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i/comment-page-1#comment-1172 Eoin Redmond Thu, 19 Mar 2009 11:08:08 +0000 http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i#comment-1172 Hey Satya. As an SME and Tech Lead, I think you have hit the nail on the head with your point on "Over-Allocated Key Team Members". This unfortunately is often combined with the problem of "Inexperienced Project Managers". I see this on a daily basis whereby the PM is out of their depth and they end up putting all the pressure on the Tech Lead to make up for their lack of knowledge or leadership. Eventually the Tech Lead drowns in documentation and issues that a decent PM would never allow happen. Come deployment/launch date, if your Tech Lead is not extremely pedantic and anal, then there are going to be production issues. Looking forward to the next article… Hey Satya. As an SME and Tech Lead, I think you have hit the nail on the head with your point on “Over-Allocated Key Team Members”. This unfortunately is often combined with the problem of “Inexperienced Project Managers”.

I see this on a daily basis whereby the PM is out of their depth and they end up putting all the pressure on the Tech Lead to make up for their lack of knowledge or leadership.

Eventually the Tech Lead drowns in documentation and issues that a decent PM would never allow happen. Come deployment/launch date, if your Tech Lead is not extremely pedantic and anal, then there are going to be production issues.

Looking forward to the next article…

]]> By: Satya http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i/comment-page-1#comment-1170 Satya Mon, 16 Mar 2009 16:15:35 +0000 http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i#comment-1170 Thanks Jeffrey. I could not agree more coming from a technical background, I know how painful it is for the team of developers when the project goes away by mismanagement. The pain, agony or the ecstasy and pleasure of a developer in bringing a product to life can only be shared by someone who has gone through the same highs and lows. Here is one from Joel, an Ex-Program Manager at Microsoft: http://www.joelonsoftware.com/items/2009/03/09.html "It helps, as a program manager, to be pretty good at coding yourself. This is unfair. Program managers aren’t supposed to write code. But programmers tend to respect programmers a lot more than non-programmers, no matter how smart they are. It is possible to be an effective program manager without being a coder, but the burden of earning the respect of the programming team will be higher." But, in the real world, we see a lot of people in management role, who have no idea on how technology works. I do not expect them to code, but they even do not know the ecosystem they live in! And they go with the principle - "Either my way or the highway!" Some even worse - follow the Caligula Principle - "They can hate me as long as they fear me" (after all they are the managers even though they do not know the technology!) Thanks Jeffrey. I could not agree more coming from a technical background, I know how painful it is for the team of developers when the project goes away by mismanagement.

The pain, agony or the ecstasy and pleasure of a developer in bringing a product to life can only be shared by someone who has gone through the same highs and lows. Here is one from Joel, an Ex-Program Manager at Microsoft: http://www.joelonsoftware.com/items/2009/03/09.html

“It helps, as a program manager, to be pretty good at coding yourself. This is unfair. Program managers aren’t supposed to write code. But programmers tend to respect programmers a lot more than non-programmers, no matter how smart they are. It is possible to be an effective program manager without being a coder, but the burden of earning the respect of the programming team will be higher.”

But, in the real world, we see a lot of people in management role, who have no idea on how technology works. I do not expect them to code, but they even do not know the ecosystem they live in! And they go with the principle - “Either my way or the highway!” Some even worse - follow the Caligula Principle - “They can hate me as long as they fear me” (after all they are the managers even though they do not know the technology!)

]]> By: Jeffrey http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i/comment-page-1#comment-1171 Jeffrey Mon, 16 Mar 2009 13:15:07 +0000 http://www.pmhut.com/11-signs-that-your-project-will-fail-part-i#comment-1171 Great post. The one I see most often is, "Over-Allocated Key Team Members" with "Lack of Senior Management Involvement"; though I would call it lack of business sponsorship. I have observed many projects being run completely by the technology team only to fail to deliver what the business wanted, but then again they never spent any time after making the request. Look forward to the next six. Great post. The one I see most often is, “Over-Allocated Key Team Members” with “Lack of Senior Management Involvement”; though I would call it lack of business sponsorship. I have observed many projects being run completely by the technology team only to fail to deliver what the business wanted, but then again they never spent any time after making the request.

Look forward to the next six.

]]>