tag:blogger.com,1999:blog-1552057561694398593.post6291380970265991767..comments2008-04-02T11:58:24.824-07:00Jason Henleynoreply@blogger.comBlogger1125tag:blogger.com,1999:blog-1552057561694398593.post-14069396906329740122008-04-02T11:58:00.000-07:002008-04-02T11:58:00.000-07:00An interesting post and one that to some extent I have to disagree with. Yes, for sure we can use the maturity model to assess where we are and then decide that it is too much effort and not go further.<BR/>Or we can do as we are doing at one MomentumSI client. We used the MomentumSI maturity model to get a very frank (and rather uncomfortable) assessment of where we are, generated some recommendations to move forward to the next levels and are actively working them. This is how it should be, of course.<BR/>Why does this client do it and other companies not? I think to a large extent it depends on what the pain drivers are, and therefore what we need to do to overcome the pain. My client recognizes that they have a lot to do to overcome the current pain of a high volume system running as monolith with change rolled out very frequently. Tough environment and one that can definitely benefit from an SOA. <BR/>They have taken a realistic look at the levels of maturity across the multi-dimensional model and realized how far they need to go to achieve the benefits they need. They may go further at some point, but they have determined that there are some places they need to go, but they don't have to be level 5 in every dimension.<BR/><BR/>Chris BirdChris Birdhttp://www.blogger.com/profile/13436436994311245922noreply@blogger.com