![]() ![]() ![]() Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Unsuitable post content includes, but is not limited to, Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. may, at its discretion, remove any post that it deems unsuitable for these forums. does not endorse user-submitted content or the content of links to any third-party websites. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. For privacy concerns, we cannot allow you to post email addresses. Please note that the first and last name from your member profile will be displayed next to any topic or comment you post on the forums. The Scrum Master is responsible for the Scrum process, its correct and continuous implementation, and the maximization of its benefits.īy posting on our forums you are agreeing to our Terms of Use. The Scrum Master doesn't manage the team that produces the work instead, he supports the product owner, coaches the team, and makes sure that Scrum processes are adhered to. The Scrum Master's role is more that of coach and facilitator, a role that sits between the project and the customer. Traditionally, the project manager is a leader, a decision maker, a planner, someone who manages the project and the team and is the person accountable to the business for accomplishing the project objectives. One of things I have come across in my personal experiences is new Scrum Masters who were formally Project Managers, falling back into there old mind set as a PM and not as a Scrum Master.Ĭontrary to popular belief, the Scrum Master and project manager roles are highly different and shouldn't be confused. I believe that the Scrum master should not be doing this activity, and should be down to the PO and The Dev Team. You'll see the blocked test account is still in the Group but is absent from the from end Team.With regards to " I like to move tasks that are dependent on something else into blocked if that something else is taking too long." However, this is not an org-wide team and I'd have not expected this behaviour for groups with manually managed membership.įor reference, the image below shows the message in the General channel of a test Team we used to recreate the issue, alongside the status within different admin portals from the same in time. I'm expecting this to be related to Microsoft Teams eligibility criteria as the article on Org-wide teams talks about blocked accounts. when unblocked, the member is returned to the Team - with another message in the general channel!.we're experiencing this behaviour on multiple independent tenants.these accounts are not removed from the underlying Office 365 Group.I'd be really interested to hear if you've experienced this or if you think this is expected behaviour that is acceptable and we should be changing our processes when temporarily blocking accounts. I'm raising a ticket with Microsoft Support but I'm posting here in case others have any insight to this. As sometimes the blocking of an account is for sensitive reasons, for it to be broadcast to other team members is not our expected or desired behaviour. However within 24 hours of blocking the account, the member is removed from Microsoft Teams teams they're part of. These are accounts that are still active, still have licenses, and accounts that we will sometime unblock after a period of time. This is behaviour we did not expect to see! Sometimes we need to temporarily block an account. We've recently spotted that when we block an account in Office 365, the account is removed from the Teams it's in with a 'XYZ has been removed from the team.' message.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |