Final answer:
Rob should review QA feedback, address the issues with the development team, and resubmit the improved user stories to QA for re-evaluation, while maintaining clear communication.
Step-by-step explanation:
If Rob has had two of the team's user stories rejected by the QA team during the promotion of a new software release, there are a few steps he should consider taking to address the situation:
- Firstly, Rob should review the feedback from the QA team to understand the reasons for the rejection of the user stories. The feedback could include bugs, lack of compliance with requirements, or other quality issues that need to be addressed.
- Rob should then work with the development team to resolve the issues identified by QA. This could involve fixing bugs, refining the stories, or making other necessary changes to ensure that they meet the desired quality standards.
- Once the issues have been resolved, Rob should resubmit the user stories to QA for re-evaluation. It's important to maintain open communication with QA to prevent further rejections and to ensure that the stories meet both the team's and QA's expectations.
By taking these steps, Rob can help ensure that the user stories are brought up to standard and are included in the final release, contributing to the overall quality and success of the project.