Structured and Thought out Management Model

In this case it is very evident that Hardcore Financial Bank (HFB) needs a more structured and thought out management model. This will help them gain better knowledge on how to deal with large and complex projects. The two management models that are talked about in the case of Hardcore Financial Bank are the Capability Maturity Model (CMM), and the Agile Model. In the case, the Chief Information Officer of HFB had very high hopes of being able to choose between the CMM and Agile management models when looking at the report that was given to her by the trusted member of her IT staff. The report that was given to her, listed some of the positive and negative aspects of the two methodologies. This way, a decision on which methodology would be more suitable for HFB can be made.

Looking at some of the core concepts of the Capability Maturity Model, we can see that it is a very straight forward methodology, with very limited leg room for innovation or free thinking, since everything is so policy driven. Consisting of various capabilities, CMM ranges from level one at “Chaotic”, to level five at “Optimization”. This fact alone is a quality concern of mine because it makes it evident that the CMM approach deals more with the organizations management process rather than the quality of the software that is being developed. Another quality concern is that if used in the wrong organization and at the wrong hands, CMM might mitigate innovation. Innovation is a key concept when it comes to software development. A client relies on the software developing company to be able to have their software developers use their expertise when developing the software. It is very difficult to apply their knowledge or to make any changes for improving the software without applying innovation into the formula.

As the name states itself, Agile is more empowering on the development team. They do this by allowing them to focus mainly on coding of the software over some of the other aspects. This in turn can cause some client issues in the quality and usability of the end product. Another quality concern that I have with this methodology is that with Agile there is a lack of emphasis on necessary