Test Case Review in Agile

Is it fine for a member of the team to review the work of another member ?

> They believe if that happens, tester's mindset aligns with the developer's mindset.

Why do managers see collaboration and alignment as a problem? Why shouldn't developers see tests, or even code in order to pass known test cases? What issue are the managers trying to solve, and why are *they* trying to solve it instead of the team?

It's absolutely fine, especially for the first Sprint. Your test case can be reviewed by any team member, not necessarily the developer(s) who implemented the user story. And it's a common practice (to do test case review) when it comes to complicated user stories.

Well. I have been having a tough time making them understand scrum values.

Test review, code review and any other types of review sounds like a good practice of communication and collaboration between the team members. It can even bring the right questions to PO before something goes wrong.
And it's not related to the sprint #, as the test cases are being created for every sprint.

Posted By Srikanth Vasudeva on 31 Oct 2016 02:24 AM
Well. I have been having a tough time making them understand scrum values.

I would phrase it this way to the Managers:

"I want to review my test cases with a developer, and hopefully find a way to automate as much of this testing as possible, to allow me more time to do exploratory testing and so that we will be better covered for automated regression testing in the future."

Is your definition of done different from the developer's? If so then there might be an issue with the story itself.

Some projects follow test cases sign off from development lead/poc. Rather getting approval for test cases, I would suggest to get approval for test scenarios/objectives or whatever you name that should be of higher level withoug getting into much details. I used to get test scenarios approval from Dev team just to make sure we both are in sync in the requirements. this will also help developers to understand the various scenarios they should have at back of their head when writing the code. therefore we can reduce defects and in turn saves time. You could give this feedback to your manager if he is not agreeing with you. but you should understand there is no pre defined test scenarios nor requirements in agile. everything can change over the course of sprint. Yeah so you can obviously change the scenarios or add more scenarios whenever required. have fun.