Просмотр новости
Найдите то, что Вас интересует
Спутники
РН
SpaceX
Роскосмос
NASA
СпутникиРНSpaceXРоскосмосNASA
Image
I see it everywhere. In LinkedIn posts, in heated comment threads, and maybe most tellingly, in job descriptions that quietly list "Scrum Master / Project Manager" as if the slash were doing no work at all.The framing is always the same: Scrum Master versus Project Manager. Which one is better? Which one is being replaced? Which title should you put on your CV?And every time I see it, I think the same thing: we're asking the wrong question.The comparison that never quite fitsOn the surface, the comparison makes sense. Both roles hover around a team. Both care about things getting done. Both show up in meetings and seem to be, in some vague way, "in charge of the process."So people line them up head to head and try to figure out which is the modern version of the other. Is the Scrum Master just a Project Manager with a beanbag chair and a different vocabulary? Is the Project Manager a dinosaur that agile finally made extinct?Here's the problem. When you actually lay the two roles side by side and look at what a Project Manager is responsible for, the comparison quietly falls apart in your hands.Follow the responsibilitiesTake a solid, reference point for what a Project Manager does. PMI's PMBOK is as good as any. It describes the Project Manager's work across a set of management domains: integration, scope, schedule, cost, quality, resources, communications, risk, procurement, stakeholders.That's the job. Now here's the interesting part. Try to hand each of those to the Scrum Master.You can't. They don't fit.Instead, watch where they actually go when you drop them onto a Scrum Team:Scope goes to the Product Owner, who owns the Project Backlog and decides what's in and what's out. And how many work that goes into the Sprint Backlog lies on the estimation of the Developers. Cost and value land with the Product Owner too, as the person closest to return on investment.Schedule sits with the Developers, who forecast what genuinely fits in a Sprint, nudged by the order the Product Owner sets.Quality belongs to the Developers, through their Definition of Done.Resources are managed by the Developers themselves, because the team is self-managing and nobody hands them their tasks.Risk is shared by all three: business risk to the PO, technical risk to the Developers, empirical process risk to the Scrum Master.Stakeholders are the Product Owner's domain, with the Sprint Review as the formal meeting point.Notice something? The Project Manager's work didn't vanish. It got distributed.The part almost everyone missesHere's where it gets genuinely interesting, and where I think most of the debate goes wrong.Not all of that work landed on a person at all.Look again at the list. Integration, the tying-everything-together work, isn't given to anyone. It's absorbed by the framework itself, by the Sprint, the events, and the artifacts that hold the whole thing in shape. A big chunk of communication is the same. Nobody "owns" it as a task, because the Daily Scrum, the Sprint Review, and the Sprint Retrospective are already doing that job structurally.This is the elegant, easy-to-miss idea at the heart of Scrum: some of the coordinating work that a Project Manager used to carry on their shoulders got engineered out of the role and into the system. It didn't need an owner anymore. The framework became the owner.That's a genuinely different way of thinking about how work gets organised. And you completely lose sight of it if you're busy arguing about which job title wins.So where does that leave the Scrum Master?Conspicuously, the Scrum Master barely appeared in that list above. And that's the point, not an oversight.The most common mistake in this whole debate is treating the Scrum Master as a Project Manager in disguise, a person who quietly holds scope, budget, and schedule while pretending to be servant-hearted about it. They don't. The Scrum Master is accountable for the effectiveness of the way the team works, not for the scope of what it builds or the money it spends. Concretely this means that anything that goes wrong that endangers the empirical process (if no one does it) it is up to the Scrum Master to make it transparent so that it could be inspected and adapted. They serve the team and clear its path. They don't direct it.If you were looking for the Project Manager hiding inside Scrum, the honest answer is: they're not hiding anywhere. They were disassembled on purpose.Responsibilities vs. accountabilitiesThere's one last piece of language worth slowing down for, because it captures the whole shift in a single word.In the Project Manager's world, these are responsibilities: things assigned to a coordinator who is answerable for making them happen. In Scrum, the equivalent word is accountabilities: they belong to the team, held collectively, not handed down to one person to chase.That's not a cosmetic difference. It's the entire philosophy in miniature. Scrum doesn't have a Project Manager role, not because the work stopped mattering, but because it refuses to concentrate that work in one person. It spreads it across the people doing the work and builds the rest into the process.The better questionSo the next time you see "Scrum Master vs. Project Manager" framed as a cage match, or worse, as a slash in a job title, try swapping the question.Don't ask which role wins. Ask: where did the work actually go?Answer that honestly and two things become obvious. One, you can't collapse a Scrum Master and a Project Manager into the same person without quietly breaking the model. And two, you'll understand Scrum far more deeply than anyone still arguing about the titles.The work didn't disappear. It just stopped belonging to one person. And once you see that, you can't unsee it.Hope this helps?
Image
Kiwii is a Singapore-based training company that brings world-class Agile and Scrum training to the vibrant business community of Singapore. As an official Scrum.org Training Partner, Kiwii is among the few globally licensed to offer the full suite of Scrum.org certified courses. Our trainers turn learning into an experience through interactive sessions with posters, games, and practical tools. Kiwii’s mission is to spark curiosity, energize minds, and grow juicy ideas that help people lead, collaborate, and deliver value together.
The potential is in YOU. We're here simply to help you unlock it. Check out our Scrum.org courses in Singapore here.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | Scrum Isn't for Stormtroopers | 0 | 15.26 | 28-07-2026 |
| 2 | No Manager in Scrum? | 0 | 13.2 | 20-07-2026 |
| 3 | Der heimliche Feind jedes Product-Owners: 5 Mythen, die Karrieren ruinieren | 0 | 15.23 | 27-07-2026 |
| 4 | How Should I Get the PSM-AI Essentials Certificate? WITH or WITHOUT a Training Class? | 0 | 18.59 | 15-07-2026 |
| 5 | Flow Metrics in Python: 3 Scripts for Ensuring Transparency | 0 | 14.98 | 23-07-2026 |
| 6 | AI Interview Agent for Scrum Master and Product Owner Readiness | 0 | 8.4 | 21-07-2026 |
| 7 | Do Inicio ao Empreendedor - A Evolução da Carreira de Product Owner | 0 | 11.1 | 24-07-2026 |
| 8 | Understand Yourself Deeply: Why Scrum Masters Decide to Learn AI | 0 | 10.94 | 27-07-2026 |
| 9 | Scrum Kumbaya | 0 | 16.01 | 13-07-2026 |
| 10 | Wie drei Jira-Spalten Release-Prognosen sabotieren – und wie Scrum Teams ihr Board reparieren | 0 | 11.71 | 28-07-2026 |