Saturday, July 30, 2005

IT Engagement Model

One of the key ingrediance for success is clearly defining the roles and responsibilities within IT. There are multiple stake holders in IT with each doing their best to provide the highest level of support to the business. Most of the time this results in people stepping over each other - especially as there generally is a not a clear definition of everyone's task. Most of the project failures are due to the confusion is the definition of the roles between the PMO, Project Manager and the Enterprise Architects, resulting in resposiblities overlap and lack of making decisions. Gartner has produced an excellent job of defining the IT engagement model at a very high-level and is independent whether organizations adopt SOA or not.


Yogish Pai said...

The updated RACI (Responsible, Accountable, Consulted and Informed) matrix for the IT Engagement model is available at my Jun '08 blog entry with the same titile at

it outsourcing services said...

Most agile implementations use a routine and formal daily face-to-face communication among team members. This sometimes includes the customer representative as observers. In a brief session, team members report to each other what they did the previous day, what they intend to do today, and what their roadblocks are. This standing face-to-face communication prevents problems from being hidden.

java software company | software development company | java development company | blackberry application development | iphone application development | android application development| java developers | java outsourcing | java software development company | agile team java | it outsourcing services

Key Learnings - Using EDA to implement the core SOA principle of "loose-coupling"!!!

A lot has been said about how SOA and EDA are unique "architecture styles". It seems like only one or the other architectural prin...