Multiple projects in n+1 landscape

[Former Member]

Hello Experts,

We have a specific requirement to complete 3 projects in a stipulated time frame.

Requirement explained with the help of an example

- Three projects to be completed in 12 months

Project 1  P1  Go live date 3rd Month

Project 2  P2  Go live date 7th Month

Project 3  P3  Go live date 8th Month

- All projects have no shared workbench or customizing objects.

- Projects donu2019t have any shared objects with the existing production support and client wants all projects to be in the existing production system. Introducing a new production instance is not an option.

- Start data for all 3 projects is 1st month.

- Existing landscape has

DV1  Development

QS1  Quality

PR1  Production

- Intention is to introduce a n+1 system landscape and start the project 1.

Catch - However with this concept P1, P2 and P3 cannot be started at the same time.

Approach to handle the scenario:

Introduce

One development system  DV2

Two quality systems  QS2 and QS3

Three transport groups  P1GRP and P2GRP , SUPGRP

All transports released to P1GRP from DV2 will only go to QS1

All transports released to P2GRP from DV2 will only go to QS2

All production support changes keyed in to DV2 released to SUPGRP will goto both QS1 and QS2.

This way production support changes can be tested along with the new projects and go lives can be staggered.

Question that a basis person would ask at this juncture:

If the project go lives are staggered and all of them are mutually exclusive, why isnu2019t project 1 and 2 done in production support path?

Issue:

o Go live dates for projects may slip.

o At some stage in the project 1 or project 2 some of objects may be shared causing issues with the production support.

Help required :

Has anyone come across such a situation in their porject ?

Would products like CTS+ in combination with CHRAM help to achieve this?

Any other recommendations?

Thanks in advance.

Thanks,

Rohit.

[sunny_pahuja2]

Hi,

As per my experience, you can have a separate landscape (DEV, QA, Mock Production system). These all three systems will be replica of corresponding system in your Live environment. So, you can do your development and testing here. So, as soon as go-live comes near you can transport all your change request to your live environment during cutover time. As a result your live environment will not be effected because of your future projects.

Thanks

Sunny