licenses versus roles

Kevin Crocker (201●8●5) | asked Nov 18 '09, 1:50 p.m.

I've installed JFS 1.0.0.1 and RTC 2.0.0.1 Standard. Comes with 3 developer licenses.

For our project we want to use the Scrum Project Process thus we need to have:
Product Owner
Scrum Master
Team Members
Stakeholders

I know that I can assign whatever roles I want to whatever licenses I give out - but it seems to me that to do Scrum cleanly, I would want to have at least 4 licenses; one for each role above to nicely and cleanly separate the roles.

And, how did 3 licenses become the magic number?

This is getting my head whirling. For example: I installed RTC, thus I'm the System Admin; but I also had to login as ADMIN so I could create some users etc; but I'm also going to be one of the users (likely a team member).

Thus, I'm just plain getting confused on what the licenses really are versus what I should be doing via users or via roles and how do I keep everything
cleanly separated without resorting to process permissions.

2 answers

Most liked answers ↑|Newest answers|Oldest answers

permanent link

Geoffrey Clemm (30.1k●3●30●35) | answered Nov 18 '09, 3:38 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

No magic to the number "3" wrt the 3 included licenses. That is done
just so that you can get started doing useful work when all you've
bought is a server.

To get started, you need to give your administrator a Developer license
(one of the 3 included ones is fine).

Then for now, just ignore licenses.

First select which process templates you want to use (and feel free to
customize any of them to create your own custom process templates). For
process templates, it is the roles that matter.

Then instantiate your project areas (using the appropriate process
templates). You can also create some team areas (possibly customizing
their process), but you could also defer that until later.

Then for a given user, assign them to the appropriate repository groups,
add them as members to the appropriate project and team areas, and give
them the appropriate roles in each of those project in team areas.

NOW you need to think about licenses.

For a given user, they need to have a license that allows them to do all
of the operations required by all the roles they perform, and assign
them that license. The simplest approach is just to give everyone a
Developer license. But if you want to save some money, you can select
the folks that don't need to do SCM or Build operations, and just give
them a Contributor license.

And you're done (other than getting some software written :-).

Cheers,
Geoff

kevincrocker wrote:

I've installed JFS 1.0.0.1 and RTC 2.0.0.1 Standard. Comes with 3
developer licenses.

For our project we want to use the Scrum Project Process thus we need
to have:
Product Owner
Scrum Master
Team Members
Stakeholders

I know that I can assign whatever roles I want to whatever licenses I
give out - but it seems to me that to do Scrum cleanly, I would want
to have at least 4 licenses; one for each role above to nicely and
cleanly separate the roles.

And, how did 3 licenses become the magic number?

This is getting my head whirling. For example: I installed RTC, thus
I'm the System Admin; but I also had to login as ADMIN so I could
create some users etc; but I'm also going to be one of the users
(likely a team member).

Thus, I'm just plain getting confused on what the licenses really are
versus what I should be doing via users or via roles and how do I
keep everything
cleanly separated without resorting to process permissions.

permanent link

Kevin Crocker (201●8●5) | answered Nov 18 '09, 6:43 p.m.

Thanks Geoff.

I'm the Administrator - so I gave myself one of the licenses :-)

I've already selected the process template - Scrum. At the moment I don't know if I'll have to customize - I'll learn as I go.

I've already created the project area (singular in this case). I don't think I need team areas for right now - this is a singular project that has an extremely short time line - 8 weeks - so adding additional teams seems to be overhead that I can't accommodate.

There is only one repository group - this is a POC/POT but it's a complex development project.

That part about assigning the licenses to people - I likely need to have some floating licenses because people will come and go on this project on a daily basis - I'm using field experts to contribute small portions each. Their time is valuable and I doubt I'll be able to get more than an hour or two out of any one expert. I was planning on giving out developer licenses - the whole project is going to use the built-in SCM and our build is strange - it's not a running app, it's going to be PDF and PPT files. So, everyone who contributes is going to have to be bound by the Source Code Management, but I'm likely the only one who has to do the builds (once I figure out how to automate PDF and PPT generation as a build concept).

Thanks - your response was helpful.

Kevin

No magic to the number "3" wrt the 3 included licenses. That is done
just so that you can get started doing useful work when all you've
bought is a server.

To get started, you need to give your administrator a Developer license
(one of the 3 included ones is fine).

Then for now, just ignore licenses.

First select which process templates you want to use (and feel free to
customize any of them to create your own custom process templates). For
process templates, it is the roles that matter.

Then instantiate your project areas (using the appropriate process
templates). You can also create some team areas (possibly customizing
their process), but you could also defer that until later.

Then for a given user, assign them to the appropriate repository groups,
add them as members to the appropriate project and team areas, and give
them the appropriate roles in each of those project in team areas.

NOW you need to think about licenses.

For a given user, they need to have a license that allows them to do all
of the operations required by all the roles they perform, and assign
them that license. The simplest approach is just to give everyone a
Developer license. But if you want to save some money, you can select
the folks that don't need to do SCM or Build operations, and just give
them a Contributor license.

And you're done (other than getting some software written :-).

Cheers,
Geoff

kevincrocker wrote:

I've installed JFS 1.0.0.1 and RTC 2.0.0.1 Standard. Comes with 3
developer licenses.

For our project we want to use the Scrum Project Process thus we need
to have:
Product Owner
Scrum Master
Team Members
Stakeholders

I know that I can assign whatever roles I want to whatever licenses I
give out - but it seems to me that to do Scrum cleanly, I would want
to have at least 4 licenses; one for each role above to nicely and
cleanly separate the roles.

And, how did 3 licenses become the magic number?

This is getting my head whirling. For example: I installed RTC, thus
I'm the System Admin; but I also had to login as ADMIN so I could
create some users etc; but I'm also going to be one of the users
(likely a team member).

Thus, I'm just plain getting confused on what the licenses really are
versus what I should be doing via users or via roles and how do I
keep everything
cleanly separated without resorting to process permissions.

Your answer

Register or log in to post your answer.

Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.

It's all about the answers!

Related questions

licenses versus roles

2 answers

Your answer