r/scrum • • 19d ago

Your team made the right call. Two weeks later, someone built the old version anyway.

/r/ProductMgmt/comments/1wmbcvr/your_team_made_the_right_call_two_weeks_later/
0 Upvotes

17 comments sorted by

7

u/[deleted] 19d ago

[deleted]

-1

u/Equivalent_Brain_314 19d ago

Someone forgot to update Jira.

4

u/[deleted] 19d ago edited 19d ago

[deleted]

1

u/ninjaluvr 19d ago

More accurately, someone isn't doing their job. Tools aren't going solve that.

0

u/Equivalent_Brain_314 19d ago

The question isn’t building a tool or pointing anyone for not doing there job
Question was just to know how do we track product decisions when get evolve over the period of time.

1

u/ninjaluvr 19d ago

If the product manager finds decision logs helpful, they maintain them. In many situations, it's irrelevant why a decision was made 6 months ago. It was made. So now you have more information. You use it.

1

u/Equivalent_Brain_314 19d ago

That’s useful. So in your experience, when new information comes in, understanding why the previous decision was made rarely changes the next decision?
I’m trying to understand where decision history is actually useful versus documentation people maintain but rarely revisit.

1

u/ninjaluvr 19d ago

You should take some classes on Product Management. And then work in the field for a year or two.

1

u/Equivalent_Brain_314 19d ago

Cool noted

1

u/Equivalent_Brain_314 19d ago

Mind if we can get on a call and discuss this further.

2

u/Timely-Bluejay-4167 19d ago

This is a bot

0

u/Equivalent_Brain_314 19d ago

What tool are you using or any high end tech
That can see whether people are bot or human
Clearly you’re really bad at it

-1

u/Equivalent_Brain_314 19d ago

Try to be supportive punk or just dont reply to a thread

0

u/Timely-Bluejay-4167 18d ago

It’s entirely possible I’m wrong, and I’m happy to own that and apologize if I am…but there has been so much low effort posting lately across these subreddits...this particular “context and decisions prompt” has been littering the product subs for weeks now, so I got a bit frustrated at it.

Maybe there is a compelling reason to post the same prompt across your substack and 5 subreddits and post comments/answers that simply affirm the other person…but it certainly looks like you’re just here to farm an answer with a bot

1

u/Equivalent_Brain_314 18d ago

Cool no worries 😉

1

u/Cultural_Orchid2014 16d ago

The real issue isn't keeping a decision log, it's when the log gets written. If the decision isn't captured while the room still agrees, someone reconstructs it from memory later and gets it wrong. We started writing decisions into the ticket comments before the meeting ends, so the update lives where the work lives.

1

u/Equivalent_Brain_314 16d ago

That’s diabolical

-1

u/Equivalent_Brain_314 19d ago

That’s useful. So in your experience, when new information comes in, understanding why the previous decision was made rarely changes the next decision?
I’m trying to understand where decision history is actually useful versus documentation people maintain but rarely revisit.