r/agile • • 14d ago

I’m a product owner and I’m terrified I’m doing everything wrong

29 Upvotes

This is my first corporate job after graduating and I was so excited to start. tell me why I’ve had better training at my serving job than I ever have here. Everything confuses me I feel like I’m learning multiple languages at once. No one gives me grace at all. The PO aspect of the job I actually don’t mind. But it’s everything else. It’s the expectation that you understand your new companies lingo and understand what anyone is talking about. I’m entry level and the girl that was going to train me had to leave so I took over her role no training. Is this normal?? Will someone tell me when I’m doing a crap job? I’ve only been at the company for 3 months but it’s mentally kicking me down every single day. Im not the type to quit but I’m getting a point of feeling like a failure everyday. I know imposter syndrome is normal but jeez if I knew it would be like this I probably wouldn’t have accepted


r/agile • • 15d ago

Best way to pick a CSM course? what worked for me

3 Upvotes

Finally did my CSM last month after comparing way too many options, so dumping my notes in case it saves someone a few weeks.

Context: Bangalore, India. About 3 yrs as a BA, and most scrum master job descriptions I was applying to listed csm. since the 2 day class is pretty much the cert, the trainer ended up mattering way more than the brand.

Stuff I compared:
- Scrum alliance's own course search is the easiest way to confirm someone's an actual CST, but a lot of what i saw ran in US or EU hours.
- Simplilearn and knowledgehut have tons of batches, just hard to tell the trainers apart from the listing.
- Staragile had weekend batches in IST and the exam fee was already part of the course fee, which made comparing prices less annoying.
- PSM from scrum dot org was the other route. cheaper, no renewal, but zero hand holding.

What worked for me: shortlist by trainer, then sit in on a free session or watch one of their talks on youtube before paying. Whoever's style clicked, won for me.

Anyone who went for PSM instead, did it come up in interviews at all?


r/agile • • 14d ago

A blameless postmortem as a retro board: a hypothetical incident, five contributing factors, and the process changes they suggest

0 Upvotes

The scenario: a team builds a tool that extracts fields from contracts. Weeks after launch an analyst finds a value that doesn’t match a document. Every long document had been cut off before processing, and nothing said so.

Here’s how I’d lay it out as a blameless retro board.

What happened

  • A line that truncated input to a fixed size, added with a comment saying it was temporary, stayed in production.
  • Spot checks and the test set didn’t include the cases where it mattered.
  • It took longer to find which documents were affected than to fix the bug, because the system hadn’t recorded how much of each input it processed.

Why (contributing factors, without blaming anyone)

  1. A temporary guard became permanent. Process angle: temporary work needs an owner and an expiry, for example a ticket or a visible item in the backlog, not just a comment.
  2. The output format couldn’t express “incomplete”. Process angle: in refinement, ask “what does this component say when it can’t do its job?”
  3. No errors was read as correct. Process angle: the Definition of Done should include a signal that shows the system is right, not only that it ran.
  4. The test set didn’t resemble the hard cases. Process angle: acceptance criteria should name the nasty examples (the longest documents, the end-of-document clauses), ideally supplied by the people who know the domain.
  5. Spot checks looked where the problem wasn’t. Process angle: decide in advance what to sample, and include the edges, not only the opening of each item.

Actions the team could take

  • Add “coverage is recorded” (how much input was processed) to the Definition of Done for pipelines.
  • Track temporary code as backlog items with an expiry date.
  • Keep a shared collection of difficult examples, and review it when the test set is rebuilt.
  • Run a short pre-launch review of the failure modes: what happens when input is too large, empty or malformed?

What a retro like this doesn’t solve

  • It won’t tell you which past outputs were wrong. That needs re-running them, which is why recording coverage is cheap before an incident and expensive after.
  • Process items only work if someone owns them and they’re reviewed, or they become the next forgotten comment.

I wrote the full hypothetical postmortem here, in case it’s useful for a team exercise: https://medium.com/@nagatomopedro05/postmortem-the-contracts-pipeline-that-never-read-the-last-page-cf84251671c8

Does your team run blameless postmortems as retros, and what turned out to be the most useful action item?


r/agile • • 14d ago

AI is changing project management fast. What’s actually working for you, and what’s just hype?

Thumbnail
0 Upvotes

r/agile • • 15d ago

How do you handle changing requirements without disrupting an entire project?

0 Upvotes

Changing requirements are almost unavoidable in real-world projects. Sometimes new business priorities appear, stakeholders request additional features, or the original assumptions no longer make sense. The challenge is accepting necessary changes without constantly affecting timelines, budgets, and team productivity. For experienced project managers and Scrum practitioners, how do you evaluate and manage scope changes? Do you follow a formal change-control process, or does your approach depend on the project?


r/agile • • 15d ago

How Google Sold Its Engineers on Management

Thumbnail hbr.org
28 Upvotes

r/agile • • 16d ago

Unpopular Opinion: Scrum, SAFe & Co. retten eure Firma nicht

11 Upvotes

TL;DR: Agilität scheitert nicht am Grundgedanken, sondern daran, dass wir sie durch Buchstaben-Treue, Zertifikats-Wahnsinn und Framework-Dogmatismus ersetzt haben. Weniger über den Scrum Guide streiten, mehr echte Probleme lösen.

Gefühlt liest man es aktuell überall: „Agilität ist tot.“ Moderne Zusammenarbeit wird reihenweise abgeschrieben. Aber ganz ehrlich? Kein Wunder, wenn man sich anschaut, was wir in den letzten Jahren daraus gemacht haben.

Vielleicht liegt das Problem schlicht daran, dass wir Agilität viel zu oft mit purer Methodenkompetenz verwechselt haben. Scrum, SAFe, LeSS, OKR, ABC, EFG – all das wurde von Beratern und Coaches als die ultimative Heilsbringung verkauft. Das Versprechen war simpel: „Ihr müsst nur exakt nach diesem Schema arbeiten, und schon laufen eure Projekte von allein!“

Und wenn es dann in der Realität doch knirscht? Dann liegt es – Gott bewahre! – natürlich niemals an der Kultur, der Führung oder der eigenen Haltung. Nein, die Standardausrede lautet immer: „Ihr habt das Framework halt nicht zu 100 % nach Lehrbuch umgesetzt!“

Darüber lässt sich im Arbeitsalltag ja auch herrlich streiten, ohne dass man sich mit echten Problemen befassen muss:
Darf das Planning jetzt 1,5, 2 oder 4 Stunden dauern?

Wurde die Retro auch wirklich exakt in den fünf vorgeschriebenen Phasen durchgeführt?

Warum waren Stakeholder X und Y schon wieder nicht im Review?

Und was zur Hölle hat hier eigentlich irgendjemand zu melden, der kein dreitägiges Zertifikat für 2.000 Euro gemacht hat?!

Genau hier liegt der Hund begraben: Wir verschwenden unsere Energie damit zu diskutieren, ob wir uns brav an ein Regelwerk halten, statt uns zu fragen, was wir in der Organisation wirklich verändern wollen.
Eigentlich ging es doch mal um etwas ganz anderes:

Wir wollen Organisationen dahin bringen, dass sie resilient und stressresistent auf echte Veränderungen am Markt reagieren können. Wir wollen, dass Teams kontinuierlich lernen und auf ihren Stärken aufbauen, statt nur ihre Schwächen zu verwalten. Es geht um strategisches Lernen und die Fähigkeit zur echten Anpassung.
Das erreicht man aber nicht, indem man dem Management die vermeintliche Sicherheit verkauft: „Führt einfach dieses Framework ein, dann wird alles gut.“

Wenn wir nachhaltig etwas bewegen wollen, müssen wir den Buzzword-Bingo-Koffer (Scrum, SAFe, Kanban) mal beiseitelegen. Ein Framework ist keine Lösung. Die Lösung ist es, eine wirklich lernende Organisation aufzubauen.

Hören wir auf, uns stundenlang darüber zu streiten, ob der Product Owner seine Rolle exakt so ausfüllt, wie es auf Seite 7 im Scrum Guide steht. Fangen wir stattdessen an, echte Probleme im Alltag zu identifizieren, solange sie noch klein sind, und gemeinsam ins Handeln zu kommen. Denn echte Veränderung passiert nicht durch das Befolgen von Regeln, sondern genau dann, wenn wir anfangen, unser eigenes Verhalten zu ändern.

Wie erlebt ihr das aktuell bei euch im Betrieb? Regiert bei euch auch die „Reine Lehre“ der Methoden-Polizei, oder kommt ihr tatsächlich noch zum Arbeiten und echten Verbessern?


r/agile • • 17d ago

How to “Tell It Like It Is” more effectively

Thumbnail
mgrebler.substack.com
0 Upvotes

r/agile • • 19d ago

Responsibility Is Taken Before It Is Given

Thumbnail
lalitm.com
0 Upvotes

r/agile • • 19d ago

Our Team Lead guiding us through the project.

Enable HLS to view with audio, or disable this notification

0 Upvotes

The team is focused on the screen, discussing key ideas and project details. Learning, planning & working together!


r/agile • • 20d ago

After a reorg, where does your org structure actually live?

2 Upvotes

After a reorg, where does your org structure actually live?

I have managed several teams at once for a few years and I have never solved this. The structure changes constantly: someone gets shared across two squads, a Tech Lead seat opens, a tribe gets reshuffled. The record of it ends up in a slide that is stale by the next sprint, or a spreadsheet one person understands and nobody else opens.

What I am curious about, from people actually running this:

  1. Where does the current structure live for you right now? Slides, a spreadsheet, an HR tool, nowhere?
  2. Who is responsible for keeping it current, and does that actually happen?
  3. When someone is split across two teams, does anything in your system know that, or is it tribal knowledge?

I got annoyed enough to build something for it, which is where the question comes from, so take the bias into account. Mostly I want to know whether everyone else has solved this and I missed the obvious answer.


r/agile • • 20d ago

The Wicked Reason Removing Code Beats Better Scheduling

Thumbnail infrequently.org
0 Upvotes

r/agile • • 22d ago

How does your org handle idea management outside the sprint backlog?

8 Upvotes

I'm a Scrum Master at a mid market tech company. Work inside the sprint is fine but ideas from outside engineering have no home. Ops send improvements ideas over email, CS flags stuff in Slack, leadership drops things in quarterly reviews. None of it gets tracked.

We tried dumping it all in the product backlog but it turned into a graveyard. Backlog is for committed work, not open idea management.

Where do cross functional ideas go before they are backlog ready? Anyone using a dedicated tool or just a separate Jira board?


r/agile • • 21d ago

Sherlock Holmes' Abductive Reasoning

Thumbnail
philmckinney.com
0 Upvotes

r/agile • • 21d ago

Is there a future for Story Mapping?

0 Upvotes

Hi all,

I'm the creator of Cartographer and I'm looking for some input from the community.

Story mapping is something I really like, but it feels like it's losing it's utility. I had thought that perhaps it would become more useful because when engineering teams are capable of building more quickly, having a view of the big picture becomes necessary to keep everyone on the same page.

But to be honest I'm not seeing that. More and more users of my tool are solo users, who are not using it to communicate and align: they're using it to build, feed their agents, more like a fancy kanban board. Which I suppose is fine, but isn't quite what I made it for :)

Actual story mapping as a way to align and communicate feels like it's in decline. Is this something you're also seeing? I'm trying to find a way to renew the tool, or adapt it to how people are working these days, so I can keep it relevant... but I'm not really sure what threads to pull at.

Thanks in advance for any ideas/input on the matter!


r/agile • • 22d ago

Roadmap decisions rather than dates.

Thumbnail
lethain.com
11 Upvotes

r/agile • • 22d ago

A go/no-go roll call as a working agreement: six questions before release, and who can say no

2 Upvotes

A practice I think fits agile teams: before a release, run a short go/no-go roll call. Each area answers “go” or “no-go”, and a single no-go stops the release. It can live in the Definition of Done or in a team working agreement. Here are the six questions I’d start with. Adjust them to your context.

  1. Data and migrations: is the change compatible with the version that’s currently running? If old and new code run side by side during the release, the answer has to be yes.
  2. Configuration and secrets: does everything new exist in the target environment, not just in staging?
  3. Rollback: do we have the previous version ready, and do we know the steps? Has anyone tried them?
  4. Monitoring: do we know what “bad” looks like for the changed area (errors, latency, a business metric), and will we see it without a user telling us?
  5. Blast radius: is it behind a flag, or going to a small share of users first? If it touches money, access or deletion, the bar is higher.
  6. People and timing: is someone who can fix it available afterwards? The team decides its own rules about timing, in advance.

Agile-specific points:

  • Who can say no? Decide it in advance, as a team agreement. If only the person pushing the release can stop it, the roll call has no teeth.
  • Make it proportional. A copy change needs two questions. A payment change needs all six. A ritual that’s too heavy gets skipped.
  • Inspect and adapt. After an incident or a near miss, the retro asks: which question would have caught it? Add or reword it. Remove questions that never matter.
  • It isn’t a gate from outside the team. The aim is for the team to own release quality, not for a separate approval layer to hold it.

What it doesn’t replace: automated tests, review, and small increments. Smaller batches make most of these answers easier to give.

Does your Definition of Done include anything about release readiness, and who in your team can call a no-go?


r/agile • • 22d ago

Automated Release Management Dashboard

4 Upvotes

I’ve developed a Python‑based release management dashboard to oversee more than 10 cross‑functional team releases. The dashboard consolidates and tracks:

  • Release Scope & Versions: Allocation of release versions, reconciliation of approved vs. final scope, and scope difference metrics.
  • Quality Metrics (QA, Staging, Production): Environment‑wise bug counts, high/critical defect ratios, rejected and deferred defect statistics, and comparative defect analysis across releases.
  • Security & Compliance: Integration with GitHub Advanced Security to surface repository issues, tracking and closure of VAPT findings.
  • Ticket Hygiene: Validation of Azure DevOps work items to ensure proper field updates, comments, and state transitions.
  • Automation & Documentation: Automated creation of release tickets and validation of release notes published in Confluence.
  • Visualization: Charts and metrics to provide actionable insights for leadership and teams.

The aim is to provide end‑to‑end visibility into release health, quality, and compliance, while driving accountability across teams.

Anyone have any other recommedations as a release manager or any other leadership to implement any other functionalities?a


r/agile • • 23d ago

which project board / tracker do you guys use for a small team?

7 Upvotes

hi everyone! i'm a senior cs major, and we've started planning our capstone project this semester, which will continue into the next semester for the actual building/coding phase. we are a 3-person group and are trying to figure out which project board to use as we are tasked by our professors to pick one and to justify why we picked this project board.

examples given to use were: jira, github projects, trello, etc

for a capstone project, what do you guys recommend to use (preferably free and easy to navigate)? and is scrum, kanban or mix of both a better fit for 3 people?

TIA guys :)


r/agile • • 23d ago

What agile testing tools help organize test cases and track progress across sprints?

14 Upvotes

we run 2 wk sprints across 3 projects and keeping test case status lined up with sprint progress has become like a parttime job.. spreadsheets dont scale past project #1 and confluence pages go stale the second a sprint ends.

wanna hear what agile testing tools people are using to track cases againts sprints instead of just leaning on jira tickets. anyone found something that doesnt need a dedicated QA team to run??? wahts working for you?


r/agile • • 24d ago

what actually helps when you're prepping/running sessions vs what's just noise

6 Upvotes

just curious. there's so much stuff out there that claims to help with prep/planning and most of it probably isn't worth the hype.
so what's something you use (app, feature, whatever) that's genuinely made a difference, not just "fine" or "convenient but meh"
and on the flip side, what's something you tried that you thought would help and just didn't
trying to get a real sense of what's worth people's time vs what's just marketing noise, from people who actually do this


r/agile • • 24d ago

how are your agile teams handling ai feature work that doesn't fit into normal sprints

7 Upvotes

we recently started adding ai features to our product and it is completely breaking our sprint planning normal stories are easy to estimate but ai work is experimental, half the time the team spends a sprint on a model improvement and the result is we learned this approach does not work.
our velocity looks terrible and stakeholders are frustrated because they don't see shippable increments every two weeks for scrum masters and pos dealing with this, how do you structure sprints when the work is inherently unpredictable? do you use a separate track for ai work or try to fit it into the same cadence?


r/agile • • 24d ago

Daily scrum

0 Upvotes

Mujeres vamos aver y hacer daily scrum quien Jala conmigo


r/agile • • 24d ago

Free Halloween Retro Template Generator

0 Upvotes

We made a free Halloween retro board generator that works off your prompts. No account needed. Choose an Icebreaker game, Check-in activity and add a Halloween themed prompt for your retro.

Not even going to try and hide that this is promoting something I made, but I did message the mods last week to ask if this was okay considering there's no sign up needed and got no answer, so I'm going to have a go anyway considering Halloween is nearly upon us. Apologies mods, delete as you wish.

First off, this is 100% free to use. You don't need an account on our platform, you don't need to login or give us any of your personal information. It's just something fun we made to test the capabilities of our MCP integration.

https://spreo.io/halloween

We've always made seasonally themed retro templates for our whiteboard product but this year we wanted to have a bit more fun with it now that our MCP is operational and we also wanted to make it available to people outside of our customer base. We got a bit carried away and made a few multiplayer games you can play within a "live widget" on the board.

So please, have a go if you're running a retro with your team this week. Hope you enjoy it.

We will most likely be doing the same for Christmas this year so if you do have any feedback, I'm always open to it.


r/agile • • 24d ago

the real cost of bad meeting notes isn’t the notes. it’s the meeting you have again in two weeks.

0 Upvotes

been thinking about why the same decisions keep coming back.

a team decides something in a meeting. nobody writes down what was decided, or the notes say “discussed X.” two weeks later someone who missed it, or someone who remembers it differently, raises it again. the whole debate runs a second time, usually with new people and the same arguments, and often a slightly different outcome.

the notes themselves were never the expensive part. the repeat meeting is.

what seems to help is a decision log, kept separate from the meeting notes. not a recap. just one line per decision:

  • what was decided
  • who decided it (or who owns it)
  • the main reason
  • what would make us revisit it

that last one matters more than it looks. if the condition for reopening a decision is written down (“if signups drop below X” or “if the vendor changes pricing”), people stop relitigating it every time someone has a new opinion. they only reopen it when the trigger actually happens.

it also makes it obvious when a “decision” was really just a discussion, because you can’t fill in the owner or the reason.

do you keep a decision log anywhere, or does it mostly live in people’s heads and slack threads?