Introduction: 

This month’s blog entry explores the complex relationship between project success and project leadership.  Risk of failure is potentially higher for IT projects than commonly acknowledged and, by all accounts, it would appear that success hinges less on strict adherence to methodology than on leadership.  Leadership, of course, assumes manifold forms, but in the context of this discussion I narrow it down to its core:  the moral/ethical responsibility of project managers to "tell it like it is," so that appropriate decision-makers can make effective decisions in a timely manner. 

This entry will be published in 3 parts:

• Part 1 will discusses some of the long-term trends in project management, that have been recorded over the last 15 years.  Given the ever-growing emphasis on rigorous management of IT projects, the interpretation of these findings continues being debated, but the conclusions are unambiguous.
• Part 2 will shine the spotlight on ethics in the context of project success.  Ethics in project management elude rigid definition, particularly as the PM discipline has evolved to encompass truly global projects, but even so, project management success is not synonymous with project success. 
• Part 3 will make the link between success, leadership, and ethics explicit.

I’m curious what experience others have had in this regard.  Are there other aspects of leadership that play a pivotal role in your projects?  Are ethics a primary driver of decision-making in your organization… or an ancillary consideration?  What effect have these played on the successful delivery of your projects? 

Please feel free to comment below.

Need uber-guru types who are willing to challenge the existing groupthink on design and architecture, especially on TDD and emergent design and pair programming anti-pattern” – job post at Monster.com 2/9/2010

I stumbled upon that quote following links on the role of the architect on an agile project. Maybe one important role of the architect is to help the team avoid groupthink.

Information Management recently sent around their pick of best IM blog articles of 2009.  Among them was Forrester’s James Kobelius’s reaction to Bill Inmon’s “incineration of a straw man concept that he refers to as ‘virtual data warehousing (DW).’”

Here are three things to remember when putting together a BI business case:

It is a commonplace to say we should manage data like a resource. But when you think about it, data is an asset but not a resource.  Data isn’t a thing like real estate, employees, or customers, but rather it represents all of those things.  In data-geek-speak, data is a meta-resource that holds information about resources.  That makes data a lot like money.

In a recent very thoughtful post on data quality, Paul Erb plays out an analogy comparing data users with Don Quixote and data quality professionals with Sancho Panza, then reverses the analogy to cleverly coin the “Sancho Panza” test of data quality professionals.  He encourages data quality professionals promoting the critical role of data quality to apply a what would Sancho say test to ensure tha

In a new post at Insurance Networking News Ara Trembly provides a balanced perspective on IT/business misalignment (Business/IT Misalignment: Whose Responsibility?).  He describes the problem as cultural, more amenable to relational than management solutions.    His conclusion sums it up: “Take a geek/suit to lunch today!”