Sample Size Calculation
Six Sigma – iSixSigma › Forums › Old Forums › General › Sample Size Calculation
 This topic has 12 replies, 7 voices, and was last updated 14 years, 11 months ago by annon.

AuthorPosts

October 16, 2007 at 9:48 am #48430
I am in the Measure phase of a project and used a 1sample Ttest to calculate if the target I have defined is significant different then the current baseline. Now I would like to calculate how many samples of the improved process I will need to take, to prove the succes of my project.
Should I use a 1sample Ttest or a 2sample Ttest?
Please advise thanks0October 16, 2007 at 10:00 am #163206
Six Sigma guyMember@SixSigmaguy Include @SixSigmaguy in your post and this person will
be notified via email.2 Sample T test My opinion. Because you are looking for statistically significant difference before and after improvement. Again if you are trying to do it with a standard/hypothetical mean then go for 1 sample t test. What is that you want to prove? is there any improvement in mean from measure to improve phase or is there any difference in mean from a standard mean.I hope your data is normally distributed..
I hope i am clear. When you frame your hypothesis correctly then choosing the test becomes easier.0October 16, 2007 at 11:23 am #163208Thanks SSGuy. I am doing a cycle time reduction project at a manufacturing facility. We have defined a target cycle time for the project. The hypothesis was to see if the target cycle time is statisticallty less than the baseline cycle time mean. I used a 1sample Ttest (correct?).
The next thing I would like to know is, how many samples (cycle changes) do I need to take to statistically prove that the improved cycle time is less than the baseline.
I used a 2 sample ttest in Minitab using baseline StDev (assuming equal variance) and a power of 0.9.
I presented the results to the project team and we got into a discussion when to use 1 sample ttest and when to use 2 sample ttest for sample size calculations. And I still not sure when to use the 1 sample ttest for sample size calculation.
Please enlighten me.
Regards.
MaJo0October 16, 2007 at 12:04 pm #163209
Six Sigma guyMember@SixSigmaguy Include @SixSigmaguy in your post and this person will
be notified via email.I think i misinterpreted your question. You need to choose 1 Sample t test ( i hope you are doing it in minitab). Since you are doing 1 sample t test to statistically prove/disprove that target is less than baseline etc you need to choose 1 sample t test to determine the number of samples required.
Instead if you want to prove that after doing improvements your cycle time has improved/decreased from baseline then go for 2 sample t test.
Ok to summarize
if its before and after then go for 2 sample t test
if its target and actual then go for 1 sample t test0October 16, 2007 at 1:08 pm #163212
At Nib MiParticipant@AtNibMi Include @AtNibMi in your post and this person will
be notified via email.Here is the Answer:
1 Sample Za sample mean and a target value when population standard deviation is known
1 Sample t a sample mean and a target value when population standard deviation is not known (Note: Normality assumptions relaxed when the number of sample observations is large (generally true when sample size >30))2 Sample tmeans obtained from two independent samples
Paired tmean differences obtained from paired samples
Note: Above tests are used when the dependent variable (response) iscontinuous and the independent variable (factor) is discrete
0October 16, 2007 at 7:40 pm #163240MaJo,
If you are interested in the minimum sample size to catch a reduction in your average cycle time, you would use the Stat>Power and Sample Size>2 Sample T (if using Minitab) or DOE>Sample Size and Power>Two Sample Means (if using JMP). In determining the minimum sample size, one of the important facets that you must determine is what the business considers practically significant when reducing TAT. Is 30 minutes significant? 3 hours? 3 Days? Simply showing statistical significance means the result seen was unlikely to have occurred just by chance. With enough data, you can make relatively small differences in average performance statistically significant, but is it something that the business would make an investment in to achieve the projected improvement?
The greater the uncertainty that is used in providing some of the key pieces of information (e.g. standard deviation, delta, etc.); the more youll want to pad the sample size that comes back. Typically, I suggest an extra 20% over what the software reports for sample size. This helps guard against estimates that dont match with reality.
Regards,
Erik0October 17, 2007 at 3:10 am #163249Unless I am missing something, the aforementioned suggestions havent addressed your original question. The hypothesis tests are not going to indicate how many times you should confirm the results of your changes. This is a function of the natural cycle of the process and should be discussed with your MBB or process owner.
As for when to use 1 v. 2 sample t tests, use the ttest anytime the population std dev is unknown and/or when dealing with small sample sizes (when n<30)…this will be most of the time….use a onesample t test when comparing an independent population against a target or stated value (like you did earlier) and a two sample t test when dealing with two independent populations, such as taking another measure of your process and comparing it with the original sample you took to confirm the change.
Dont forget to check the underlying assumptions…normality, independence, and equal variation (this one for the 2 sample t)….for example, cycle time data often will not approximate normality.
Good luck.0October 17, 2007 at 5:58 am #163250Thanks you all for your valuable input – the difference between 1sample & 2 sample ttest is very clear now.
I would like to address Annon’s point. Some background info: the project is about reducing the cycle time between two production campaigns. On this plant we produce 2 different products and there are not that many campaings – so data is limited – change over approx every six weeks.
I can discuss with the process owner when he would agree that the changes implemented are sustained – but the culture at my company currently is that once a project is finished (that is a change has been implemented) the project is succesful.
So to change the culture to become (more) data driven and to get peolpe used to the idea that statistics could be a very powerful tool in data analysis (when used properly) – I wanted to use the sample ttest to make my point that we just can not walk away once a change is implemented.
Any thoughts, comments, helpfull tips?0October 17, 2007 at 7:28 am #163255
fake accrington alertParticipant@fakeaccringtonalert Include @fakeaccringtonalert in your post and this person will
be notified via email.Excellent as usual
0October 17, 2007 at 4:08 pm #163270The control phase of DMAIC will address these issues. Not only will it work to sustain the gains you have made, but it provides a valid methodology for closing and signing over the project to the process owner. See the blue bar for some good introductory info.
Mistake proofing (ie polka yoke) and SPC (ie control charting) are two techniques you might want to research while formulating your control strategy. The former is generally considered preferrable, while the latter is often a useful secondary option….see the ASQ website for some good control chart templates if you decide to go this route.
Good luck.0October 17, 2007 at 8:31 pm #163294I agree that the methodology and tools will take care of sustaining the improvements – if the companies culture allows it. In our company we are not at that point yet.
So we need more (data, change leadership,….) to convince people that they need to follow the methodology and use the appropriate tools.0October 17, 2007 at 8:34 pm #163295Majo:
Erik makes a good point. I also pad the sample size with 10% usually, but anywhere between there and 20% will suffice. Keep in mind the cost of the sampling process as you add to yoru minimum sample size – will the return outweigh the cost…0October 17, 2007 at 8:50 pm #163304If you cant get someone to follow a basic control plan, then I wouldnt be in there wasting my time and hurting my reputation. This is the kind of CAP issue you want to discuss in DEFINE and clearly state in ¨roles and responsabilities¨ or ¨stakeholder analysis¨.
But if you do not have the avid support of the process owner AND the project sponsor (preferably at a Director level or above), dont go near it. Thats my advice.
Good luck.0 
AuthorPosts
The forum ‘General’ is closed to new topics and replies.