Scrum Teams vs Work Groups

[Uncle Rob]

So it looks like the SDLC / Project areas of the tool have a concept called "teams", which for the life of me looks exactly like Assignment Groups but without the roles.

Much of the OOB sprint planning seems to hinge on that Team concept but I can't understand what team is bringing to the table that normal groups wouldn't.

Could someone explain it to me?

[Tammy Simmons]

Not sure if there was a resolution for the assignment groups versus Agile team so I thought I would offer up this information incase it can help out someone. We also faced this issue where we needed an assignment group that could work Incidents and also have access to Agile Development without creating a separate team.

Solution: We created the group under the "System Security > Users and Groups > Groups" module and just added "Agile Team" to the "Type" field on the new group. We started with Calgary and are currently on Helsinki so keep in mind, Calgary still contains a "Group Type" field which is different from the "Type" field on a group. I have a sandbox that started with Helsinki but now on Istanbul and the "Group Type" field on groups appears to have been deprecated and replaced with "Type".

Hope this helps.

[SusanWinKY]

tsimmons, curious... did you have a similar issue with project tasks?

We can multi-purpose groups as both Agile Team and Assignment Group, but can't *consistently* get those same groups to work for a project task.  The reference qualifier on the project task's Assignment Group has this dictionary override...

javascript:'sys_idIN'+ScrumSecurityManager.getPhaseDotGroup(current).join(',')

Not sure what that's doing.