Hello Guys,

 

Generally, in an IT Industry, there are 2 kinds of Projects "Development" and "Maintenance" project.In a Development project, we could have feature development and span over a period of time followed by stabilization etc. . and is generally a regular development where as in Maintenance, mostly it deals with Bug fixing or Ticket Fixing ...

 

The question is in Development Projects the measurement of Schedule Variance is easy and could be straight forward = (Actual - Planned )/Planed (could be +ve or -ve depending if planned > actual or vice versa), But in Bug Fixing task how can we measure the same.

 

Challenges in Bug Fixing : The customer could come and say that whatever tickets that you were working is not important for you to fix today .I want you to work on 20 new tickets and are of higher priority .and this has been case in ticket fixing mode as the priority keeps on changing .Sometimes ,a low priority tickets (based on classification) becomes a higher priority next day , you may have to leave all the previous working tickets and starts again .Secondly , each ticket has its own complexity and therefore how  planning is feasible in such case .

 

How can we factor such changes to plan for a ticket? Are there any schedule variance metrics which can measure this challenge and provide a true reflection of data. and also the planning can be done because ..(please note that even bucketing of tickets does not work because tomorrow you may need to work on the new set of tickets ) 

 

Please suggest multiple options for planning and measurement ??

For Maintenance projects you can track below metrics,

Inflow & Outflow 

SLA tracking 

Bad fixes

Productivity of each bug fix