At the end of each Sprint, the Scrumboard is reset or wiped off, which is standard practice in Scrum. This allows the team to start fresh with the new tasks and updates for the next Sprint, ensuring clarity and focus on the current Sprint's work.
As a Scrum Master, Emily needs to focus on increasing the team's capability to articulate their challenges to find solutions and ensuring they understand Scrum processes and principles. While technical knowledge and understanding business value may be important, the primary responsibilities related to training fall within the scope of improving the team's process literacy and problem-solving capabilities within the Scrum framework.
To determine and document the difference between the current business capabilities and the final desired set of capabilities, a Gap Analysis is most appropriate. Gap Analysis involves comparing the current state with the desired future state to identify gaps in performance and areas for improvement. It helps in highlighting the discrepancies between existing capabilities and target outcomes, making it an ideal tool for this purpose.
In Scrum, collaboration is defined by the team working together towards a common goal with open communication and mutual support. These activities include discussing strategies, helping team members, and interacting with the Product Owner for clarifications. Option A, which describes the team independently deciding and assigning which Sprint to work on specific User Stories, involves less collaborative communication and decision-making processes, making it the least collaborative of the options listed. Other options involve direct and supportive collaboration.