We just recovered from getting an entire Team inadvertently zapped. We had an experienced team member pressed into the role of an SM, so they received Planning Level Admin permissions per company policy. They inadvertently managed to delete their own team. We recovered, but it is EXTREMELY easy to do this - just hit the Delete menu item, hit the Delete button - and it's gone.
Since TEAM is a foundational element of any agile approach - particularly scrum - it should be difficult to dispose of a team - particularly one with a rich history of existing work and portfolio items. Even a second warning - are you sure you want to get rid of a TEAM?
It shouldn't be easier to get rid of a team with features than it is to get rid of a feature with stories attached.
by: Noel S. | 2 months ago | User Interface
Comments
We will look into this requst