The role of Scrum master regarding team conflicts Any activity done in group may create conflicts between individuals.Scrum, by proposing self-organized teams synchronized by ceremonies and pair-reviews, may bring to the surface conflicts within the team and outside the team. A common thinking is that it relies on the Scrum master to solve these conflicts. … Continue reading Scrum hoax #2: the Scrum master handles all conflicts
Fighting lack of transparency in your Scum implementation Better transparency is one of the key value proposition of Scrum and one of its pillar. Several parts of the framework are designed to help it and make sure to keep stakeholders aware of the progress. More often than not, this does not work as expected and … Continue reading Scrum hoax #1: The black box syndrome
A branching strategy in adequacy with the Scrum model. Scrum is a great framework. If you do not know it, you should check it out and then come back here ! Defining a branching strategy suitable for Scrum is not so simple, here is a proposal. Scrum is designed to develop product among iterations (called … Continue reading A branching strategy for Scrum using Git
The difficulties of dealing with technical requirements in Scrum In agile transformation projects, the position and scope of the Product Owner role is often source of confusion. Most agilists get that it is about translating user wishes into stories. Functionally it seems OK (thus it is not always easy to do). But a software product … Continue reading Should a Scrum Product Owner have technical skills?