I work as a technical lead / team lead in the IT security team at my workplace. We currently use the SAFe Scaled Agile methodology of organizing our features and user stories.
During the most recent program increment planning event last week, team members on our team were trying to solution / design the work for user stories when it is my understanding that the PI event should focus on the business objectives from product owner and the "what" of the upcoming sprints, not the how of technical implementation.I felt that while technical discussion of how to implement is valuable, such ideas detract from planning of the bigger iteration roadmap.
The whole of the IT security team us about 70 folks, divided into several units, e.g: AppSec,controls and compliance, security architecture etc. We have a product owner and scum master. However, our scrum master is not the most assertive team member which somewhat hinders us, as usually maintaining team discipline and prioritzation is usually their responsibility in an Agile work culture.
To give some examples of solutioning that team members started to discuss that I feel is distracting during planning ceremony:
How to actually pen test an application and the viable attack vectors to attack with, rather than when or agreeing on the rules of engagement first with asset owners
Actual brainstorming of test cases to verify a vulnerability has been remediated, rather than the bigger strategy of how to approach such testing itself
How do you discourage in the moment solutioning during Agile PI events without team members feeling shut out as if their ideas dont matter? If I raise this point, I want to appear supportive of all on the team.
As I am neither the product owner nor scrum master , is it appropriate for me to raise this issue at all, i.e: Inefficient use of time and possible misunderstanding of the objectives of Agile PI planning?