iSixSigma

Some questions!

Six Sigma – iSixSigma Forums Old Forums General Some questions!

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • #49009

    nelson
    Participant

    I have a testing project on FX trading application, which is Offshored to India. I want make sure that 1. I dont get any defects found by Users 2. Improve the test case efficiency (using Orthogonal Arrays) 3. Spend less time on testing without compromising quality 4. Improve productivity of my Offshore team.
    My questions are:- 1. What are the datas and charts required to do Hypothesis Testing for my project? 2. I have asked the team to use system time to check their effort on each task – will this qualify for my Gage R&R analysis? 3. How do I quantify the above items in terms of cost/dollars? 4. How do I quantify Users found defects in terms of dollars? 5. what other ways can i think of to improve the test case efficiency? (as this is a purely knowledge based service)
    1. Is it possible for me to come up with CTQs without having any customer specs?

    0
    #166647

    Neal Nelson
    Participant

    I have a testing project for FX trading application, which is Offshored to India. I want to make sure that 1. I dont get any defects found by Users 2. Improve the test case efficiency (using Orthogonal Arrays) 3. Spend less time on testing without compromising quality 4. Improve productivity of my Offshore team.
    My questions are:- 1. What are the datas and charts required to do Hypothesis Testing for my project? 2. I have asked the team to use system time to check their effort on each task – will this qualify for my Gage R&R analysis? 3. How do I quantify the above items in terms of cost/dollars? 4. How do I quantify Users found defects in terms of dollars? 5. what other ways can i think of to improve the test case efficiency? (as this is a purely knowledge based service)
    Is it possible for me to come up with CTQs without having any customer specs?

    0
    #166653

    qualitycolorado
    Participant

    Nelson, Good morning!
     
    Wow, you have a very ambitious project.  If I understand you correctly, your project pertains to a foreign exchange trading computer application, and your project is suppose to reduce defects, and improve the testing efficiency and productivity of your Team, all at the same time.  Very admirable, though doing all of this at the same time may be quite challenging.
     
    I think I follow you that far.  It’s not clear how MUCH you need to improve those, but I’m sure that you have numeric goals as part of your effort.
     
    Here is where you lost me: it looks like you are jumping right into hypothesis testing.  I’m not quite sure why.  Don’t get me wrong: its a great Six Sigma tool, if used in the right situation.  I’m not sure why it is the tool you chose, however. 
     
    Could you elaborate?
     
    Also, for your gage R&R:  I also do not follow what you are asking here.  What you have described so far definitely is not GR&R — Please elaborate.
     
    Best regards,
    QualityColorado

    0
    #166669

    Neal Nelson
    Participant

    Thanks for your inputs QC – I have already started capturing the data.
    To be honest, this is my first SS project (i only had a GB training). Though I am an engineer, I only the concepts what I had studied in my engineering. Hyp Testing is one area where I am not very strong. From the data I have collected, I have come up with a “not so reliable” argument. Now I must analyze the authenticity of my argument for which I was told that I need to do a Hyp Testing. Thats when I decided to post this message.Even I am not able to justify why I should use this tool (I just crossed “M”phase). According to the analysis of data, I came up with an argument that testing efficiency is slowing down because of 1. too many test cases (which are infact redundant) (this i found after I used Orthogonal Array technique)  and 2. missing scenarios (due to improper planning) I feel that somewhere I am going in a zig-zag direction. My disadvantage is I have a BB mentor who is not a an expert BB and doesnt understand much of statistical jargons (this is the 1st project for him as well). My limitation is that I can not pass it on to my Offshore team as they are very new to this concept.
    Over to GR&R, I did an effort analysis as follows: I chose 6 test sets and gave them to 3 QA engineers to execute them; such a way that every engineer executes all 6 sets in a week’s time. Each engineer noted his/her effort spent on each test set based on the stop watch. My GRR was to do the MSA on the stop watch – so that I can shift to some other time keeping system.
    I hope the above explanation will help. Kindly let me know if I am in the right direction of using tools (I know I jumping from M phase to I phase and vice versa) Call me a confused SS candidate or whatever.

    0
    #166704

    qualitycolorado
    Participant

    Nelson, Good morning!
    Thanks for your note.  I have re-titled the thread, so that others will see it and perhaps provide comments, also.
    You have a tough Project situtation, which I think you already realize.  You have a “Black Belt” guiding you, but not really, since this is his first project, too.  He may be a “Black Belt-in-Training”, but would not quality as a BB at any other company.  Your project probably has a Champion / Sponsor, but it is also likely that he/she is a novice, too.
     
    However, that is not meant to discourage you. Your enthusiasm will definitely help you.
     
    As I noted previously, I am not sure why you decided on using hypothesis testing, and it sounds like you may not be clear about this, either.  Hypothesis testing is a fine tool, but it may not be suitable to your situation or data.
     
    It may be more useful to start with basic root cause analysis (RCA).  I would like you have some possible causes already identified (such as “too many test cases” and “missing scenarios”.  Try organizing them, using a cause-and-effect diagram (either the “fishbone” version, or just a tree diagram version). Get ALL of the possible causes down.
     
    Then, use a root cause verification table to identify: 1) the most-likely causes; 2) how you will “verify” whether each possible casue is really a cause, or not; and 3) the results of your verfication for each possible cause.
     
    After finding the root cause or causes, you can then proceed to the “I” step (Improve) to develop ways to deal with them.
     
    The root cause verification may take some time, but will be well worth it.
     
    Best regards,
    QualityColorado
     
     

    0
    #166708

    Fake Harry Alert
    Participant

    You  should  be  glad  to  receive  such  a  comprehensive  answer  from QC.I  have  tried several  times but I  could  not succeed.
    good  luck 

    0
    #166716

    qualitycolorado
    Participant

    FHA,  Good morning!
     
    Sorry for the delays, been out of touch for a while.  Please refer to postings 133247 and 133249.
     
    Best regards,
    QualityColorado

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

The forum ‘General’ is closed to new topics and replies.