MBA Alumni | MBA Students | MBA Aspirants | MBA Forums
--- MBA Home ---

CoolAvenues.com

offers
Advertising
Services

on the web  
 

Home     |    MBA Jobs      |     Knowledge Zone      |     Seminars      |     Placement Report      |     Admission Alert       |     café     |     Search

Operations Article | "Motivation & Competitiveness Framework for Application Support Teams"

Operations @ Knowledge Zone

 Home

 Knowledge Zone Home

 General Management

 Finance

 Marketing

 Human Resource

 System

 Operations

 Knowledge Seminar

 MBA Forums
 Search
 Join e-Communities
 Be a CoolAssociate
 Give Suggestions

 Company Search
 
 

Subscribe:
Seminar & MDP Alert
   To keep yourself updated with the latest Seminars & MDP happenings in the country, join Knowledge Seminar& MDP mailing lists.


Latest Management Discussion on CoolAvenues Forums



Motivation & Competitiveness Framework for Application Support Teams

- by Ashish Gupta *

Previous

Page - 7

4. Correct Fixes: This parameter is the most important factor for ensuring application stability in production environment. One bad fix might result into outage in the system impacting thousands of users and critical business operations of
the customer organization. Therefore, it is very essential that support teams are encouraged to "build" a culture of delivering correct fixes in the first instance.

Failed Fixes are categorized as follows: -

  • Defects found during internal quality assurance process of software fixes supplied (IQADEF)

  • Defects found as "Failed Fixes in Production", i.e., software fixes which did not work as per requirement of original ticket (FADEF)

  • Regression Defects, i.e., software fixes which worked correctly as per original requirements of ticket but might have introduced another problems in application (REGDEF)

    Total Failed Fixes are computed as follows: -

    TOTDEF = IQADEF + FADEF + REGDEF

    Therefore, Correct Fix % is calculated as follows: -

    5. Residual Defects: One of the major critical success factors for support project is preventive and perfective steps taken by teams to stabilize their respective modules (rather than working in "corrective maintenance mode" where team supplies software fixes against raised tickets only). As part of preventive and perfective maintenance activities, teams identify relatively weaker areas of respective modules (on the basis of incidents and tickets reported by end-users) and plan additional regression testing / code refactoring on a continuous basis on their own. These activities help to stabilize applications faster and results are visible from the "residual defects" reported from the live application (i.e., declining trends of tickets). Residual Defects can be calculated as Tickets per unit size (Tickets per Function Point OR Tickets per KLOC). This parameter can be measured as: -

    Next


    * Contributed by: -
    Ashish Gupta is an MCA graduate, currently working as a Lecturer at Lakshmi Narain College of Technology (LNCT), Indore.


    Post Your Comments       |       E-mail to Friend       |       Want to Contribute

  • Send this E-mail this Article

     

    MBA Jobs
    MBA Preparation
    B-Schools
    MBA Forums
    About CoolAvenues
    Senior Mgmt Jobs CAT / MAT/ CET Dean talk CAT Preparation Post a Job
    Finance Jobs Admission Alert B-School Profile Executive MBA Advertise with Us
    Marketing Jobs MBA Insider B-School Diary Career Help Contact us
    HR MBA Jobs MBA Admission Process Summer GMAT Privacy
    Operations MBA Jobs English Preparation MBA News Companies Copyrights
    IT MBA Jobs MBA Abroad MBA Events B-Schools About CoolAenues
    Consulting MBA Jobs CAT / MAT / CET test papers MBA Placements Summer Guidance
    Resume Design Tips MBA in India Summers Guide Classifieds

    © All Copyrights exclusive with Zebra Networks
    Part or full of the contents can not be published, copied or reproduced
    in any form without the prior written exclusive permission of Zebra Networks. Pls refer to CoolAvenues Copyright section.