What kind of roles are required in a SAP Portal project in general?

When a company would like to start a portal project, there will usually have the persons to take responsibility on the following roles (one person can have more than one role)

1) Project Manager
Role description in brief: Manage and monitor the whole project in term of business requirement, design, analysis, implementation and team leadership.
2) Business Analyst
Help in outlining and developing the business requirement of the project. Comunicate with business owner, users and content manager to gather business data required by the project.
3) Technical Project Lead
Lead the technical team (solution architect, developers, system administrator) in technical design and implemenatation.
4) Solution Achitect
Layout the overall portal architecture design for the project implementation. Configuring hardware (i.e. server), portal installation and other portal infrastruture.
5) System Administrator / Portal Basis Administrator + Security Administrator
After portal installation, responsible for standard setup and configurations within the portal. His/her responsibilities included security settings, backend connectivity, content migration and other user management tasks(i.e. setting up LDAP server for user management engine).
6) Several Portal Developers
Developers are the person actually develop the custom portal applications that cannot be configured through standard portal configurations. There are different sub-roles in development: content development, connectivity with backend system, Knowledge Management & Collaboration, or Business Intelligence and etc.
7) Content Manager
Manage and intergrate content that built by developers and take care portal overall look- and-feel. Tasks included configuring page layouts, iviews, roles, worksets, navigations and etc.

I will cover their specific tasks in detail in the future (especially developer's tasks).

SAP Implementation

n
SAP Implementation is the whole of processes that defines a complete method to implement the Enterprise Resource Planning SAP ERP software in an organization. The SAP implementation method described in this entry is a generic method and not a specific implementation method as such. It is based on best practices and case studies from various literature sources and presents a collection of processes and products that make up a complete implementation method to allow any organization to plan and execute the implementation of SAP software.
Introduction
The implementation of SAP software, such as SAP R/3 is almost always a massive operation that brings a lot of changes in the organization. The whole process can take up to several years. Virtually every person in the organization is involved, whether they are part of the SAP technical support organization (TSO) or the actual end-users of the SAP software. The resulting changes that the implementation of SAP generates are intended to reach high level goals, such as improved communication and increased return on information (as people will work with the same information). It is therefore very important that the implementation process is planned and executed with the usage of a solid method. There are various SAP implementation methods. An example of how one company, Robert Bosch GmbH, implemented SAP R/3 over 10 years is available This study shows that designing IT architecture is very critical in SAP implementation practices.