kumsan060

 Profile Answers by kumsan060 Questions by kumsan060

• Jan 16th, 2008

 

For Full Time Position - It is for my security in the company so i can work without fear at max extent and Its good for project untill it complete i never quit off


Estimation - can be done from metrics. Estimation and schedule done from metrics by calculating all the effort of manpower

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• May 27th, 2009

 

Full time :  You can say like i'm seeking for my job security and if my job is secure then i
                  will put more concentration on my job.

estimate: Yes this can done by exp or using some metrics..

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 8th, 2009

 

Q1: Why you are looking for full time position?

1) I enjoy working in the industry.  I believe your company is the best in class and I

want to contribute toward its continued success.
2) I have researched your company and feel I would be a greater asset as a full-time

employee.
3) I want a 401k, stock options, and other benefits that comes with full-time employment.

Q2: What are the different ways to estimate testing?  How do you estimate and schedule the testing process?

When estimating a test project, you must consider:
1) the complexity of the program to be tested
2) the resources you have to test it, and
3) the amount of time alloted for testing

The first thing I do in order to estimate complexity, resources, and time is to facilitate a business requirements review with all my testers.  By reviewing requirements with them, I learn the complexity of the application.  At the end of this meeting, I assign functionalities to each tester.  I give them several days to pour over their requirements again and get a good feel for their areas and then I ask them how much time they believe they need to 1) produce test plans, 2) produce test cases, 3) map requirements to test cases, and 4) prioritize test cases.  Typically, I will take these numbers and apply a multiplier to account for their optimism as well as unanticipated risks.     

kurtz182

 Profile Answers by kurtz182 Questions by kurtz182

• Dec 11th, 2009

 

Q1: Why you are looking for full time position?

1) I enjoy working in the industry. I believe your company is the best in class and I want to contribute toward its continued success.
2) I have researched your company and feel I would be a greater asset as a full-time employee.
3) I want a 401k stock options and other benefits that comes with full-time employment.

Q2: What are the different ways to estimate testing? How do you estimate and schedule the testing process?

When estimating a test project you must consider:
1) the complexity of the program to be tested
2) the resources you have to test it and
3) the amount of time alloted for testing

The first thing I do in order to estimate complexity resources and time is to facilitate a business requirements review with all my testers. By reviewing requirements with them I learn the complexity of the application. At the end of this meeting I assign functionalities to each tester. I give them several days to pour over their requirements again and get a good feel for their areas and then I ask them how much time they believe they need to 1) produce test plans 2) produce test cases 3) map requirements to test cases and 4) prioritize test cases. Typically I will take these numbers and apply a multiplier to account for their optimism as well as unanticipated risks.

• Nov 1st, 2011

 

I'm not sure if contracting/consulting is a common practice in India these days. When I was still working in India, many of the MNCs (Infy,Satyam,TCS, Wipro etc) came up with a rule to hire 90% full time staff and 10% contract/temporary staff. anyhow here is my answer.

NEVER ever mention job security; its a cliched answer. It's an easy way to eliminate candidates who come across as cookie cutters. Every job posting these days demands "out of the box" thinking employee and not a cliched cookie cutter! If I were you I wouldn't even go there.

So you can say..
Everyone wants to be a part of company that performs well looks after it's employees well (mention the company growth statistics if went public AKA IPO). I would like to be a part of the company and experience its wonderful culture; feel part of the team (this will speak of your interest in the company & job position. This will also tell employer how through you are in your work including a job interview!) Temporary staff may not get to fully experience the company culture and besides it's short-lived!

Be ready to talk about the culture. Tell the employer you have heard from your past colleagues/friends etc who were with the company you are interviewing with. Word of mouth : That's direct advertisement!

Moving on to the next part of your question - estimating and scheduling test efforts.

Best practice is to look at projects similar to the current one that needs estimation. Looks for data such as over all testing hrs, creating reports and other documents, bug re-testing, # hrs spent in writing test cases, # hrs spent in logging defects/bugs, etc. Add up all these numbers to get the estimated testing hours.

Rule of thumb: always pump up estimated hrs (based on past data) by at least 20%. I usually add 30% to accommodate vacation time, sick leaves etc. The net value is what you need to give to project holders. Based on estimation you can schedule the deadlines - setting specific dates.

Once project stake holder and client accept these #, the schedules deadlines are frozen.

estimation : how many hr will it take to accomplish a task.
Scheduling : Coming up with target dates (deadlines) based on the # (estimated) hrs.