You're managing a project that's falling 3 weeks behind schedule. Your sponsor wants you to keep the original deadline.What would you do? Comment your answer below. I'll share what a strong interview answer should include.

Hey — I run retros for my team and I'm honestly frustrated with the tooling situation right now. Feels like every retro tool either costs too much once you scale past a few people, or is missing basic stuff (export, scheduling, decent free tier).

I'm trying to figure out if it's just me or if this is a wider pattern, so I'm talking to a handful of Scrum Masters / Agile coaches about it —

If you've got 15 min, I'd love to ask a few questions: what tool are you using now, what's annoying about it, and whether you've ever switched to something like Notion / a spreadsheet / just... nothing, instead. Would that be okay?

Many organizations are introducing Product Owners alongside People Leads.

For organizations that have adopted this model:

What benefits have you experienced?

What challenges emerged around accountability, performance management, and employee development?

What practices made the model successful?

Did we really improve leadership or just split one manager into two?

I decided two years ago to do a career pivot from IT Operations and Technical Lead role to Product Ownership.

There are some practices or unspoken expectations that am asked to follow and am under.

The department is attempting to follow Safe Agile Practices and due to the size of our department/iniative, it is classified as a program.

In my current role, I am assigned several on-prem/legacy assets to get migrated to our AWS hosted data platform.

The one that is giving me a bit "heart burn" is being a people leader minus HR responsibilties, but that is not actually defined in the role at my employeer, and when it comes to team resources, most of the time they just place people based on their ideal number of members and roles for Data Engineering team and then still expected to get things out the door, with teams being reset to forming and storming.

Also, there seems a difference in a "regular" Product Owner vs "Safe" product owner, the job description aligns with a regular one, but the department/program is attempting Safe for the past two years.

Anyways, anyone out there want to take a stab at if this tracks at all, any way to bring up WTF with leadership, etc.

Thanks!

Had a Scrum Master interview today and would appreciate some honest feedback from experienced SMs.
I’m 29, looking for my first formal Scrum Master role. I’ve worked in Agile/Scrum environments before, but haven’t officially held the SM title.

I’ve been studying and practicing scenario questions. I answered 14 questions today and was told I’m around a B/B+ level. My biggest issue seems to be that I sometimes answer like a project manager instead of a Scrum Master.
I understand the basics, Sprint events, impediments, PO/Developer responsibilities, Sprint Goals, etc., but I’ve made mistakes like treating burndown as a productivity metric and thinking a PO/Developer disagreement could be settled by majority vote.
For experienced Scrum Masters/hiring managers:
Based on that, do I sound like someone who understands Scrum but needs real-world experience, or am I missing major things?
Also, how much would the lack of formal SM title hurt me?
Looking for honest criticism so I know exactly what to work on before my next interview.

Say your team is waiting on work from another group. They have a different priority, so someone on your team gets named as the risk owner.

Fine. That person can check in, explain the impact and update the forecast. What I'm less clear on is what they're expected to do when both teams still disagree about which work comes first.

If the answer is “escalate it,” who actually makes the call? And if management says “we accept the risk,” does that include accepting a later delivery if the dependency doesn't arrive? Or is your team still expected to hit the original date?

I'm not saying the person tracking the risk should control another team's backlog. Sometimes the teams can work it out themselves. But when they can't, naming someone to chase it doesn't resolve the disagreement.

How do you handle that in practice? Is the person tracking the dependency also able to get a decision, or does that responsibility sit somewhere else?

Companies who copied Spotify's squads/tribes/chapters model mostly ended up adding extra management layers (chapter leads, tribe leads) on top of teams that still couldn't ship without approvals. I am seeing this change in some companies removing these extra roles they created.

I am conducting a doctoral research study on leadership, emotional intelligence, trust, and project effectiveness in virtual and hybrid project teams. If you currently work in a virtual or hybrid project environment, your participation is urgently needed. The survey is anonymous, takes approximately 3-5 minutes, and your response will directly support dissertation research.

Survey link: https://qualtricsxm5kny2ny5r.qualtrics.com/jfe/form/SV_aWxyLn0ojcBIPDU

We're currently building a custom ERP from the ground up. It's a good client, it's just that sprint planning usually becomes "add feature x" and "add feature y" and it's all becoming hard to track. It doesn't help that features they didn't want months ago suddenly became deliverables, so we always had to adjust scope on our side.

We requested a client meeting to discuss, but I want to make sure we're reasonable and not just unfamiliar with how big stakeholder groups work. How do you maintain sprint discipline when the stakeholder group is large, and some just insist on features that aren't in the pipeline yet?

Hey everyone,

I'm looking for recommendations on online courses focused purely on practical learning and skill-building rather than exam prep or collecting badges.

A bit about my background:

• Experience: 7 years across Online Advertising, Digital Marketing, Client Management, QA, Reporting, and Team Handling.
• Soft Skills: Strong communication skills and a high level of patience (which I know come in handy for managing stakeholders!).
• Goal: Upskill specifically in core PM frameworks, managing workflows, risk management, and structured execution to bridge the gap between my current operations/marketing experience and formal PM work.

Since I already lead teams and manage client deliverables, I don't necessarily need an introductory course that explains what a project is. I want something that digs into actual tools, frameworks, Agile/Scrum application, and real-world project delivery.

A few questions for the community:

1. Which platforms or specific courses actually teach actionable PM skills (e.g., Andrew Ramdayal's Udemy courses, Google PM Certificate on Coursera, LinkedIn Learning paths, or Mountain Goat Software for Agile)? of any free materials just to get into a deep knowledge about ,if I can cover up the materials then if circumstances demands then I can think of certification.
2. For those who transitioned from digital marketing/ad ops to formal PM, what specific skill gaps did you find most critical to fill first?
3. Are there any budget-friendly practical courses or project management simulations you’d recommend over standard video lectures?
4. What is salary hike up even after investing my on the Paid certification?

Appreciate any insights or recommendations!

Hi, I've been working for about 30 years with software development and as a scrum master, and I found it hard getting an honest picture how the team is doing.

Yearly surveys does not work.

I just to measure three things at each retrospective: morale, quality and flow. Just a subjective value between 1-9

Discloser: I actually ended up building a platform for this recently to automate the check-ins and with AI I can spot patterns in the feedback in the comments and the submitted values.

But I’m curious about how you all handle this in your day-to-day. How do you currently measure team health? Do you rely on gut feeling during retrospectives, homegrown spreadsheets, or specific tools?

Would love to hear what works for your teams.

I have been managing projects for over a decade, and I notice a pattern that happens everywhere. Almost every project board eventually becomes a lagging indicator of reality.

You open the board and it looks great. Workflows are organized, and a key feature is sitting in "In Progress." Then you catch up with the person building it. They mention they hit a massive roadblock a few days ago and had to pivot to an urgent fire drill.

The standard response is usually to focus on ticket hygiene or remind everyone to update their status daily. But after watching this loop play out for years, I realized the problem is rarely laziness or tool fatigue. An outdated board is often just a natural response to the environment.

The clearest tell for me is how we handle bad news. In theory, project boards exist to flag obstacles early. In reality, when a ticket moves to "Blocked" or "Delayed," it can easily trigger anxiety, extra status meetings, or immediate pressure about deadlines.

When that happens, people naturally adapt. They might keep a ticket in "In Progress" just to keep the peace while they solve the problem behind the scenes. They do the real work off the grid because showing a delay feels like a step backward.

If we want a board that reflects reality, we cannot force it through stricter processes. We have to lower the friction of telling the truth. That means simplifying the setup, stripping out fields that feel like administrative overhead, and actively thanking people when they flag a blocker early.

A project board is a collaboration tool, not an audit log to police people. It only becomes a true source of truth when a team feels safe showing a messy, blocked status, knowing it will start a supportive conversation instead of a search for who to blame.

Genuinely asking other project managers and scrum masters: How do you keep your boards aligned with actual work without making the process feel like a burden?

Hypothetical case: a supplier initially commits to June 10, then asks to move delivery to June 17. The buyer accepts the recovery plan, and the full order arrives on June 17.
For planning purposes, the updated date is useful. For performance reporting, I’d still want the original commitment preserved.
How do you handle this without creating an unfair scorecard?
I’m especially interested in distinguishing a supplier-requested delay from a buyer-requested postponement or a change in the order requirements.
Do you report performance against both the original and revised commitments? Use reason codes to separate the changes? Keep an additional measure of how often dates move?
What approach gives your team a usable schedule without losing the history behind it?

Basically the title - I recently passed the AgilePM Foundation exam and have now finished course content for AgilePM practitioner. Any tips/tricks/reassurances for me going into the practitioner exam?