Re: Discussion: Test Effort Estimation Techniques
On Thu, Jan 9, 2014 at 9:51 PM, akriti wrote: > Thanks Rob and Edwin for response. > > It is general topic discussion and there is no significant relevance to > open office work related to this topic. > > > > > * It might be useful for volunteers if one wants to know how much effort > he/she is spending (using any effort technique) while executing tests. For any estimation work, where I need to estimate my own person work, I use the techniques described here: http://en.wikipedia.org/wiki/Personal_software_process Essentially, define a metric for measuring the amount of work. Then find or create a tool to automate measurement. Then time how long it takes you do accomplish the tasks. Over time you then develop a baseline for quantity of work per unit time, your own personal productivity value. For example, with writing code the metric might be "non-comment lines of code". For testing it might be "test cases executed". For documentation it might be "number of words". Almost any work where the tasks come in countable or measurable small pieces can be estimated using techniques like this. Where this technique is especially valuable is when you then adjust your personal process and measure whether your productivity increases or decreases. It becomes part of iterative process improvement. Regards, -Rob > Thanks. * > > On Thu, Jan 9, 2014 at 5:05 PM, Rob Weir wrote: > >> On Thu, Jan 9, 2014 at 6:10 AM, Edwin Sharp wrote: >> > Hello >> > How is this relevant to us? >> > From the Wikipedia page on test effort it is for cost estimation - >> Apache OpenOffice is developed 100% by volunteers. >> >> It might still make sense, even in a volunteer-led non-profit context. >> It is not a "cost" in a commercial sense, but we still need to >> coordinate things like translation due dates, estimated beta and >> release dates, and so on. We try to line up communications, >> interviews with the press, etc., to coincide with milestone dates like >> this. So being able to estimate how long a test pass will take is >> useful to predicting these dates. >> >> That said, I'm not sure we do anything very sophisticated here. What >> I've seen is mainly counting test cases and estimating how test >> cases/hour a volunteer can execute on average. >> >> -Rob >> >> >> > Edwin >> > >> > On Thu, Jan 9, 2014, at 12:30, akriti wrote: >> >> Hello All, >> >> >> >> Happy New Year to all..!! >> >> >> >> I am interested in learning and implementing Test Effort Estimation >> >> techniques. >> >> Can we discuss about the latest or greatest Effort Estimation techniques >> >> here/ >> >> >> >> It would be nice if OO QA members share their experience. >> >> >> >> Thanks & Regards, >> >> Akriti Jaiswal >> > >> > - >> > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org >> > For additional commands, e-mail: qa-h...@openoffice.apache.org >> > >> >> - >> To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org >> For additional commands, e-mail: qa-h...@openoffice.apache.org >> >> - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Discussion: Test Effort Estimation Techniques
Thanks Rob and Edwin for response. It is general topic discussion and there is no significant relevance to open office work related to this topic. * It might be useful for volunteers if one wants to know how much effort he/she is spending (using any effort technique) while executing tests. Thanks. * On Thu, Jan 9, 2014 at 5:05 PM, Rob Weir wrote: > On Thu, Jan 9, 2014 at 6:10 AM, Edwin Sharp wrote: > > Hello > > How is this relevant to us? > > From the Wikipedia page on test effort it is for cost estimation - > Apache OpenOffice is developed 100% by volunteers. > > It might still make sense, even in a volunteer-led non-profit context. > It is not a "cost" in a commercial sense, but we still need to > coordinate things like translation due dates, estimated beta and > release dates, and so on. We try to line up communications, > interviews with the press, etc., to coincide with milestone dates like > this. So being able to estimate how long a test pass will take is > useful to predicting these dates. > > That said, I'm not sure we do anything very sophisticated here. What > I've seen is mainly counting test cases and estimating how test > cases/hour a volunteer can execute on average. > > -Rob > > > > Edwin > > > > On Thu, Jan 9, 2014, at 12:30, akriti wrote: > >> Hello All, > >> > >> Happy New Year to all..!! > >> > >> I am interested in learning and implementing Test Effort Estimation > >> techniques. > >> Can we discuss about the latest or greatest Effort Estimation techniques > >> here/ > >> > >> It would be nice if OO QA members share their experience. > >> > >> Thanks & Regards, > >> Akriti Jaiswal > > > > - > > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: qa-h...@openoffice.apache.org > > > > - > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > For additional commands, e-mail: qa-h...@openoffice.apache.org > >
Re: Discussion: Test Effort Estimation Techniques
On Thu, Jan 9, 2014 at 6:10 AM, Edwin Sharp wrote: > Hello > How is this relevant to us? > From the Wikipedia page on test effort it is for cost estimation - Apache > OpenOffice is developed 100% by volunteers. It might still make sense, even in a volunteer-led non-profit context. It is not a "cost" in a commercial sense, but we still need to coordinate things like translation due dates, estimated beta and release dates, and so on. We try to line up communications, interviews with the press, etc., to coincide with milestone dates like this. So being able to estimate how long a test pass will take is useful to predicting these dates. That said, I'm not sure we do anything very sophisticated here. What I've seen is mainly counting test cases and estimating how test cases/hour a volunteer can execute on average. -Rob > Edwin > > On Thu, Jan 9, 2014, at 12:30, akriti wrote: >> Hello All, >> >> Happy New Year to all..!! >> >> I am interested in learning and implementing Test Effort Estimation >> techniques. >> Can we discuss about the latest or greatest Effort Estimation techniques >> here/ >> >> It would be nice if OO QA members share their experience. >> >> Thanks & Regards, >> Akriti Jaiswal > > - > To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org > For additional commands, e-mail: qa-h...@openoffice.apache.org > - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Discussion: Test Effort Estimation Techniques
Hello How is this relevant to us? >From the Wikipedia page on test effort it is for cost estimation - Apache >OpenOffice is developed 100% by volunteers. Edwin On Thu, Jan 9, 2014, at 12:30, akriti wrote: > Hello All, > > Happy New Year to all..!! > > I am interested in learning and implementing Test Effort Estimation > techniques. > Can we discuss about the latest or greatest Effort Estimation techniques > here/ > > It would be nice if OO QA members share their experience. > > Thanks & Regards, > Akriti Jaiswal - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Discussion: Test Effort Estimation Techniques
Hello All, Happy New Year to all..!! I am interested in learning and implementing Test Effort Estimation techniques. Can we discuss about the latest or greatest Effort Estimation techniques here/ It would be nice if OO QA members share their experience. Thanks & Regards, Akriti Jaiswal
