EVM Without Quality is Unsuitable for Software Project & Program Management

Page 1

International Research Journal of Engineering and Technology (IRJET)

e-ISSN: 2395 -0056

Volume: 04 Issue: 03 | Mar -2017

p-ISSN: 2395-0072

www.irjet.net

EVM WITHOUT QUALITY IS UNSUITABLE FOR SOFTWARE PROJECT & PROGRAM MANAGEMENT Ms. Vanshika T1, Dr. Poonam Sinha2, Ms. Rachna Kulhare3 1Department

of I T, UIT, BU Bhopal Department of Electronics, UIT BU, Bhopal 3Asst. Professor, Department of I T, UIT BU, Bhopal

2 Professor,

---------------------------------------------------------------------***---------------------------------------------------------------------

Abstract: Earned Value Analysis/Management is an

light of these essential difficulties, the new concept that does not exist in traditional projects comes out as an inevitable part of IT project: reworking. It represents all the changes to the existing system as well as corrective actions of defective, failed or non-conforming items. Reworking itself introduces further complexity in terms of planning, estimating, monitoring and controlling. It could also cause further rework in a recursive cycle that can affect the project

industry standard method of measuring project's progress at any given point in time; forecasting its completion date and final cost, and analyzing variances in the schedule and budget as the project proceeds. It compares the planned amount of work with what has actually been completed, to determine if the cost, schedule, and work accomplished are progressing in accordance with the plan. As work is completed, it is considered "earned".

timeline. In various studies performed it has been reported that approximately 40% of the total IT project budget was spent for reworking. The studies also show that the cost of rework can approach 50% of the project budget for the large IT projects. Reworking impacts the entire development process from definition to implementation and testing.

EVM /EVA missed to consider a significant and important aspect of Project Management - Quality which is completely missing from its landscape. This paper aims to highlights, how not including quality in traditional EVM is detrimental/counterproductive in reporting project progress of software projects.

IT projects are suffering a lot from reworking. Based on the essential characteristics of the IT developments projects especially and the quality related issues, reworking is accepted as a natural consequence and an indispensable part of the projects. For the projects of the other industries like construction projects, reworking is not very common or acceptable particularly after some milestones. As a result, the consequences of reworking are not so visible for those projects in most cases.

Keywords: Program Management, Project Management, EVM, Earned Value Management, Cost of Quality

1. INTRODUCTION IT entities are remarkably complex compared to any other construct since there are no two parts alike in general. IT cannot ignore or simplify details of the real world. Complexity grows exponentially as the size of the system increases. Since there is no physical reality, it cannot be accurately modeled as in the case of, for example, construction. The projects are continuously subject to change even after being completed. In contrast, manufactured things, such as buildings, cars, and computers are rarely changed after manufacturing. They are simply outdated by later models. For example, callbacks of automobiles occur reasonably infrequent.

IT projects especially development projects have significant rework effort directly influenced by quality factors. The quality of the work matters and affects the quantity as well in terms of reworking. A research shows that IT development specialists spend about 40 to 50 percent of their time on avoidable rework rather than on work that’s done right in the first time. Another study states that software vendors typically spend 30% to 50% of their development budget on detecting and fixing errors. EVM in a traditional form focuses on the three main elements of software project success: scope, schedule and cost. It essentially emphases the quantity of the work performed. It does not deal with the quality explicitly. EVM assumes quality to be part of scope element. It means when the task is completed, it is supposed to be completed without

In particular, because of the changeability, IT projects are subject to continuous changes which makes planning and controlling very hard. Additionally, complexity and invisibility bring other challenges into management. In the

Š 2017, IRJET

|

Impact Factor value: 5.181

|

ISO 9001:2008 Certified Journal

|

Page 1288


Turn static files into dynamic content formats.

Create a flipbook
Issuu converts static files into: digital portfolios, online yearbooks, online catalogs, digital photo albums and more. Sign up and create your flipbook.