Why on earth would this BOK be into existence when there are loads and loads of documentation available on company archives that we can refer to during crunch times. So Am I reinventing the wheel ? No way. The below bulleted matrix would help you keep afloat in case you hit the agile monster or have butterflies in your stomach about Agile based projects and its future. So is Agile Immortal ? Humm ……….let me think. Well Almost for the current era. Agile is a way for product companies to substance their lively hood by ensuring they power pack their software products by business driven factors which we know as requirements, enhancements, UI features, and bug fixes. Agile is a way to build software using the small optimized revisions that resembles the iterative and incremental approach. This resembles as a scaled down approach of the predecessors. The key element to Agile is it ensures that the risks elements are at bay.

According to AIIM & Accenture Surveys report – in the next few years’ volume of information produced by our civilization will be doubled. Report also points, that arrangement will be split into 20% of structured data and 80% of unstructured data. Following this analysis, Gartner (Feb 2008) points that “By 2009 ECMs will become the focal point for empowered managers, enabling proactive or reactive responses to opportunity and threat scenarios”.

A recent survey suggests that two thirds of large organisations are looking to implement a service catalogue in the next few months.  However, the same survey also stated that less than half could articulate what benefit the service catalogue would be to the business.  Looks like we are in a classic technology hype cycle!

This document emphasis on the variety of frameworks development approaches and their categorization and then walks thro’ the Visual Studio framework creating process. At the end it contains a case study of framework targeted for a telecommunication companies.