Sprint Retrospective often becomes very ineffective and often painful as the Scrum Team struggles to find ways to improve. Read this article on how Scrum Master can help with effective Sprint Retrospectives

Scrum Guide says that, the purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. In order for the Sprint Review to be effective, we need to focus on how to get most useful feedback about the increment. In this article we see how the Scrum Master can help the Scrum Team to prepare for and conduct this event in such way that we can get the best feedback.

Visit Blog Home Agile Estimations with Planning Poker This article discusses how Agile Estimations work with Planning Poker. Planning Poker is a collaborative estimation technique used by many Agile Team. This technique helps to determine the relative effort required...

Only Developers are mandatory in Daily Scrum. Then how can Scrum Master help where are not even required? That is the focus of this article.

This article describes common challenges faced by the Scrum Master along with some suggestions on how to approach these challenges.

Scrum Guide says, “The Product Owner is one person, not a committee.” However, many times, teams often seem to want multiple People acting out as a product owner for multiple teams. This usually happens when especially when product starts getting bigger and more complex. In this article we will discuss why the Scrum Guide says Product Owner is One Person and NOT a Committe.