Building a Team – Most of the organization always short change on resources at the beginning of the project, as it comes close to go live, they realize that they are running short of resources. Then it becomes difficult to get a resource and train him/her. You can get very good technical resource, but not the one who knows your business process. So it is very important that the resources are planned properly, and get the resources at right time.

Scope- Try to keep the scope of the project plain and simple if it is a new implementation. Changing the scope is the last thing you want to do.

Design and Planning- The more time you spend on this phase, less time you will spend on the rest of the phases. Planning is very critical.

I have always been asked how the role should be constructed, if the customer should be using composite roles. How many roles should be made?

I follow very simple rule – Three roles for any job duty. Example of job duty is Account Receivable clerk. 

• The first role is a general role which is assigned to all the users in that company. This will have transaction like SU53, SU03 and other t-code which will be used by all users in your company. 
• Second role is a report / display role for specific track, like finance will have display role which will be assigned to all the finance users. Please don’t assign any report which is very critical, and not be accessed by all users.
• Last the job duty role. Example of Job Duty based role is Account Receivable Clerk role.