# some good starting points for a Scrum master to check when you join a new team#: 1. Which boards the team uses? 2. What iteration are you in now? 3. How long is the iteration? 4. What are the team velocity and capacity? 5. What are the epics of the product? 6. Is there a backlog? 7. Are there stories rollover? 8. Do Iterations have a goal? 9. Is the story descripted from the user perspective? 10. Is the story description understandable? 11. Is there an acceptance criteria? 12. What issue type are used in Jira? 13. What is the Workflow? 14. What Is the release schedule? 15. Is there DoD? 16. Are there any Scrum meetings that already scheduled? 17. What are the problems that the team members are facing in the day to day? 18. What works for your team and why?
Great points Franka Njeck . It's also very important to check,if 1. The team has a working agreement set. 2. If the team has retrospective conducted after every sprint, as this is crucial to reflect and adapt.
We tried hiring the best coach for a football team having the best players but we did not win the league
I'll keep this in mind
SAFe® Agilist | CSM® | CSPO® | Agile Expert
5moGreat points, additional suggestions: 1. KPI Metrics and reporting 2. Release schedule 3. Project roadmap to avoid the technical debt (Jira timeline can be helpful) 4. Deployment schedule. 5. Peer review and code refactoring sessions