Any opinions about Scrum Master job roles? Is there any demand? What about certifications available in the market: CSM, PSM, SAFe SM do these make any difference in a career?

I'm a SM for a dev team and I am on the struggle bus.

This team was tasked with onboarding a new business orchestration tool; they hated it ("we can't build with it, the UI sucks, etc.") so we are reverting to the previous tool (they hated that one, too, but suddenly it's better) and we are rebuilding the solution that was already 80% complete.

The biggest issue is that when I ask them to provide high-level target estimates, they complain that they can't be expected to estimate their work. Excuse me, but these devs have a combined work experience of 15 years, and the QAs have 24 years - how do they not know how long it takes them to get work done? They often push back with "well, we don't have a client that's going to use this feature" but when we DO have a client, they act like it's no big deal to tell said client that we missed the go live date by three months.

I'm not asking for exact drop dead dates, but seriously, if I had a builder building me a house, he should at least be able to tell me what month I can expect to move in!

The teams in this department only do demos sporadically - most sprints, there isn't enough completed work to demo and it gets canceled. Lots of carryover, and this attitude is endemic throughout the entire department. I know am only one person, but my fellow SMs and I do have support from our boss (also pressure, because he understands the current culture but supports us trying our best to be change agents).

I am really hitting a wall and it's costing me professionally because the team's lack of progress is being interpreted as a lack of leadership ability on my part (not wrong TBH since all team failures are rooted in leadership) and it's preventing me from moving on to other projects.

If you have experienced similar issues with a team, please offer suggestions for solutions that have worked for you. I appreciate theory, but I am seeking solid, proven examples of success.

Appreciate this sub so much.

I’m not looking to argue but have more of a feeling on what I see as an issue and happy to discuss. I feel like the original intent of agile has been lost. It started with a group of pioneers in a room figuring out what was needed. They stated their, write down their vision and the manifesto was born.

Today we have scrum alliance and scrum.org, SAFE and now PMI has jumped in. I feel like agile became a business model and not who you are as an organization. Now people chase credentials, organization need consultants, and nothing seems to scale without rigid rules and dogma instead of just meeting people, teams, and orgs where they’re at.

Am I off base and need some realignment? If so, what would you recommend? Any podcasts, books, blogs?

Thanks for your help, conversation a guidance. I appreciate kindness as well. I just want to help people connect and teams feel empowered to take ownership of their work.

Cheers to a great week all!

I'm building gamified processes for Scrum and Agile. Tell me the first things that come to your head. Btw, in the comment there should be a gift for you...

I work as a SM contractor for a big financial company that is basically for US Veterans. Unfortunately, I am a contractor. I handled close to 5 teams at once. 7 teams at once. Now I have H1B, applied it before the 100K rule, I work from Nearshore, but office people are reluctant to send me over to USA. I filed my H1B externally.
any tips or suggestions to move to USA from mexico? I have good reputation from clients, exceptional feedback on LinkedIn and good client connection.

Hi all,

I made this simple app for planning poker, id love to get some feedback to make it better please..

I got tired of using sites that kept asking for creating acount and limited number of time we story point our stories..

www.planningpokersimple.com

Thanks for anyone for feedback!

I am hoping if anyone can help me.

I am going to be running the 2nd sprint soon with the sprint planning. I already the have the user stories that I created with the definition of done. I also have a whitenoard with sticky notes where the team is able to see their progress (in progress, blocked and completed), as well as it is updated to Ms Planner

I am just stuck in the loop where I don’t know how to break down tasks further since they seem high overview and how to track progress and accomplishments. Also, with the user stories, I don’t know how close to reality it is. I am new to the team and this so any help would be good.

The project is about moving Working on a IT project implementing a new inventory management system using Agile. We’re mid-sprint, I manage the PM side, and the team includes both internal staff and a vendor.

Hello fellow SM's

I need some career advice.

I started off my career as a developer and bounced around to different roles like release Manager, devops and then landed into SM.

What would you say is the next progression after being an experience SM? I feel a little stuck l right now.

Thanks

around january my commit pace started dropping. not because features got harder but instead i was spending more time getting PRs through the gate than actually developing. so i started tracking my past three months, 30 plus PR failures across my own commits. the reason wasn't what i expected

genuine regressions were the minority majority of it split across three patterns… flaky locators tied to DOM attributes that shift between deployments, environment-specific failures from configuration drift between staging and rollout that nobody formally documented, and tests asserting against implementation details rather than behaviour. that last one is the worst. refactored a transformation module in february, cleaner logic, identical output, four tests failed because they were coupled to intermediate state that no longer existed, the feature worked but the suite disagreed

a lot of these tests were written under automation pressure the team needed coverage numbers up, sprint had a TC automation quota, so tests got written fast. no time to think properly about selector strategy, assertion design, or whether the test was actually verifying behaviour versus internal structure the suite grew, the metrics looked healthy, and the underlying fragility got baked in quietly

that's what i've been committing against for three months

the invisibility of it is what actually gets to me. sprint metrics don't capture time spent re-running pipelines or diagnosing flaky failures. from the outside my velocity looked low…. the suite looked green. those two things were directly connected and nobody was looking at that relationship

started logging failure reasons instead of just counts. flaky infrastructure, environment drift, wrong assertion target, genuine regression. each one has a completely different fix and collapsing them all into a single failure metric is how this stays invisible for months

I am not sure what the fix looks like at the team level yet

Curious what Scrum Masters are making as I’m negotiating with my company’s HR on wage. Recently got promoted from Scrum Master Associate to a full Scrum Master, I currently make $76,000 annually but curious what the jump will be and what I should expect. Specifically, if any scrum maters could provide their salary in the Midwest region for financial institutions like Banks and credit unions. Specifically Wisconsin would be ideal but I’ll take any insight. Thanks all

We implemented Scrum and currently have:

A well-defined PO

Also introduced a “Project Owner” as the main client-facing role

Now we’ve hit a conflict:

👉 Who should run client ceremonies and own delivery?

We’re considering assigning this to a Delivery Manager — but that starts overlapping with the Project Owner and even the PO.

Straight to the point:

Who talks to the client on a daily basis in your setup?

Who runs reviews / client checkpoints?

Does the Delivery Manager actually handle this or not?

Does having a “Project Owner” make sense, or is it just another unnecessary layer?

No theory — looking for real-world setups that actually work.

I was a scrum master for 8 years and an agile coach for three. I often see questions about CSMs in particular. Ask away

I’ve been working on something for PMs and wanted to get honest feedback from this group.

After years of managing projects, one thing kept bothering me:

Even strong PMs (including PMP-certified) struggle with visibility outside their current role… and on the flip side, companies often don’t really know who they’re getting when they hire a PM.

It feels like there’s a disconnect between:
• Proven experience / certifications
• Actual access to the right opportunities

So I started building a platform called PMaaSHub — focused specifically on helping PMs showcase themselves and connect directly with businesses.

It’s still early, but I’ve opened it up to start bringing in the first group of PMs.

Before I take it any further, I’d really like to hear from people here:

👉 What do you think is the biggest issue right now for PMs — visibility, trust, or access to opportunities?

If you’re curious, here’s the site:
https://www.pmaashub.com

I’m not here to push anything — just trying to build something that actually helps and would value real feedback.

Hi everyone,

I’m a developer at a startup where the leadership is putting heavy pressure on engineering to increase "individual output."

To address this, a new process has been introduced:

1. Mandatory Absolute Estimation for Sub-tasks: Every single sub-task must have an absolute time estimate.（days）

2. Planning Poker for Time: We use Planning Poker to decide these daily estimates. Since our teams are cross-functional, the accuracy is often poor, as we frequently estimate tasks outside our core areas of expertise.

3. Individual Monitoring via Custom Tool: A custom dashboard has been built to track the "points/hours" completed by each individual developer.

I’m concerned that this approach may not lead to the intended outcomes.In particular, I’m unsure whether estimating sub-tasks in absolute time—and using that data to monitor individual performance—aligns well with Agile/Scrum principles.

I have a few questions for the community:

• Has anyone actually seen a system of "sub-task level absolute estimation" work to increase actual value or speed?

• How do you handle the inherent inaccuracy of using Planning Poker for absolute time (days) rather than relative complexity (points)?

• In your experience, what are the long-term consequences of this kind of individual metrics-tracking on team collaboration and code quality?

I feel like we are measuring "the weight of the plane to see how well it flies," but I want to make sure I’m not just being cynical.

Is there any logical or architectural justification for this approach?

I’ve been supporting a few teams that have heavily integrated AI coding tools, and something about our sprint planning feels off. We’re still using velocity the same way, for capacity planning and commitments but the actual work inside a sprint looks different now. Coding tasks move faster, but review and refinement can take longer because there’s more code and sometimes more iteration. So even if total velocity doesn’t change much, how that effort is distributed clearly has. I’m not sure whether we should be adjusting how we think about capacity, or if we just accept that velocity stays the same and the work shifts underneath it. Is anyone else rethinking this, or are you keeping things as-is?

Hi all, I'm trying to learn how Scrum teams keep project context from getting lost across sprints, handoffs, decisions, files, and ongoing work.

I'm especially interested in what helps people reconnect quickly with why something matters, what was decided, and what still needs follow-through.

I'm speaking with a few practitioners and also sharing a very early prototype with a small number of people to get candid feedback on whether this problem is worth solving and what actually feels useful in practice.

This is informal early-stage research, not a sales pitch. If you'd be open to chatting or trying something early, feel free to message me. Happy to send a small thank-you gift after the feedback.

Hi Everyone.

Well, I thought about opting for PSM I. However, after reflecting on myself, I now wonder whether or not I should reconsider my decision.

Having considered my recent activities and some training sessions for PSM 1, the thought that came to my mind is that maybe working independently and contributing by means of producing goods suits me rather than being merely a facilitator in a team environment.

Thus, I started considering that perhaps I should go ahead with the PSPO certification instead of PSM I, as I may find it more interesting.

Could someone who successfully became PSPO give some tips on the utility of PSPO for the position of product manager?

Does PSPO certification help you in interviews or work somehow?

How difficult was it?

Any recommendations for preparation?

Also, what are the experiences of those who became PSPO (PSM vice versa)?

As a Scrum Master at a large enterprise, I’ve spent years preaching the "Agile Gospel." I’ve facilitated thousands of ceremonies, managed endless backlogs, and watched "messy" teams struggle to hit a Definition of Done. We always blamed the same things: missing requirements, technical debt, or "bad vibes" in the sprint.

Then I started Vibecoding**.** For the uninitiated, it’s the shift from line-by-line syntax to natural language intent. You "vibe" the architecture into existence by talking to AI agents. Mind you, I'm a non-technical SM. I don't know how to code. I think it's cool and I envy those that are classically trained and can look at a console or file and read it like a book telling a story. It's amazing and is underappreciated.

Last month, I decided to put my money where my mouth is. I wanted to see if I could build a full-stack, enterprise-grade application from scratch. This involved complex database migrations, third-party API integrations, and a premium UI. In a traditional corporate environment, this is a 6-month project with a $500k budget (if we're lucky, let's be real here).

I built the core engine, the infrastructure, and the frontend in 12 hours. Perfect, no. Something an enterprise is going to actually pay for? Lol. This post isn't to make me sound like I cracked the Vibecoding nut and it's the next big thing. I'm no master product manager or an expert at that stuff. I dabble, but it was more just something fun to do and it helps me to connect to our devs better. I digress.

Here is what that 12-hour "Vibe Sprint" taught me about why our traditional human teams are often stuck in the mud:

The "V1" Trap: Resisting the Lazy Fix

When I finally got V1 running, I started user testing. Within minutes, I found a bug. In the old world, that would be a ticket. In the "Vibe" world, the temptation was overwhelming: Just tell the AI to fix it. Just type 'Fix the bug where the data doesn't load' and let it rip.

I realized right then that vibe coding is a double-edged sword. If I had just "tossed" that fix to the AI, I would have started the slow slide into spaghetti code. I would have been trading long-term stability for a 30-second dopamine hit.

Instead, I went back to the Refined Process. I stopped. I logged the bug. I took the screenshot. I documented the root cause and prioritized it in the backlog. I treated my AI agent like a Junior Dev that needed a perfect spec, not a magic wand. I could have gotten lazy and complacent, but I knew that would destroy the architecture I'd spent 12 hours perfecting. Discipline is the only thing that separates a "Vibe Product" from a "Vibe Mess."

Here is what that 12-hour "Vibe Sprint" taught me about why our traditional human teams are often stuck in the mud:

1. The "Definition of Done" is usually a lie

In my day job, "Done" is a moving target. Developers say it’s done when it builds. QA says it’s done when it doesn't crash. When I was vibecoding my project, I had an uncompromising DoD. Because the AI doesn't get "tired" or "bored," it didn't skip the unit tests or the database schema validation.

The Lesson: Most messy teams fail because their DoD is a suggestion, not a constraint. In a vibe-sprint, if the output doesn't meet the "vibe" (the specific requirements), the sprint doesn't end.

2. We over-complicate "Backlog Refinement"

We spend hours in refinement meetings arguing over story points. During this project, I used "Vibe Logic": I described the outcome, and my AI "Agentic Scrum Master" broke it down into Epics and tasks instantly.

The Lesson: We treat the backlog like a sacred text. It’s not. It’s a set of instructions. If instructions are clear enough for an LLM to build a working environment in 5 minutes, they’re clear enough for a human. If they aren't, the problem isn't the team. It’s the clarity of the intent.

3. "Velocity" is a vanity metric; "Flow" is everything

My project had a velocity that would make a consultant weep. But it wasn't because the "typing" was fast; it was because the feedback loop was instantaneous. I didn't wait 24 hours for a code review or 3 days for a server to be provisioned. I "bounced" the code between a Developer Agent and a QA Agent in 30 seconds.

The Lesson: Scrum isn't about moving tickets; it's about removing the "Wait Time" between development and feedback. A messy team is often just a team with high latency.

4. The "Finely Tuned Machine" vs. The "Human Mess"

By the end of the 12th hour, my app had:

• A modular backend architecture.
• A fully migrated database.
• Dockerized services for caching and data.
• Compliance protocols that are usually a nightmare to code manually.

I realized that this project wasn't just a piece of software; it was a perfect Scrum Team of One. The Bottom Line Vibecoding didn't make me a better coder. It made me a better Scrum Master. It taught me that when a team is "messy," it’s usually because the "Vibe" or the underlying architectural intent and communication is fractured.

If you can’t describe your product well enough for an AI to build it in a weekend, you shouldn't be asking a human team to build it in six months.

My project is live. My "traditional" corporate sprint? It’s still in refinement. I think I know which one I prefer.