Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Participants in the scrum council weekly #23

Open
MetalMagno opened this issue Feb 16, 2022 · 4 comments
Open

Participants in the scrum council weekly #23

MetalMagno opened this issue Feb 16, 2022 · 4 comments

Comments

@MetalMagno
Copy link
Contributor

MetalMagno commented Feb 16, 2022

It looks like only the accounts managers and PMs talk. Is necessary the attendance of the QAs?

@CesarDav
Copy link

if only the status of the projects is going to be discussed, I prefer not to be at this meeting.

@anjelysleal
Copy link

I think that if the PM gives the status of the project, the presence of the QA is not necessary.

Unless the PM cannot attend the meeting and it is the QA who must comment on it. The invitation would only be passed on that day with prior notification. (This is not a recurring case).

@rossileidys1990
Copy link

I think QA staff shouldn't be involved in the Project Scrum Council meetings. The PMs are the ones that can give feedback about the project status. On the daily meetings, the PM can take a few minutes to explain the results of the meeting about the project status.

@Edwardzabalaf
Copy link

the presence of the Qa is necessary if you are doing a mixed Qa /Pm work or as in my case Project and Quality Specialist.

If the presence of the Qa would be necessary if for some reason the PM is going to be absent from the Scrum Council, in this case, he must inform the Qa of the status of the project, and notify that it will be the Qa of the project who will be present to give the status of the project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants