|
| Total Answers and Comments: 4 |
Last Update: August 27, 2009 Asked by: sushkumar |
|
| | |
|
Submitted by: surendra_kumar Kalyani you have to understand the question first. in fact instead of answering the question you have raised the same question once again in a different way.
The question itself demanding the answer with some metrics to defend it.
The answer is, wheather it is the change in the technology being used OR change in the development schedule it should be updated in the test plan. If not the whole concept of preparing the TEST PLAN itself is not usefull. Test plan will also have all the time schedules mentioned in it w.r.t. the development schedules.which means it is highly dependent on the schedules commited by the Development team, so it becomes obvious to update the Test Plan also when there is a change in the Development shcedule to deliver the product in a timely manner.
As we all know the Test Plan is mainly made up of the elements like Testing Environment,Assumptions, Risk, Contigency Plan(mitigation plan),Effort estimation and Schedules,Hence its very obvious to update the Test Plan also for any changes in the Development schedules OR Technology, otherwise a Quality Product cant be delivered as per the schedule. For any successfull Deliverables proper Planing is most important, and if that plan itself is not properly done (or not properly updated) may end up in a mess.
If someone feels it is not required to Update the TestPlan for any changes w.r.t. changes in Technology and Development Schedules, Then it is not required to go behind the concept of Test Plan at all.
Above answer was rated as good by the following members: vk1978 | Go To Top
|