|
Project failure is prevalent all projects. Todd's Back From RedTM blog addresses the reasons for project failure along with methods to avert and correct the problems that cause the failure.
|
Sunday, 18 July 2010 17:30
Managing On A Mobius StripThe two most common project attributes that raise the red flag are cost and timeline problems. Both are easily measured and inextricable intertwined. As the timeline extends, there is a commensurate increase in cost; similarly, as cost goes up (usually from increased scope) the timeline increases. However, time is different. Benjamin Franklin said it best, "You may delay, but time will not." Work can stop (controlling the burn rate) extraneous features can be removed (decreasing the required work) but time marches on. We cannot control time. Although intuitively obvious, the concept seems to escape a large number of managers and executives.
|
Sunday, 11 July 2010 21:43
The Revered Decision Maker... Not Really The quickest way to get lost, in business or in your personal life, is failing to make decisions. Not knowing where you are headed increases stress and frustration. It would seem natural, then, that teams on projects beleaguered with indecisive management would be excited to have the logjam broken by a dynamic, decisive leader. Simply put, they are not. Every decision has its opponents and they are bound to be irritated, feeling they have lost prestige or stature. However, turning the decision into action requires a unified team. One of the best tools to accomplish this is to understand what impeded decision making and tactfully educating the team members on the source of the problem. This will garner their backing and improve their willingness to support the decision.
Monday, 05 July 2010 09:28
The CIO's Role in Project Failure A couple months ago I asked the question, "Who should the CIO report to?" on the LinkedIn's CIO Magazine Forum. Surprisingly, over 100 people responded, so many that the group's moderator moved the discussion to the jobs section. Maybe they were tired of the attention this old, beat-up subject was getting. I surely did not think responses would be quite as passionate as they were. However, my interest lay in another area, not in the answers to the direct question, rather the reasoning behind them.
Sunday, 27 June 2010 17:00
Snake Pit... Taking the Poison out of Technical DebtProjects build in technical debt and maintenance groups remove it—if your organization has a maintenance group. Technical debt accrues in any product, whether or not it has a technical component. It is the result of taking shortcuts when building the product. Sometimes it is the result of not having enough time, on other occasions it is due to not having the right tools. Anything from the implementation of the software component to light fixture can have technical debt. Promises are made to correct it later, but later never comes.
Sunday, 20 June 2010 17:42
Five (more) Stupid Management Decisions on Failing Projects A few weeks ago, I posted an article on five of the ten stupidest decisions management had done on troubled projects, as promised, here are the other five. Although these may all bring a little light hearted laughter, the goal is to educate in order to avoid repeat performances. We all have seen, and made, dumb decisions; finger pointing and blame will not improve the result. So, read on, enjoy and then share your experiences so we all learn more.
|
|
|
|
|
|
Page 2 of 12 |
Blog: Back From Red.jpg "BFR blog")
