Scrum is one of the most commonly used popular framework for implementing agile. Many frameworks can be used to implement agile, such as Kanban for example, but scrum has a unique flavor because of the commitment to short iterations of work. Scrum is an agile process most commonly used for product development, especially software development. Scrum is a project management framework that is applicable to any project with aggressive deadlines, complex requirements and a degree of uniqueness. In Scrum, projects move forward via a series of iterations called sprints. Each sprint is typically two to four weeks long. The Scrum Master is not the leader of the Team members, nor are they a project manager or team representative. However, the Scrum Master’s job is to serve the Team. They help to remove barriers to project, protect the Team from any outside conflict, and help the Team to adopt modern development practices.
History of Agile; started to gain traction in the early 90s as a reaction to the widespread failure of many large software projects. Back then, the software development process tended to be slow and documentation heavy. The first few months of a project would be spent detailing everything within a specification document, which would often end up being several hundred pages in length. Nobody ever read these documents, but when requirements changed, people ended up in dispute and claims of scope and cost adjustments ensued. People realized there must be a better solution, and so Agile was born.
In 2001 Schwaber worked with Mike Beedle to describe the method in the book, Agile Software Development with Scrum.] Scrum’s approach to planning and managing product development involves bringing decision-making authority to the level of operation properties and certainties.
In 2002 Schwaber with others founded the Scrum Alliance and set up the certified scrum accreditation series. Schwaber left the Scrum Alliance in late 2009 and founded Scrum.org which oversees the parallel professional scrum accreditation series.
Since 2010, there is a public document called The Scrum Guide that defines sort of an official version of Scrum and is occasionally revised.
Some responsibilities of Scrum Master:
- Supports the team rules and coordinates with other teams and protects the team from external and internal distractions.
- Scrum master is a facilitator and servant leader who encourages and demands self-organization from the development team.
- The Scrum Master guides and coaches the Team, the Product Owner and other stakeholders.
- Removes impediments so the team can focus on the work at hand and follow scrum practices.
- Leads team efforts in relentless improvement
- Facilitates meetings
- Builds a high-performing team
- Supports estimating
- Facilitates preparation and readiness for art events
- Protects developer team from disruption
What are the Scrum main roles?
What are the main roles of a Scrum Master and Product owner?
What are the advantages of Scrum master?
What is Sashimi and Impediments?
List out what are the artifacts of Scrum process?
What is the ideal duration for a Sprint?
Do you have any agile or scrum certification?
What are the benefits of scrum certification?
Is the Scrum Master more like a project manager?
What is Test Driven Development?
What is the role of scrum master in Scrum?
What is the difference between Agile and Scrum?
Why is the Scrum development less risky than waterfall method?
How do you define a user story?
How do you work with remote workers?
What is scrum poker or planning poker?
What is the objective behind holding a Sprint retrospective meeting?
How do you ensure that the Scrum team has an access to the stakeholders?
What is DOD? How is this achieved?
Do you see any disadvantage of using scrum?