When product owner express the userstories, scrum team asks for clarification for better understanding.What is the order of actions in sprint planning, is it that tasks of particular user story should be entered in in scrum board or acceptance criteria of the user should be defined first and then entering the details of develeopment tasks with the estimates derived? can you help me with this?
Some of our teams have struggled with not being able to complete the testing hours for stories in a sprint, and thus not reaching DONE for the story. One team has vollied up the idea of doing the development work in one sprint & sizing that then doing the testing in the next and sizing that. This doesn't seem like the best solution, but wanted input on others experiences. We also think the root cause could be that the stories are too big for the 3-week sprint duration. At this time we are not using any automated testing methods, but are working to begin this later this year. Please provide input & experiences. Thank you!