Managing the Changes or Changing to Manage February 10, 2010Posted by Somenath Nag in Distributed Engineering, Enterprise Next.
Tags: Agile Methodology, Change Management, Requirements Management, Scrum
add a comment
According to Standish group’s ‘Chaos Report’, only 32% of all projects are succeeding, which are delivered on time, on budget, with required features and functions. Rest 68% of all projects late, over budget, and/or with less than the required features and functions, cancelled prior to completion or delivered and never used. This is not a very rosy picture. We all know from our own experience in managing projects, one thing comes out very clear is that managing the changes in requirements is probably the single biggest challenge that any project manager has today. But, if we look from a project sponsor’s view point, we find that it is absolutely important for her to incorporate changes during the product or application development life cycle. Otherwise nobody will be buying/using her software. From our experience of managing projects in traditional waterfall or iterative models we know that changes are expensive, they always have a negative impact on project schedule & cost. But, in reality, we know that changes are inevitable, in the software that we build or in our life! Here comes the most critical dilemma of our life, how do we manage to avoid changes? But, is it really that we should look for? Or we should try to change so that we can manage the reality? (more…)