The following protocol is to be followed when defining a Test Plan in order to avoid the deletion
There is no way to manage the delete permissions separated from the edit and creation, but there is a work around related to the iteration/Area of the test plan
Step 1- Create a separated area for suggested Test Plans, in this area the plan is inactive (as is not approved yet) and can be created by each one of QA team.
The un-active state avoid the deletion of the Test Plan
In this area QA members only can work and the plan is related to the area only.
Step 2- Move the Test Plan to state active under Approved area
Once the Test Is created the QA manager will approve and move to active and to the approved area
In this area the QA members are unable to delete the Test Plan
Pre-requisites:
Define the areas, associate the permissions
Let's do it:
From VS2010, under Team>>Settings>>Areas…

In Areas Dialog define the Areas ( And/ Or you can choose the Iteration)

Define for the QA Team, the proposed and approved security issues



Step 1-
Create a new plan (as QA member)

Create a Test Plan (Area will be default, so you need to be able to add to Area)


When you try to changed to approved and save it...


You get the appropriated message
Then the team leader moved it to approved. When the QA member try to delete we see is unable to do it



Limitations:
This is a workaround and not the expected behaviour
תגים של Technorati:
Team System,
Test Plans , but it works, if the area issue is not enough you can play with the iteration issue, the state (inactive) is not strong enough and a Test Plan can be deleted even in this state