Microsoft TFS (Team Foundation Server), is a software tool used for managing a team and their code.

It's a combination of a version control system (VCS), an issue tracker like Jira, and a limited application
lifecycle management (ALM) tool.
https://www.youtube.com/watch?v=9MRbY8RqQdU
Sprint – Iteration or a period of time you plan and build the work or the increment.

Sprint Planning – Sprint is kicked off with a planning meeting. You all meet and decide what you want to
build in the Sprint and start building it.

Daily Scrum – Daily stand up call for the team to chat about what work has been done and how to get
one step closer to Sprint Go. 10-15 min call (What, What and Issue).

Sprint Review – To show the product increment to the product owner and get their feedback and then
feed this back into the product backlog and build future sprints.

Retrospective – Whole team gets together and retrospects and adapts the process. What went well and
what didn’t go well and try to improve things in future.
Step1: Initial Meeting – Figure out the Product Owner and Scrum team

Product Owner -> Who owns, what he/she wants, has the power to make a decision, fund the project
and is available for discussion

Step 2: Backlog Construction

Steps in TFS
1. Go to TFS, create a Project

2. Click Product Backlog Items

Challenges for a Scrum Master

1. Lack of Agile training for team - As the Scrum Master is meant for the team,
it’s a responsibility to make sure all your team members have foundational Agile training.
This is one of the most problem faced by Scrum Master.
2. Managing Role Expectations - Many organizations, as well as the upper
management, confuses the role of the Scrum Master with a Project Manager. However,
the most important thing that we all should know is that the Scrum Master is a Scrum
facilitator for a team as well as an organization.
3. Handling urgent change requests - We can handle the change requests at
the end of the sprint or at the start of the Sprint but not in between. However, in a
 practical world, we see Product Owners/Customers/Stakeholders coming up with an
urgent change requests or bugs.
4. Distributed teams – teams distributed geographically - there are
sometimes delays, network issues, cultural or regional issues, different Time Zones,
different working hours, it is always difficult to get everyone connected and
collaborate/communicate with everyone.
5. Keeping everything Time-Boxed - For example, the Daily Scrum event
should not exceed 15 minutes, but in reality, we see team members start discussing their
technical difficulties and the meeting goes longer than the allotted time. It’s one of the
most common challenges for any Scrum Master.

http://mlapshin.com/index.php/scrum-quizzes/sm-learning-mode/

https://mlapshin.com/index.php/blog/scrum-questions/

https://www.techagilist.com/practice-exams/psm-i-practice-test/psm-practice-exam-practice-mode-
questions/

https://www.thescrummaster.co.uk/assessments/professional-scrum-master-i-psm-i-practice-
assessment/