When to escalate an issue?
One of my team distributes story points of a user story between Dev and QA while sprint planning.
This creates a restricted mindset where people would pick up work work items based on their story points capacity where we consider 1day as 1sp working using SAFe.
The team is a mix of 4devs and 3QAs.
what I’m trying to change?
I’m trying to get the team to develop a mindset where they focus on the work item and not the story points.
The Tech manager agrees for the change but the tech lead does not and want to distribute work items story point. E.g user story A is a 5pt, then the lead would give a dev 2.5 and QA 2.5 or Dev 3 and QA 2.
The team is delivering the PIs committed objectives. It’s a culture issue here.
It’s a culture issue here.
Who sees this as an issue? You and I might, but from what you describe there seem to be no consequences and no penalty arising from the precociously scaled implementation you have. Who in the company wants different outcomes from this team, and can create a sense of urgency for change?
I agree with Ian. Is this causing issues that prevents the team from being able to consistently deliver the necessary increments? If not, then it may not need to change. Remember that the Developers are responsible for the plan of how to deliver the increments from the Sprint Backlog. The Scrum Master supports them in their efforts. Since Scrum does not have a role for a Tech Manager or Tech Lead, I do not know what roles they are trying to fulfill (Product Owner, Developer) and can't comment on their contributions.
Also, you need to understand that SAFe does not use Scrum as described in the Scrum Guide. It uses a variation that they developed called ScrumXP. It is similar but is modified to fit into their Scaled Agile Framework (SAFe). So, the answers we give related to Scrum from the Scrum Guide may not be consistent with the way that your organization has implemented SAFe.