Scrum hoax #3: Project managers should be Scrum masters

Scrum hoax #3: Project managers should be Scrum masters

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] While adopting Scrum, many organizations are facing difficulties to appoint the Scrum master. This role has a scope and mission that is disrupting the status quo of the hierarchical organizations, and one particular role: the project manager.   On the other side, Scrum is extremely often seen as a project management methodology, while it is clearly documented as a product development methodology.   From these situation, many organizations choose to appoint project managers as Scrum masters and believe their agile transformation is done. But is it a valid option? Let's have a look. [siteorigin_widget class="WP_Widget_Media_Image"][/siteorigin_widget] What is a project There is no occurrence of the word project in the Scrum guide, so it sounds awkward to see the problem persist. If we can understand the confusion from…
Read More
Scrum hoax #2: a Scrum Master is useless – Conflicts

Scrum hoax #2: a Scrum Master is useless – Conflicts

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] 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.  In this article we will review where the role of Scrum master lies regarding conflict resolution. [siteorigin_widget class="WP_Widget_Media_Image"][/siteorigin_widget] Many people believe the Scrum master is useless. On the other side of the spectrum, some people believe that he is kind of a manager of the team. Where is the truth? Last week, there was a conflict between two members in a team that I coach. Apparently the organization, including the team members, were expecting the Scrum master to take care…
Read More
Scrum hoax #1: Scrum prevents transparency

Scrum hoax #1: Scrum prevents transparency

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] 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 Scrum is blamed for that. It is a perfect opportunity to open this series of articles around the Scrum hoaxes. In today’s article we will discuss the black box syndrome some organizations encounter while implementing Scrum, and cover the possible causes and solutions. [siteorigin_widget class="WP_Widget_Media_Image"][/siteorigin_widget] Some times ago, I had a discussion with a senior product analyst about how Scrum impacted its organization. Like some people complaining here and there, he was not happy at all with the methodology. Bottom…
Read More
A branching strategy for Scrum using Git

A branching strategy for Scrum using Git

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] 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 sprints). The sprint backlog contains stories which represents the work to do in the scope of the sprint. At the end of the sprint the Product Owner will decide if the proposed product increment is accepted or not. It is common for Scrum teams to have strong difficulties with the branching strategy to apply to the product they are building. As a matter of fact, the expected level of collaboration on each story, the need to propose a shippable product increment,…
Read More
Should a Scrum Product Owner have technical skills?

Should a Scrum Product Owner have technical skills?

Agility
[siteorigin_widget class="SiteOrigin_Widget_Headline_Widget"][/siteorigin_widget][siteorigin_widget class="SiteOrigin_Widget_SocialMediaButtons_Widget"][/siteorigin_widget] 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 is more than a bunch of features. If you have seen conflicts between the Product Owner and the development team about a technical change (refactoring, framework updates are common ones), you are at the right place. In this article we will propose a review of what the role of PO consists in with a focus on technical aspects. We discuss then how it impacts the staffing for this position.  [siteorigin_widget class="WP_Widget_Media_Image"][/siteorigin_widget] The obvious All Scrum practitioners know that the PO is…
Read More