A Sprint (or iteration) is the basic unit of development in Scrum. The Sprint is a timeboxed effort; that is, it is restricted to a specific duration. The duration is fixed in advance for each Sprint and is normally between one week and one month, with two weeks being the most common.
https://en.wikipedia.org/wiki/Scrum_%28software_development%29
Humility – Lastly, I agree with most other scrum theorists that the scrum master should be humble. I think this is called ‘servant leadership’ by them, but I’d chalk it up as just good leadership skills. A good SM won’t boast or take credit for other’s work, but place credit where it is most surely due.
https://anagilestory.com/2011/09/03/who-should-be-the-scrum-master/
Scrum Master Summary. So there you have it: The Scrum Master plays a very different role to that of the Project Manager, and the Lead Developer. You can be a Scrum Master and a Project Manager but only on separate projects. An Agile project is defined by the Product Owner and developed by the team. The Scrum Master is there to facilitate, make sure that Agile processes are being followed and to support the Product Owner and the team.
https://www.codeenigma.com/community/blog/scrum-master-not-project-manager
The picture that emerges for a good scrum master candidate is a leader; not a secretary or a bureaucrat. My view on this differs from traditional scrum thinking. Where they see a helper of the development team, I see the scrum master as an active, engaging and dynamic person with a big stake in the game.
https://anagilestory.com/2011/09/03/who-should-be-the-scrum-master/
A key principle of Scrum is its recognition that during product development, the customers can change their minds about what they want and need (often called requirements volatility), and that unpredicted challenges cannot be easily addressed in a traditional predictive or planned manner.
https://en.wikipedia.org/wiki/Scrum_%28software_development%29
The Scrum of Scrums is a technique to operate Scrum at scale, for multiple teams working on the same product, allowing them to discuss progress on their interdependencies, focusing on how to coordinate delivering software, especially on areas of overlap and integration.
https://en.wikipedia.org/wiki/Scrum_%28software_development%29
Scrum is a feedback-driven empirical approach which is, like all empirical process control, underpinned by the three pillars of transparency, inspection, and adaptation. All work within the Scrum framework should be visible to those responsible for the outcome: the process, the workflow, progress, etc.
https://en.wikipedia.org/wiki/Scrum_%28software_development%29
Scrum is facilitated by a Scrum Master, who is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables. The Scrum Master is not a traditional team lead or project manager, but acts as a buffer between the team and any distracting influences.
https://en.wikipedia.org/wiki/Scrum_%28software_development%29
The role of the Scrum Master is more a coaching and facilitation role, a role that sits between the project and the customer. The Scrum Master doesn't manage the team that produces the work, instead he supports the Product Owner, coaches the team and makes sure that Scrum processes are adhered to.
https://www.codeenigma.com/community/blog/scrum-master-not-project-manager
This is where the Scrum Master plays a vital role. While Agile is becoming a part of many projects, there are still many who shy away from it, are nervous of it or just don't trust it. Often, they see the traditional Project Manager role as far easier to understand.
https://www.codeenigma.com/community/blog/scrum-master-not-project-manager
who is a scrum master
ScrumMaster is accountable for removing impediments to the ability of the team to deliver the product goals and deliverables.