Scenario: I was asked by management if it is a good idea to add test cases to user stories before the sizing session. This will involve investigating the item, writing test cases, speaking to developers / architects to ensure areas are covered and adding more if needed.
During a normal sizing activity, the team will take an item from the backlog, discuss it briefly, and each member will mentally formulate an estimate. From a developers perspective, they don't build a prototype, they discuss the item and then size the item.
So after doing some research, I am not comfortable for the team to create test cases before sizing because there might be discussions in the sizing session and we might uncover issue with acceptance criteria or the priority might change or technologies might change, as we know the IT industry is always evolving.
I think this should be factored in with the sizing session. The test cases can be created after the item is pulled into the sprint.
Have anyone tried this before or do you have any concerns or ideas that might help.