It's all about the answers!

Ask a question

Sharing project templates for existing Project Areas

Tadeusz Janasiewicz (120149) | asked Jun 05 '14, 4:02 a.m.
edited Oct 24 '14, 5:35 p.m.

I have a question about a supported scenarios in case of project template sharing:

The recommended way is to use the Unconfigured template in case of new PAs because this is the easiest way to assure that all configuration data is inherited [1] [2].
But how inheritance works in case you need to make changes in the consumer project that was created based on a different project templates?
For example, I've 1 single provider project area and 2 types of consumers, some are based on Unconfigured template (A) and some were originally based on Scrum (B) (older projects).

Is the second scenario (B) supported?


Tadeusz Janasiewicz commented Jun 05 '14, 4:03 a.m. | edited Jun 05 '14, 4:07 a.m.

Hi @jburns maybe you know the answer?
Is there any document that describe such scenario?

Accepted answer

permanent link
Eric Jodet (6.3k5111120) | answered Jun 05 '14, 7:27 a.m.
 Hello Tadeusz,
(possibly Jared or Ruby - Martha Andrews) may correct me but given:

Using a template that defines its own process causes the project area that consumes process to override the process it is consuming, which is not usually the behavior that you want.

Which I interpret as:
- supported
- the SCRUM based consumer projects will override settings in parent PA
(which make inheritance useless here)
Tadeusz Janasiewicz selected this answer as the correct answer

Your answer

Register or to post your answer.