Happened to read Pradeep's blog today and got enthusiastic to write a blog. Found there is a intricate situation for me to blog about, and almost all of us would have faced it some time.
Of late I was called by one of the engagement manager to help one tester (the lone warrior and new joinee to organization) in project to help him on test strategy. Had a meeting in the after noon with project team and got to know that team has least information on project (assignment had begun a week ago). Project is a migration task from one java technology to other and testing activities would involve function testing (with no definition of scope) followed by performance testing. Team is bewildered as they have least information about project whereabouts and the tester has no idea on how he would carry out functional and performance testing. On top of this the very first deliverable for the project is test strategy document.
So our warrior has been asked to come up with test strategy. And he indeed developed a test strategy document on the basis of general info and experience ha has gained over years. The document does not consist any specific attribute to project (for obvious reasons). Now engagement head is not happy with length of document as this is a deliverable which is going to bring more money and probably more business. He believes that it has to have more info. I don't question him for his opinion as his objective is to get more business to company may be right from his perspective.
So what I did? Well first of all I consoled the poor tester who was feeling left out. A new joinee having feelings of not being able to live up to responsibilities of his first job. Besides this only option I could think of was questions, zillions of questions to be asked to client as we had least info about the project. I had a dedicated section added to doc about questionnaire which we had to know before having the testing assignment begun. He added a couple more pointers about exit and entry criteria for each phase of functional and performance testing. The document is sent to supervisor and review comments are awaited.
So what different would you have done in this situation?
Of late I was called by one of the engagement manager to help one tester (the lone warrior and new joinee to organization) in project to help him on test strategy. Had a meeting in the after noon with project team and got to know that team has least information on project (assignment had begun a week ago). Project is a migration task from one java technology to other and testing activities would involve function testing (with no definition of scope) followed by performance testing. Team is bewildered as they have least information about project whereabouts and the tester has no idea on how he would carry out functional and performance testing. On top of this the very first deliverable for the project is test strategy document.
So our warrior has been asked to come up with test strategy. And he indeed developed a test strategy document on the basis of general info and experience ha has gained over years. The document does not consist any specific attribute to project (for obvious reasons). Now engagement head is not happy with length of document as this is a deliverable which is going to bring more money and probably more business. He believes that it has to have more info. I don't question him for his opinion as his objective is to get more business to company may be right from his perspective.
So what I did? Well first of all I consoled the poor tester who was feeling left out. A new joinee having feelings of not being able to live up to responsibilities of his first job. Besides this only option I could think of was questions, zillions of questions to be asked to client as we had least info about the project. I had a dedicated section added to doc about questionnaire which we had to know before having the testing assignment begun. He added a couple more pointers about exit and entry criteria for each phase of functional and performance testing. The document is sent to supervisor and review comments are awaited.
So what different would you have done in this situation?
Comments
Post a Comment
No spam only genuine comments :)