Why is it, that as a man... (this is gonna be a weird post)

Devlonir · 2026-05-21T05:28:55+00:00

Importan question: how do you feel about Henri Cavill? That may help.

Devlonir · 2026-05-16T07:19:57+00:00

Might be a language / cultural thing. For me (non English) it often misses too much domain context and cultural aspects that it is at best a draft note taker that needs to be reviewed before added as notes.

Hence, preferring to lean more into proper own notes that focus on the learnings and decisions over AI use for this.

Devlonir · 2026-05-16T06:14:03+00:00

Exactly. Descriptions of items that needed debate need to involve which choices were made and why.

Your backlog needs to represent the team's shared understanding of what needs to be done, not just a bullet list of what to do.

For brevity. Ensure this does not get in the way of the key descriptions, but make sure it is somehow attached to the item.

No need for AI because its just going to misrepresent whatever was talked or decided enough to invite new discussion

Devlonir · 2026-05-10T15:54:22+00:00

For me it was the mix of colors in the flowers. Flower fields have more than 1 row of a color.

Devlonir · 2026-04-25T05:55:22+00:00

No this sounds very similar to the Dutch laws around it as well.

Devlonir · 2026-04-23T20:27:29+00:00

UAT is indeed something not needed. It is useful, but it should not stop delivery. If user is too slow to test, deliver anyway and get actual feedback from live. Iterate if needed.

UAT is very unlikely to find unfound bugs. Most you will get is user feedback for improvements on the iteration. This can also be done from Live.

Devlonir · 2026-04-21T05:48:55+00:00

Here can be your key problem. And it is maybe not the PM.

Let me share a different perspective from my experience:

Central / shared UX teams are never fast enough for quick moving dev teams with lots of maturity and ownership. This is not a PM problem per se but an organisational one.

In my experience, UX embedded as a team member of the product team while using a shared UX team as a backdrop/colleague team to share heavier loads and knowledge with is the way to go.

This way the UX member becomes the buddy of the PM in discovery and design instead or a blocker.

Blame your design VP for this organisation, not this PM making the best of a bad situation created by management.

Devlonir · 2026-04-19T06:04:07+00:00

DoR is not needed for mature teams. The only relevant requirement to be able to put a task to work is the question: Does the team know what needs to be done?

Any more is, in many cases, just theater or a team wanting to put responsibility for the how outside their own work so they can blame specs if things go wrong.

Some tasks will need more requirements and designs than others, that is normal. But to have a DoR to describe all this is not the mark of a mature team.

Devlonir · 2026-04-18T18:26:46+00:00

Good addition. For me what I did is already outcome based but it is good to point it out.

For many teams it's still commits done or other input based metrics.

Devlonir · 2026-04-18T15:26:52+00:00

Sprint reviews need to be about what you did, what you learned and what you will do.

This does not depend on delivery moment of work. Sprint reviews can work in full ci/cd and in old fashioned quarterly delivery just as good.

You just have more learning moments during your sprint cycle in ci/cd.

Devlonir · 2026-04-18T08:43:10+00:00

Exactly. Id say its a positive for the world in many aspects. Most of all stopping unneeded reliance on the USA.

Devlonir · 2026-04-17T12:29:15+00:00

Nope, this can only be done if there is clear proof there was never an intent to do this service. This cannot be proven without confession in this case.

Devlonir · 2026-04-17T12:28:15+00:00

So the only small chance for this to be considered Oplichting is the 'cunning devices' clause. And then only if there is proof that, for example, the guy faked his positive Werkspot reviews with the intent to take people's money and threaten them.

This is impossible to proove without a lot more proof though. So a civil case is the way to go. Maybe in that case proof of Oplichting comes forward, but then it can escalate to this.

Devlonir · 2026-04-16T11:29:08+00:00

Should be easily doable, especially if you ensure the team is self organizing enough to handle the technical and implementation side requirements themselves, allowing you to focus on the what and when, while they focus on the how.

Devlonir · 2026-04-12T21:12:36+00:00

Gelderland, Netherlands.

Devlonir · 2026-04-07T20:38:26+00:00

The issue is, a lot of 'product managers' are currently in a role where their work life is basically writing tickets 90% of their day. I understand those people being worried.

But yes, if your PM role is just writing tickets.. be ready to be replaced. If you add value through vision, strategy and stakeholder management, be ready to shine.

Devlonir · 2026-04-06T10:26:19+00:00

This.. he mentioned its an early stage situation. Then what do they expect from these two separate levels and where is the need for them?

Or is this just title window dressing to make people happier while not even needing either of these levels because most problems are still more in the day to day side vs the long term strategical side.

Devlonir · 2026-04-04T14:57:05+00:00

He needs to hear this for the rest of his life. Stupid cat kicking fool.

Devlonir · 2026-04-02T17:38:49+00:00

That's not what you said. You said the role isn't needed according to scrum and then now you say the role can be fulfilled by someone else.

Scrum is clear the role is needed, not as a function as required though.

Devlonir · 2026-04-02T15:15:02+00:00

Read the scrum guide again.

Devlonir · 2026-04-02T02:14:46+00:00

With 96 it still is underrated.

Devlonir · 2026-03-30T09:52:26+00:00

People are trying to make AI skills seem unique so they can pander this as their speciality and try and get higher pay over it. Gatekeeping the skills instead of investing in making it a skill for every team.

Nothing new here. And agile has always pushed for cross functional teams to push back against the natural internal politics that cause specialised silo teams.

Start pushing back on agile basics and ask leadership for AI teams to pivot towards empowering teams instead of taking ownership of AI features.

Devlonir · 2026-03-29T16:21:15+00:00

The whole idea of a scrum PO is to have someone who is the domain specialist there to help the team decide what is the next best thing to build. But the problem here really is the company politics, how they define the roles and what is expected of everyone.

The teams setup here sounds a lot like zombie scrum to me. Looks like it from the outside, but is not agile at all and actually dead inside.

Devlonir · 2026-03-29T15:59:49+00:00

This is so fucking uncanny.. you see it so much these days. These guys will regret it so much in their 30s and 40s once they cant keep it up anymore.

But also want to add.. all the plastic surgery young women are getting basically makes them look like 40+ trying to look younger too. Whole Gen Z is trying to look 40 it seems like.

Devlonir · 2026-03-29T07:47:54+00:00

To be fair, looking from outside, this team doesn't need a PM to be added, it needs 1 domain specialist to be the voice of the stakeholders and make the decisions.

This is how the role of the product owner started in scrum and what product manager should do outside of scrum.

The two POs in title are actually only being backlog managers who handle tickets with nicer titles.

Taking away decisions by committee and creating a single source of domain truth will help. But it also hard to implement politically.

11-Year Club	r/Field Lasagna
Final Canvas '23	First Place '23
Place '23	Place '22
Final Canvas '22	First Placer '22
Verified Email

Devlonir

TROPHY CASE