Project Portfolio-Program Management

A common comic mail circulates with this image, which gives good understanding of how requirements captured during a project life cycle goes like this: Typical Software Development Life-cycle explained Above picture succinctly tells about common perception of developing a software, how requirement understanding filters with changing roles, time and space with gaps between factual and results. Thanks to the  the word "agility", which has evolved in world of software technology with the evolution of Rational unified process the term use-case or scenario development for documenting and capturing requirement in the initial phase of software development. "A use case is a software artifact of systems and process of expected sequence of interactions between a module and an external actor, which leads the actor to desired goals and objectives. " Use case scenarios can be mirrored as clip of a movie making scene development where-in director has assigned a s

Is IT driven by business? I believe its a good question to be asked at this point in time after the doom of financial markets allover world. When top investment banks collapsed in USA and Europe everybody is asking a question how it is possible if the system in place. IT in general supposed to be driven by business requirements so its natural process that, as other component in business, this is also adding value to business, but is that benefits realized to business? Is IT a hype from time and again? Business value of IT measured in different metrics and methodologies that may or may not give true picture of IT value to business, so the contradiction lies in the hypothesis itself that IT is driven by business which is adding no value but continuing. In the concurrent world where businesses are competing for survival and existence IT is invaluable from intangible perspective.  Making sense of PM triangle  The infamous scope, cost and schedule trio can be realized for IT business val