|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
VersionOne Community > Discussions > VersionOne-users > Member Groups and Teams
|
|
|
 | E-mailed: 5/2/2008 5:43 PM by System Account | | |
|
| | Member Groups and Teams?
Is there a description someplace of the advantages of Member Groups
and Teams? A comparison that talks about when one is appropriate vs
the other?
Pat O
Cognex, Corp.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "VersionOne-users" group.
To post to this group, send email to versionone-users@googlegroups.com
To unsubscribe from this group, send email to versionone-users-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.com/group/versionone-users?hl=en
-~----------~----~----~----~------~----~------~--~---
| |
| |
| E-mailed: 6/22/2012 5:34 PM by System Account | | |
|
| |
The referenced KB article (Q11414) does not exist.
| |
| |
| E-mailed: 6/26/2012 11:36 AM by System Account | | |
|
| |
Pat,
I’m not sure if there is any place that gives this information, but here’s the skinny from my point of view:
Teams are created for a variety of reasons and most grids have fields that allow you to filter / sort by them as well. VersionOne users aren’t assigned to
teams. Users have the ability to assign Teams to Stories and Defects. Once VersionOne users are associated with these backlog items, they automatically become a part of a team. While a bit confusing at first, this allows for the reality of team memberships
to change without having the messy admin overhead.
Member Groups are much more rigid and are used solely for reporting purposes. We use Member Groups for reporting structure purposes. As a manger, I have three
different teams of people that work on completely different projects in VersionOne. By creating a single Member Group, I can run effort reports, etc. for all of my direct reports without the mess of having to run multiple reports for multiple teams.
Hope that helps.
Brook W
| |
| |
| E-mailed: 5/5/2008 2:57 PM by System Account | | |
|
| |
Yes :)
http://community.versionone.com/KnowledgeBase/FAQs/Q11414.aspx
-Maggie
| |
| |
| E-mailed: 5/5/2008 3:18 PM by System Account | | |
|
| |
Pat-
I like to think of Teams as a planning tool that is a conceptual group
of people and member groups as an assigned reporting group of people
(think skill group).
In an agile environment of self-managed teams covering all roles, the
team is the scrum/xp team and the member group is the QA team that has
a person in each scrum team.
In companies like mine, these may be one in the same.
As far as I can tell (I'm newer to V1), you can't assign people to
teams, but you can assign people to member groups. This is because an
agile team will pull it's items from the "team bucket" and self-manage
them.
Kevin Schlabach
Project Coordinator, Strategic Development
Beyond.com, Inc.
| |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
