Scrum Teams vs Work Groups
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-15-2015 07:13 AM
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?
- Labels:
-
Project Portfolio Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-18-2015 02:18 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2015 06:16 AM
After further research it looks like Team has properties and relationships that are different from Group, but I'm still trying to figure out if there's important architecture concerns I'm missing.
I want work to be assigned to Assignment Groups. That way I can build single list views/reports for a a group to get maximum visibility to all work, regardless of task type. Using OOB data elements, it looks I need two separate management structures to ensure work gets to the same people.
If Team needs unique relationships, are there any obvious reasons why it wasn't made an extension of Group?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2015 08:40 AM
I wonder if you could have the system create a 'group' that matches each of your 'assignment groups'. And then in Agile, when you select a 'group', behind-the-scenes it could auto-populate 'assignment group' as well?
As for the rest of the functionality of 'group' within Agile, we're also looking into this ourselves. Hoping someone at SN can give you more information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-23-2015 03:02 PM
I think this is a good usecase where agile team members would also be working on other tasks ( incidents, problems etc.) in addition to working on tasks for the project's agile phase. The idea behind creating a team entity was to create a small group of people within PPM who would have a defined capacity ( points) and would only work on agile phase tasks as a team.
Generally an agile team has a defined capacity (velocity) using which release/phase planning is performed with the assumption that team members availability to the team is known in advance. An assignment group is slightly open where users can work on different tasks depending upon the workload.
Please explain your usecase/requirement with more details, we can consider this for future enhancement.
Thanks
Pradeep