Project Portfolio-Program Management

Vectorized from: Ken Schwaber, Mike Beedle: Agile Software Development with Scrum Prentice Hall PTR, 2001 (Photo credit: Wikipedia ) Over the years, its by human nature to quantify most of the aspect when it comes to Return on investment . Project dashboard are meant to provide bird view of the project's overall health from a top level perspective. Although it gives a broad level view of the time lines , resource utilization, budget and so on so forth. Can we quantify performance indicators like human aspect of deliverable like motivation levels of team members, quality of customer sustenance, business continuity etc. Since emotional intelligence has certain predominance over IQ definitely it matters. In concurrent times of agile development where practices like scrum, iterative development , extreme programming are kind of just in time techniques to deliver solutions to different kind of projects. can we be able to quantify human aspect of indicators in agile ...

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...