Our startup is trying to save costs, so our Product Owner is also facilitating the ceremonies and managing the team's impediments. Is this a viable long-term strategy, or are we setting ourselves up for a conflict of interest that will eventually hurt the product quality?
3 answers
This is a major "Scrum Smell" and a direct conflict of interest. The Product Owner’s job is to maximize value and often push for more features, while the Scrum Master’s job is to protect the team's process, health, and sustainable pace. If one person does both, they will naturally prioritize the "What" (Product) over the "How" (Process). When pressure mounts, the PO/SM hybrid will likely ask the team to cut corners on quality or skip retrospectives to meet a deadline. This leads to burnout and technical debt. For a startup, it's better to have a lead developer act as a part-time SM than the PO.
Cynthia, I see your point, but in a small 4-person team, does it really justify the overhead of a dedicated Scrum Master? If the PO is technically minded and understands the importance of a sustainable pace, can't they just wear two hats until the team scales?
I've seen this fail every time. The team stops speaking up during retrospectives because they feel like they are complaining to their "boss" (the PO) instead of a neutral facilitator.
That’s exactly what’s happening here, Patricia. The openness in our retrospectives has completely vanished since our PO started leading them. We need to change this soon.
Andrew, the issue isn't the person's intent; it's the structural tension required for Scrum to work. The SM is supposed to hold the PO accountable for the quality of the backlog. It is very hard to hold yourself accountable objectively. Even in a small team, you need that "check and balance." If you can't hire an SM, let the team self-organize the facilitation and have them take turns being the "Guardian of the Process."