How to decide on writing 1 Blueprint or Many Blueprints for a small project?

[Former Member]

Hi folks,

     what are the decisioning criteria (questions) that you use to decide on whether writing one Blueprint, or several Blueprints, is the best course of action when doing blueprint for a small project (say, less than 300 person days)?

     Can you offer me a few things you have used for such decisions in past? 

Thanks,

     Russ

[Former Member]

Hi Russ,

It is definetely a good idea to split the blueprint writting task among the project team members where each member will produce the blueprint for the task(s) he will perform. Involving the project team members in the bueprint phase will increase their commitmment. 

Produce a number of sections for the blueprint, which will be merged into a single document in the end. This approach will facilitate re-usability in future projects. It is also a good idea to assign the ovverview of the blueprint to one person (the most experienced one) who will also be repsonsible for merging the various sections in to a single document.

Regards,

Nikos

[Former Member]

Hi Russ,

My understand and i do blue printing if i have one complete solution to be implemented in the existing SAP Landscape. From your query i understand that you already have a existing SAP Landscape and over it you are implementing an SAP Solutions. If this is the case you can create a Master Blue Print and split the Blue print with Different Tasks for many of the Business Cases. This will be a good approach i think.

This is pretty much the same approach like that of Nikos.

Regards

Balakumar