Scrum is a popular Agile project management framework that has been adopted by organizations worldwide. A Scrum Master is a critical member of a Scrum Team, responsible for facilitating the process and ensuring the team follows Scrum practices. In this comprehensive guide, we’ll cover everything you need to know about being a Scrum Master, including the role and responsibilities, the skills you’ll need, and how to get started.

This Vlog looks at the topic of Emergence from its definition as a word and application in the natural environment. Emergence in Scrum is a key principle to delivery.

The Bytesize Agile Series is inspired by discussion tangents that arise during training. 3 Amigos the topic of today comes up during discussion regarding refinement of backlog items into a ready state.

The topic of my blog today is another one that is common on client’s sites. The use of the terms Showcase, Show & Tell or Sprint Review. In this situation, there is likely to be a broad mix of people fulfilling the Scrum Master roles.

Although I am going to use the term technical debt in this discussion. I am actively forming the opinion that this is the wrong term to be used both in how various assessments assess understanding and by practitioners in the agile community.

Within the Scrum process, there are eleven basic elements that make up the framework. 3 roles, 3 artifacts, and 5 events. Practitioners need to learn to apply and understand the principles behind these in order to obtain the full benefits of the Scrum process.

A review of the Scrum Guide section in the Sprint Backlog to consider and debunk the myth that the Sprint Backlog is a fixed Commitment by the Development Team.

One of the recurring Scrum Myth discussions I have with colleagues, teams new to Scrum and those attending training when comparing Scrum & DevOps relate to a misinterpretation of the following paragraph from the Scrum Guide.