iSixSigma

SixSigma in Software Engineering

Six Sigma – iSixSigma Forums Old Forums Software/IT SixSigma in Software Engineering

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #62770

    “Ken”
    Participant

    Tim,

    See my post as follows:

    https://www.isixsigma.com/topic/how-do-software-developers-use-six-sigma/

    Let me know if you would like additional info.

    Ken

    0
    #25854

    Tim
    Member

    I work in a relatively small software company in Saint-Petersburg, Russia. One of the problems we have encountered lately was how to implement our knowledge on Taguchi methodology and/or Six Sigma approach in software engineering. The question is: “What software metrics must be used to calculate representative statistics?”.
    Thanks in advance,
    Tim

    0
    #62771

    Venkatesh Bangale
    Member

    Hi Tim
    I am in same boat as you for Six Sigma approach in software. Still, I am trying to answer you question. Statistical analysis of software metrics depends up on the ‘Objective’ for the analysis. Answer to ‘why you want to analyze the data ?’will guide you to select appropriate metrics. Hope this helps.
    Best regards
    Venkatesh B

    0
    #62772

    JB Miller
    Participant

    Before you decide on the data to gather, it is recommended that your processes be completely defined, in this case the processes you are using for the software development effort.
    By using the knowledge you currently have about where you are having problems in the software development effort, you can then look at the processes that are actually affecting the software created.
    Decide if you really want or need to measure process, project, or product in order to track the solution to your problems. Examine your process to find the correct points to insert measures into, and begin data collection.
    John

    0
    #62773

    Markert
    Participant

    I too work in a software company that develops an AI code for the collections industry and have found in my improvement efforts that it helps to remember the basics.
    Processes are the sequence of events that create something of value to a customer.  So getting to your point, start by defining your process, gather VOC, then measure the CTQs for outputs, critical process steps, and inputs.  Measures will differ based upon your process.  Some measures that are always important to know are defects(as defined by your CTQs), lead/cycle times (read “The Goal” if you haven’t already), and any other data point for important layers of stratification.
    So in summary, return to the basics to get started in your efforts.  After your company has matured in it’s Quality mindset then more doors/measures will open up to you.

    0
Viewing 5 posts - 1 through 5 (of 5 total)

The forum ‘Software/IT’ is closed to new topics and replies.