r/agile • • 22h ago

Project Management is not Scrum Mastering

34 Upvotes

I have had a stint where I have tried some traditional Project Management.

They are completely different roles. So for anyone confused, here is how they are different :

Scrum Masters are focused on improving Agile ways of working, that means coaching teams how to implement the Scrum framework to deliver work.

Unlike Project Management, the role is not aligned towards tracking how the work is being delivered.

Which leads me to the PM role.

As a PM , I have had to :

Put together a project plan.
Track decisions being made in a Decisions log.
Track actions in an Action log.
Track risks, issues, dependencies in a RAID log.
Put together communication plans.
Reporting

After working in this way for a project , you start to see why it’s valuable to track things in this way. It gives Stakeholders clarity and confidence that a Project is being Managed. When key decisions are being made, and how the work is being distributed. In addition, when you do this role properly, you start to realise that it is indeed a full time job. My dev colleagues do not have the time to maintain these delivery artifacts and are often more concerned about the technical details. By having a PM, you help people to zoom out and objectively keep focused on the bigger picture.

I think the community needs to be clearer on the differences between the roles. It seems as though a lot of Agile Coaches have spent limited time doing PMing and are spreading misinformation about the value of it.


r/agile • • 1d ago

our retro has had the same action item for fourteen months

40 Upvotes

It’s “improve communication.”

It has survived three reorgs, two scrum masters, and a complete change of tooling. nobody remembers who wrote it. at this point it has more tenure than half the team.

every retro someone looks at the board, sees it sitting there in the “carry over” column, and says “yeah, still relevant.” everyone nods. we move on to talking about the build pipeline for forty minutes.

Last month a new hire asked what it meant. we looked at each other. nobody could say. we just knew it was important.

I’ve started to think it’s less an action item than a team mascot. if we ever actually completed it, I’m not sure we’d know who we were.

What’s the oldest action item on your retro board?


r/agile • • 22h ago

What is the best cert in this space

0 Upvotes

For people leading programmes and projects?


r/agile • • 2d ago

The Semmelweis Reflex

Thumbnail
mikefisher.substack.com
1 Upvotes

r/agile • • 4d ago

"Yes, by Friday" is quietly wrecking our sprints. How do you get honest pushback in planning?

24 Upvotes

A pattern I keep seeing in stand-ups and planning: a request comes in late (real-time sync, dark mode and "a small AI feature" by Friday), there's a pause, and someone says "yes." No trade-off, no re-plan. The ticket goes into the sprint, and the sprint is now quietly 140% committed.

I've started calling it Yes Debt. Every yes with no conditions borrows capacity from future sprints. You pay it back in carry-over, rushed testing or a 2 a.m. incident. Velocity looks fine until it doesn't.

Some of the yeses I recognise:

- The Optimist: "like, two days." It is never two days.

- The Hostage: the yes that really means "please, somebody, help."

- The Thumbs-Up: a single 👍 on a 900-word spec.

I think the ceremonies make this worse when people feel that "no" is risky: layoff anxiety, demos that make big work look quick, and video calls with nobody's camera on.

Two things that seem to help:

- A priced yes: "Yes, by Friday, if we drop dark mode." The trade-off goes back to the PO, where it belongs.
- When someone agrees too fast, ask: "What would we have to say no to?"

How do your teams surface trade-offs before planning practices that make "no" safe to say?

Longer write-up (Lots of Engineers Are “Yes” Engineers Now)


r/agile • • 3d ago

A 5-minute test for your session summary: can a fresh session tell you what was rejected, and why?

0 Upvotes

When a long session gets summarized (by you, by the assistant, or by a tool’s automatic compaction), the summary usually keeps outcomes: what changed, what passes, what’s next. In an article I wrote, I argued that it tends to drop the reasons, and especially the rejected options, which look unimportant right up until someone proposes them again.

Here’s a simple way to check whether that’s happening to your handoff. It’s my own adaptation, and I haven’t run it as a controlled experiment, so treat it as something to try.

The test

  1. Take the summary you’d normally carry into the next session (or whatever the tool produced).
  2. Open a fresh session and give it only that summary, no code access yet.
  3. Ask: “What alternatives were considered and rejected, and why was the current approach chosen?”
  4. Compare the answer with what you remember (or with your notes).

How to read the result

  • If it lists the rejected options and the reasons: your summary kept them.
  • If it answers fluently but the reasons are generic or not what actually happened: it’s reconstructing a plausible story from the outcome, which is the failure mode to worry about.
  • If it says it doesn’t know: that’s the honest answer, and it tells you what the summary is missing.

What I’d do with the result

  • Add a short decision record next to the summary: the decision, the reason, what was rejected and why, what’s still open, and the next step. Five lines is enough per decision.
  • Only record decisions a future session could reasonably propose the opposite of.
  • Remove or mark superseded entries, because a stale record that confidently says the wrong thing is worse than none.

Limits of the test

  • A model can sound convincing without the information, so judge the answer against your own knowledge of what happened, not by how fluent it sounds.
  • One run proves little, and outputs vary.
  • It doesn’t tell you whether the assistant will use a record once it has one. A clear record improves the odds, and doesn’t enforce anything.
  • For short sessions and throwaway scripts, it isn’t worth the effort.

The article goes through three claims with the strongest objection to each. I’m the author, and it ends with two resources of mine on Claude sessions (one free, one paid), so treat the link as optional: https://medium.com/@nagatomopedro05/what-a-session-summary-forgets-three-claims-three-objections-dc35b96909d2

If you try the test, what did the fresh session get wrong about what was rejected?


r/agile • • 4d ago

Need test management software for agile team

5 Upvotes

Sprint review last thursday. PO asks if were good to ship.. two of us say yes, one says the checkout flow only got tested on staging .. nobody could really prove it eitherway

we have 5 testers covering 3 scrum teams, all on 2 week sprints. test cases are half in jira tickets and half in a google sheet someone made in 2022 that no body wants to touch. automation results just sit in CI and nobody looks unless its red

ive seen pracitest, testmo, testrail and a few others mentioned when people talk about agile test management software but what are u guys actualy using that survives a mid-print scope change??


r/agile • • 4d ago

James Shore: Measuring AI’s Impact on Delivery Speed

Thumbnail jamesshore.com
5 Upvotes

r/agile • • 4d ago

what’s the least painful way to push signatures to everyone

0 Upvotes

small team, no budget approved yet. group policy, a script, or just send people instructions and accept that half won’t do it. what did you end up with


r/agile • • 4d ago

"Walls" for remote teams

9 Upvotes

In reading through Jeff Patton's story mapping book, he highlights the value of using walls to display story maps, "vacation photos", etc.

It got me asking: How can we reproduce that sort of passive interaction with concepts in a remote setting?

I'm curious if anyone has found ways to put story maps and stories in places where people may inadvertently gaze at it for a while or accidentally start pondering what the team is working on.

I believe there's no substitute for pen and paper and real world environments, but here we are running remote teams so I'd like to make the best of it.

Has anyone found something clever?


r/agile • • 5d ago

Training and building agile capabilities

10 Upvotes

Hi All

I am working on creating training for my business users as no matter what, they go back to thinking in a traditional way.

We have lost a couple of POs, SMs and Project Managers, so I am worried that everyone will be back to their old ways.

Can you please give me guidance on how do I go about building agile capabilities within business? What innovative ways through which I can train? E-learning modules and videos no one seem to care :(

Thanks for your help.


r/agile • • 4d ago

Why I Still Believe in Mentorship

Thumbnail
endler.dev
0 Upvotes

r/agile • • 5d ago

We don't plan anything and it drives me nuts

16 Upvotes

Ingredients: Small dev team, Kanban and one vibe coding product manager. 

We supposedly have a weekly planning, but the PM just brings up the same high level roadmap that never changes. Nothing is ever discussed in detail in this meeting.

Then we go on with whatever is thrown at us in the week: high prio bugs, urgent customer request, some vibe coded PRs or random tickets (with AI generated).

As lead dev, I try to keep the quality up with all kinds of initiatives that I try to maintain. There are a lots of tech debts that I now track and try to reduce on the side. It never gets planned because there is no planning.

Three weeks ago the tech debt that we knew existed for months got collected in a big incident, because the team did not plan or execute the reduction in time. Amazingly we got out of the situation in one piece somehow, but we got really close to paying a high price.

So, I realized I don't want this stupid workflow anymore. This team is in dire need of some planning to get priorities, features and tech debt straight..we need some good old project management, at least thats my stance.

But tbh I don't see my current manager capable or willing to do so. To make matters worse he is an AI advocate. He is reluctant to take responsibility in the recent incident, blames the developers and doesn't see planning or management as the cause but rather some unimportant details in the observability. The most shameful thing was, in the post mortem of said incident he came up with a lot of suggestions what the devs have to fix, but never questioned his role or process. 

How can I convince him and the team that we gotta do something about that planning and priorities?


r/agile • • 5d ago

Hierarchy Exists

Thumbnail
kore-nordmann.de
0 Upvotes

r/agile • • 5d ago

How refactoring almost ruined my marriage

Thumbnail
manager.dev
0 Upvotes

r/agile • • 6d ago

Pm2 agile - european agile methodology

0 Upvotes

What do you think of the EC's PM²-Agile methodology as an extension of the classic PM²?


r/agile • • 7d ago

Product Owners: What do you actually need on your Jira dashboard?

0 Upvotes

I’m building a personal dashboard on top of Jira data, primarily for Product Owners.
I’m not a PO myself, so I’d like to understand what information you find most valuable in your day-to-day work.
What do you want to see first when opening your dashboard? What metrics, views or warnings help you make decisions or spot problems?
And what do you currently miss in Jira?


r/agile • • 8d ago

Does anyone else find context switching harder than the actual work when juggling J1 and J2?

0 Upvotes

The coding itself isn't always the hardest part.

It's going from a J1 architecture discussion straight into a J2 standup, then jumping back into another meeting where people expect you to remember decisions from last week.

Different projects, different terminology, different priorities, and sometimes overlapping calls.

I've been exploring this problem while building CatchMeet, particularly how an AI assistant could keep track of meeting context and surface relevant information when you need it rather than making you search for it afterward.

But I'm wondering what works for people who have been doing OE for a while.

Do you keep separate notes and workflows for each job, rely on meeting summaries, or just get better at switching contexts over time?


r/agile • • 11d ago

Can a Project Manager act as Scrum Master?

20 Upvotes

Hello lovely folks

A simple question, we don’t have Scrum Master and there is no budget or inclination by seniors to hire Scrum Master. We did have them in past but now the role doesn’t exist anymore.

We do have Project Managers and now the expectation is that Project Managers perform the responsibility of Scrum Master. Is it realistically possible? What could go wrong?

And if it is possible, what training would be needed?

Thanks, appreciate your response.


r/agile • • 10d ago

Need Suggestion

0 Upvotes

r/agile • • 10d ago

AI-empowered Leading SAFe cert?

0 Upvotes

Hi all - I need to get this Leading SAFe cert for a contract position, ideally within the next 48 hours. What are the must know tips/resources for making this as easy as possible?

For context, I am registered for a 2-day class starting tomorrow. I have worked in Agile software development for 8 years and am familiar with SAFe concepts (PI planning, etc). I recently studied for and passed my PMP.

Thanks!


r/agile • • 11d ago

Build the Busy Western Town

Thumbnail
marcrandolph.substack.com
0 Upvotes

r/agile • • 12d ago

The Art of Simplifying Decisions.

Thumbnail
dpereira.substack.com
7 Upvotes

r/agile • • 12d ago

Integrating non tech teams in agile wow

3 Upvotes

Anyone got any experience integrating non tech / non agile teams into an art workflow wise? I accepted a CPO role in a fairly small art within the financial sectors - leading 8 teams with about 150ish fte:s focusing on data and analytics. We focus on setting up data products and for reporting and analytics needs across the company. Issue is that two of the teams (containing data owners, specialists and data architects) historically have not been working according to safe even though they are a part of the art, and as a consequence we keep running into problems at all stages of development. They very much resist any attempts at switching to an agile wow, prefering to funnel their requests via team manager and with little to no jira transparency or other follow up methods. Team is owned by a separate unite linewise so no formal way of forcing a move either. Anyone have any experience of a similar situation and what would be a good approach to consider? I mainly try to identify common win/wins areas to start working with to bring teams closer, but still met with extreme reluctance...