Return to Question

As a Tech Lead within a "Scrum" team, I am annoying regarding some laid rules.

It is established that only Product Owner, Business Analyst and Scrum Master (and eventually Product Manager) be part of the user stories prioritization process (backlog prioritization).

They are sorting US based on story points, without any further software-oriented facts and knowledge.
Worth noting that those story points emerged from a quick and probably "blind" macro-estimation process, not a deep one.

They judge which valuable US could be delivered and when through those macro-estimations.

I notice that their decision is often based on wrong assumptions and false hypothesis; leading to a sorting readjustment, therefore wasting anybody's time.

Do you consider a Tech Lead (or any other qualified developer) should be part of this prioritization process to aid to prioritize based on programming knowledge?
Like a guarantor of feasibility.

As a Tech Lead within a "Scrum" team, I am annoying regarding some laid rules.

It is established that only Product Owner, Business Analyst and Scrum Master (and eventually Product Manager) take part of the user stories prioritization process (backlog prioritization).

They are sorting US based on story points, without any further software-oriented facts and knowledge.
Worth noting that those story points emerged from a quick and probably "blind" macro-estimation process, not a deep one.

They judge which valuable US could be delivered and when through those macro-estimations.

I notice that their decision is often based on wrong assumptions and false hypothesis; leading to a sorting readjustment, therefore wasting anybody's time.

Do you consider a Tech Lead (or any other qualified developer) should be part of this prioritization process to aid to prioritize based on programming knowledge?
Like a guarantor of feasibility.

As a Tech Lead within a "Scrum" team, I am annoying regarding some laid rules.

It is established that only Product Owner, Business Analyst and Scrum Master (and eventually Product Manager) be part of the user stories prioritization process (backlog prioritization).

They are sorting US based on story points, without any further software-oriented facts and knowledge.

They judge which valuable US could be delivered and when through those macro-estimations.

I notice that their decision is often based on wrong assumptions and false hypothesis; leading to a sorting readjustment, therefore wasting anybody's time.

Do you consider a Tech Lead (or any other qualified developer) should be part of this prioritization process to aid to prioritize based on programming knowledge?
Like a guarantor of feasibility.

As a Tech Lead within a "Scrum" team, I am annoying regarding some laid rules.

It is established that only Product Owner, Business Analyst and Scrum Master (and eventually Product Manager) be part of the user stories prioritization process (backlog prioritization).

They are sorting US based on story points, without any further software-oriented facts and knowledge.
Worth noting that those story points emerged from a quick and probably "blind" macro-estimation process, not a deep one.

They judge which valuable US could be delivered and when through those macro-estimations.

I notice that their decision is often based on wrong assumptions and false hypothesis; leading to a sorting readjustment, therefore wasting anybody's time.

Do you consider a Tech Lead (or any other qualified developer) should be part of this prioritization process to aid to prioritize based on programming knowledge?
Like a guarantor of feasibility.

As a Tech Lead within a "Scrum" team, I am annoying regarding some laid rules.

It is established that only Product Owner, Business Analyst and Scrum Master (and eventually Product Manager) be part of the user stories prioritization process (backlog prioritization).

They are sorting US based on story points, story points that are derived from a time notion, not an effort/complexity notion.
This mapping was the decision of the Scrum Master.

PO and them judge which valuable US could be delivered and when through those macro-estimations.

I notice that their decision is based on wrong assumptions and false hypothesis; leading to a readjustment of sorting, therefore wasting anybody's time.

Do you consider a Tech Lead (or any other qualified developer) should be part on this prioritization process to aid to prioritize based on programming knowledge?

As a Tech Lead within a "Scrum" team, I am annoying regarding some laid rules.

It is established that only Product Owner, Business Analyst and Scrum Master (and eventually Product Manager) be part of the user stories prioritization process (backlog prioritization).

They are sorting US based on story points, without any further software-oriented facts and knowledge.

They judge which valuable US could be delivered and when through those macro-estimations.

I notice that their decision is often based on wrong assumptions and false hypothesis; leading to a sorting readjustment, therefore wasting anybody's time.

Do you consider a Tech Lead (or any other qualified developer) should be part of this prioritization process to aid to prioritize based on programming knowledge?
Like a guarantor of feasibility.