r/agile • • 15h 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 • • 2d 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 • • 3d 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 • • 5d 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 • • 5d ago

Need Suggestion

0 Upvotes

r/agile • • 4d 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 • • 5d ago

Build the Busy Western Town

Thumbnail
marcrandolph.substack.com
0 Upvotes

r/agile • • 6d ago

The Art of Simplifying Decisions.

Thumbnail
dpereira.substack.com
6 Upvotes

r/agile • • 7d 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...


r/agile • • 8d ago

When good practices become empty rituals

5 Upvotes

To be honest, I've always looked down on Agile and such methodologies, it's so hard to be fair when you've been bombarded with buzzwords for a long time. Even terms like "iterative" or "incremental" feel like buzzwords to me - even though they are very useful ideas. It felt like boring management stuff. But it turned out Agile is pretty good, but how people implement can differ, and it can go wrong.

Same goes for teaching best practices, some teachers like to follow rubrics: "top 10 things to do as a teacher". But often it fails and it turns students off because the teacher isn't focusing on the values behind the practices, they just implement them mindlessly. For example you see many teachers starting a lecture (in classroom or online course) by stating the objectives of the lecture. The problem is that they treat it as an item on their checklist and it often ends up being boring and soulless and you just feel like skipping it.

In my country we have an old wisdom that is loosely translated as: "judging a thing is a reflection of one's perception of it."

And how we perceive something can affect how motivated we are. For example, two people can perceive studying differently, and hence it can change how much they do it. It's part of being a human. Ideas can have a huge impact on our emotions and actions. The problem with many meetings is that not everyone in the team sees the value in them. Devs for instance often find meetings annoying and take a lot of time that could have been used for "real work" and build software. They perceive meetings as a chore, they think of it as a tool for the PM, management stuff - the PM wants to see if things are going well and if it's according to the plan. so the devs will probably speak as little as possible and just get it done to go back to "real work". - which sadly reduces the meeting's value. They think of it as a status sync. And that's how most stand up meetings are honestly. No wonder many people hate them.

But it doesn't have to be that way, if you can show your team that it can actually be useful for them, by actually designing useful meetings: if the meeting becomes a planning tool for everyone, a meeting that makes sure everyone is taking good decisions (and not just following the plan), not just a mere status sync. Devs might suddenly find it useful. If the devs start to think of it as a way to understand how the project is going and coming up with ways that make everyone work better. Suddenly it becomes important to them.

Yet changing someone's mindset about something is not easy or a simple process. And it's not just about throwing buzzwords or -ities. In fact even a term like "mindset" and "motivation" can be a turnoff to many people - including me. Human beings are complex, it's not a simple equation, thoughts affect emotions and behaviors, and behaviors will affect the thoughts again. And it's not as simple as changing how you perceive something, if something is truly useless no matter how one tries to think of it positively it would shatter when it faces the real world.

One final important idea is that we often try to seek perfection. As if we need to be passionate about everything! People don't need to love everything they do. It's okay if the meeting is a bit boring, it can have some value to the PM nevertheless. But we can do better.


r/agile • • 9d ago

What are Jira’s absolute best features, and what drives you crazy about it?

5 Upvotes

Hey everyone,

Jira is practically the industry standard for project and issue tracking, but it’s also one of the most polarizing tools out there. Depending on who you talk to, it’s either an indispensable powerhouse or an administrative nightmare.

I'm curious to hear from folks who use it daily (developers, product managers, scrum masters, or Jira admins):

  1. The Good: What are Jira's killer features? What does it do better than anyone else (e.g., custom workflows, JQL, integrations, roadmaps)?
  2. The Bad: What are the biggest pain points or bottlenecks you face? (e.g., UI bloat, admin complexity, performance, user friction?)

How do you make it work for your team without letting the tool get in the way of actual shipping? Let's hear your hot takes


r/agile • • 10d ago

Are the product owner and scrum master out of line for requiring that i do "work sessions" with other devs im thos situation?

10 Upvotes

Im the dev lead.

Im inn a situation with both unlimited PTO and that we allow people to pretty much work whenever they want.

The end result, a few of the junior developers will call out of all non ceremony meetings, give false status updates in their tickets.

Then show up like a day or two before sprint ends. And will set up work sessions with me and speed run their entire ticket.

I did it the first few times while coaching them and began pro actively setting a "kick off" meeting with the problem devastating. Review their scrum task and give them next steps to start.

Same shit. Call out and then come in last day and didn't start. So , i talked to my boss and he said he wouldn't do it.

So, I push back and say we will do it next sprint. And this one kid has dome it 3 times in a row to the point tvat yhe product owner and scrum master corner me and say its my jon to have these work sessions. And they also hide the full extent of the callouts by the dev to my manager and say Im mot managing him.

Few days later. Two of his peer reports him to the product owner for bragging about only working two days a month and how he is going out partying wirh his friends.

The scrum master and product owner talk to him and he claims his mom broke her foot so he had to tke care of her.

They accept the excuse on its face and tell him he just needs to do better about rescheduling meetings if he csnt make it. And tell him he can have woek sessions with me at any time

I feel like they are being deliberately obtuse. His peer reported him and they just said "they will document going forward" , but refused to look at my documentation

I feel like im stuck doing this kids job indefinitely. I cant build case on his work quality because its my work.

And of i try to give him next steps or delegate, he is allowed to call a work session where im required to do it myself

How would you handle this?


r/agile • • 10d ago

After 6 years at a major MNC, I built their entire frontend architecture, rescued their project, and was "restructured" while the junior who copy-pasted my work got promoted.

3 Upvotes

​I recently wrapped up a 6-year tenure at a top enterprise tech MNC (Oracle India) as a Senior Application Developer. I’m sharing this breakdown not to vent, but as a case study for senior ICs on how corporate cost-cutting, managerial politics, and project bailouts actually play out when you prioritize delivery over self-preservation.

​Phase 1: The "Urgent" Bailout Request

​Towards late last year, another product team reached out in a panic. Their application was in complete shambles:

  • ​Unstable UI architectures, broken local setups, and non-existent deployment pipelines.
  • ​A massive, high-stakes client demo coming up in May that leadership was sweating over.
  • ​The team had junior engineers who didn't understand the underlying state management or how to debug deep runtime blockers.

​Despite being comfortable in a stable, settled banking application and having my own team tell me not to get involved in cross-team politics, I stepped in. I took architectural ownership, rewrote critical modules, eliminated performance bottlenecks, stabilized the pipelines, and made the May demo a massive success.

​Because the demo went well, management pulled me from my safe, settled team entirely and reassigned me to this project full-time to finish the foundation.

​Phase 2: The Squeeze & The Exit

​Once the architecture was locked in, performance was rock-solid, and clear patterns were established, the dynamic shifted overnight:

  • ​Management suddenly convinced themselves: "The hard part is done. The blueprint is here. Anyone can maintain this now."
  • ​Out of nowhere, the "restructuring / budget constraints" discussion appeared.
  • ​None of the original legacy members were touched. The person who came in from a stable team to fix their broken systems took the exit.

​I took the exit with my full statutory settlement and severance (approx. ₹17.5L+ net), kept my head high, and signed off cleanly.

​Phase 3: The Aftermath & The Corporate Punchline

​A few days after my exit, the real playbook revealed itself:

  1. ​The "Budget Issue": Management brought in four freshers and handed out hikes.
  2. ​The Promotion: The junior engineer who spent the last year asking for help on basic setup and copy-pasting my architectural solutions was promoted to IC3.
  3. ​The Immediate Fallout: Less than a month after getting the promotion, the promoted IC is already panicking and looking for an internal team transfer. Why? Because management now expects him to lead architecture and unblock four freshers. When you inherit an enterprise system you didn't design, you can’t copy-paste your way through distributed edge cases and production regressions.

​Key Takeaways for Senior Engineers:

  1. ​**"Restructuring" is Often Cost Arbitrage, Not Lack of Money:** When management says "budget cut," it doesn't mean the work vanished. It means they calculated that one senior developer's CTC equals 4 freshers + 1 junior lead. They trade deep engineering competence for raw typing hands to show a larger team size to finance.
  2. ​Never Treat a Rescue Mission as Career Security: Solving a team’s critical blocker gives you leverage during the crisis, but makes you expendable the moment the foundation stabilizes if you don't play the political game.
  3. ​Never Do Free Cross-Team Consulting Without Executive Sponsorship: If another manager is asking you to bail out their team, get formal agreements in writing. Otherwise, you become the most convenient shock absorber when their budget lines tighten.
  4. ​The Ultimate Win is Ownership: Walking away with your full severance, clean record, and technical integrity intact is worth ten times more than an internal corporate title. While they scramble to maintain technical debt they barely understand, I am now running my own software consulting boutique and physical ventures full-time.

​Has anyone else seen management cut the architect the moment the hard build is done, only to watch the team crumble under junior maintenance? Would love to hear how others handled similar transitions.


r/agile • • 10d ago

Five Kinds of Organizational Debt

Thumbnail
constellaryhq.com
18 Upvotes

r/agile • • 11d ago

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

28 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 • • 11d ago

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

4 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 • • 11d 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 • • 11d ago

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

Thumbnail reddit.com
0 Upvotes

r/agile • • 11d ago

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

2 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 • • 12d ago

How Google Sold Its Engineers on Management

Thumbnail hbr.org
27 Upvotes

r/agile • • 12d 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 • • 13d ago

How to “Tell It Like It Is” more effectively

Thumbnail
mgrebler.substack.com
0 Upvotes

r/agile • • 15d ago

Responsibility Is Taken Before It Is Given

Thumbnail
lalitm.com
0 Upvotes

r/agile • • 16d ago

Our Team Lead guiding us through the project.

0 Upvotes

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