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?

[sonja1]

Hello Kelly, sorry for the very late reply - I've been away

If the meeting has not yet occurred, I would love to be included.

[kellykaufmann]

Perfect Sonja Haas - the meeting is currently set for Tuesday 7/21 at 10am CST. I just 'friended' you - if you send me your email address I'll add you to the meeting invite.

[LaniStover]

Hi Kelly,

I won't be able to attend, but can you provide details back from the session via a recording or some other mechanism?

[unigrpmm]

Hi -- I am looking for the outcome of this conversation.   Can you please let me know the thread in the community where this meeting was summarized?   Would be a big help to me implementing PPM, SDLC, etc-- thanks so much.            

[arun_vydianatha]

SDLC had this concept of Release Teams and Sprint Teams from Calgary/Dublin days.

The idea was to quickly assemble a Release Team and pick members from them and assemble a Sprint Team. For each team you can have potentially different team composition. For each sprint you can pick different members. Here I am talking about the pure SDLC flow (without PPM). Members have additional attribute added to them like points which rolls up to give you the Team points.

In Fuji we have extended the team concept in SDLC and introduced Project Team in the mix. Our Release Table, Story table historically had reference to Scrum Team entity. Technically we can use groups as well for this. But changing them now to point to Group instead of Team would break many existing customers who use pure SDLC (without Projects).

For the question "Where will I find my work" - my work is tasks where my name comes in "Assigned To" field. So even in case of Story/Scrum Tasks we use the same Assigned To field like we do in Incident or Problems.