I had an opportunity to work as a "Scrum Master" (SM) on one of my last few projects. It was lot of fun with challenges and i had great pleasure on doing it. Thought I would share some few things that i have learned from the team management perspective as a SM.
Well!, if you check the Wikipedia site, you can find the definition for Scrum master as ...
Scrum is facilitated by a ScrumMaster, whose primary job is to remove impediments to the ability of the team to deliver the sprint goal. The ScrumMaster is not the leader of the team (as they are self-organizing) but acts as a buffer between the team and any distracting influences. The ScrumMaster ensures that the Scrum process is used as intended. The ScrumMaster is the enforcer of rules and sprints of practice.
According to Scrum checklist book the definition of Team is
The team does everything to win the game – to deliver the product. The team is cross-functional. That means the full know-how to realize the product is located in the team. The team needs to understand the vision and Sprint Goals of the Product Owner in order to deliver potentially shippable product increments.
Few other things that i learned/referred/observed as a Scrum master for the Team were...
The above were my findings with the experience i have, so if you happen to find something wrong or different, please post it as your comment.
Filed under Project Management, Scrum | 1 Comment »
This looks like anti scrum to me when you have to delegate work. The developers should be able to pick from the sprint backlog as per their wish.